3 ms·
The wrapper to fit Lambda into a client-server synchronous-invocation world is API Gateway. But Lambda was built as an event consumer e.g. listening to a SNS q
by inopinatus 10y ago
The wrapper to fit Lambda into a client-server synchronous-invocation world is API Gateway.
But Lambda was built as an event consumer e.g. listening to a SNS queue. If you look at the broader set of AWS services you have a full toolbox of event-driven pub/sub message/event-driven tools to play with: Lambda / Kinesis / S3 / DynamoDB / SNS / SQS / Cognito / IoT and more.
It's enough of an integration & compute lego kit to build complete distributed/asynchronous pub/sub applications. However the tools are kinda .. developmental, you'll be doing much of the wiring up yourself.
- spriggan3 10y ago> The wrapper to fit Lambda into a client-server synchronous-invocation world is API Gateway. So yes, there is a server indeed. Why call it "serverless" then ? because one part of the stack uses pubsub ? then call that part a worker queue because that's what it is.
- inopinatus 10y agoThat's a separate service.