Talk given at the Serverless London User Group on 15 November 2017. Focus on some serverless patterns that aren't event driven, decoupled microservices, but are very effective.
Pattern: Wrapper/Proxy API Pattern: Facade API Pattern: Async Orchestration: One way chain Orchestration: Two way chain Orchestration: Fan out Orchestration: Fan in Pipes & Filters: Workflow and Long Running Pipes & Filters: Streams Traditional: Command Traditional: Singleton Serverless Design Patterns.. The Book!
sh*t I need to maintain this thing Now I’m deploying servers to manage my serverless application I can never imagine doing it any other way Serverless is Lyf
params and query strings into JSON, and then turning that into valid WSGI -Attaching response codes to response bodies, Base64 encoding, using that as a regex to route the response code, decoding in VTL, then mapping the response body -Packing and Base58 encoding multiple cookies into a single cookie -Turning cookie-setting 301/302 responses into 200 responses with HTML redirects
app in Lambda without any changes Allows you to run deploy decoupled Serverless Apps Broad support for AWS services (x-Ray, Cognito, SNS, etc) Up to date with AWS feature set (ie Dead Letter Queues)
the mainly New World family Troglodytidae. ... Most wrens are small and rather inconspicuous, except for their loud and often complex songs. - Wikipedia
@IamStan Streams your user code from S3 and hot loads it into Lambda Uses the Anaconda Python Runtime Can scale to your Lambda account concurrency limit Alternatively can use a single EC2 server