Skip to content
This repository has been archived by the owner on May 1, 2023. It is now read-only.

Use an event message broker for routing and packet transformation? #55

Open
dj2 opened this issue Aug 12, 2021 · 1 comment
Open

Use an event message broker for routing and packet transformation? #55

dj2 opened this issue Aug 12, 2021 · 1 comment

Comments

@dj2
Copy link
Contributor

dj2 commented Aug 12, 2021

Currently we send the API gateway and other ingress data directly to the Lambda handler. This means the hander has to determine what type of data it's handling.

We should investigate setting up an event message broker like Kinesis, Kafka or SQS to ingest the various data streams, transform them to be consistent and then send to the primary API handler. The handler should not have to determine where the data was coming from in order to process but be able to use the transformed data from the message broker directly.

@CalvinRodo CalvinRodo changed the title Use Kinesis for routing and packet transformation? Use Kafka for routing and packet transformation? Aug 12, 2021
@CalvinRodo CalvinRodo changed the title Use Kafka for routing and packet transformation? Use Kinesis for routing and packet transformation? Aug 12, 2021
@CalvinRodo CalvinRodo changed the title Use Kinesis for routing and packet transformation? Use an event message broker for routing and packet transformation? Aug 12, 2021
@CalvinRodo
Copy link
Member

Just edited this to be less product specific

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants