You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
CalvinRodo
changed the title
Use Kinesis for routing and packet transformation?
Use Kafka for routing and packet transformation?
Aug 12, 2021
CalvinRodo
changed the title
Use Kafka for routing and packet transformation?
Use Kinesis for routing and packet transformation?
Aug 12, 2021
CalvinRodo
changed the title
Use Kinesis for routing and packet transformation?
Use an event message broker for routing and packet transformation?
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.
The text was updated successfully, but these errors were encountered: