6 ms·
> I suspect what’s happening from here is that API Gateway is in front of a Lambda function (indeed, this is a common design pattern that AWS documents) that do
by interblag 5y ago
> I suspect what’s happening from here is that API Gateway is in front of a Lambda function (indeed, this is a common design pattern that AWS documents) that does minimal-to-no processing of the JSON blob and puts it in a database, likely DynamoDB given the overall managed services flavor of this implementation. At that point, backend processes can take over...
A bit of an aside, but since this is an article about architecture, wouldn't the more common pattern here be APIGateway->Lambda->MessageQueue->BackendServices rather than APIGateway->Lambda->Database->BackendServices? Or does DynamoDB have something like a queue that backend processes can subscribe to? (Non-AWS user here).
- Cyberdogs7 5y agoReally either would work, depending on your specific use case. DynamoBD can emit an event stream based on writes/updates, which would be published to an SQS queue.
- dpcx 5y agoDynamoDB has DynamoDB Streams[0] and Kinesis Streams[1] which it can hook in to. 0: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html https://docs.aws.amazon.com/amazondynamodb/latest/developerg... 1: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/kds.html https://docs.aws.amazon.com/amazondynamodb/latest/developerg...