Serverless Architecture

Serverless Architecture

• 1.
  Serverless Architecture Saul Caganoff Withattribution to Mark Boyd and Mehdi Medjaoui https://medium.com/@APIdays/mapping-the-api-serverless-market-landscape-1d27d72ffc8d#.3g5xyxtco
• 2.
  Why Serverless? • DevOpsis too hard • developers don’t want to have to do the “ops” bit ==> NoOps • Lean Startups • want to prove a business idea quickly & cheaply • Because you can • new serverless offerings in the market from big platforms to small startups • Scale and Cost • Autoscaling built in • Pay per call (never pay for idle)
• 3.
  Global Drivers forServerless • Cloud - is now mainstream, easy and cheap • Microservices - gaining adoption • Digital Business - technicians and business working together in integrated teams to digitise their business and deliver value
• 4.
  Faster, faster!
• 5.
  API Serverless Products •Design an API • Attach to cloud-based data store • Add business logic • Publish • Manage consumers https://medium.com/@APIdays/mapping-the-api-serverless-market-landscape-1d27d72ffc8d#.3g5xyxtco
• 6.
  E.g. Restlet • SimpleBaaS • Create a Datamodel • It will generate a REST-ish API for you • YAML, JSON, XML • Swagger documentation • SDKs • shell, node, java, python, php, objective-c, go
• 9.
  API CRUD Makers •Transform data sets into APIs • Structured • Unstructured • CRUD https://medium.com/@APIdays/mapping-the-api-serverless-market-landscape-1d27d72ffc8d#.3g5xyxtco
• 10.
  API Funnels • Aggregatemultiple APIs into one https://medium.com/@APIdays/mapping-the-api-serverless-market-landscape-1d27d72ffc8d#.3g5xyxtco
• 11.
  Creation tools andframeworks • Create and link APIs in the cloud • Serverless Applications https://medium.com/@APIdays/mapping-the-api-serverless-market-landscape-1d27d72ffc8d#.3g5xyxtco
• 12.
  Squirrelbin Architecture • AngularSPA • Hosted on S3 • REST API • CRUD Lambda Functions • Storage in dynamoDB • Execute acorns in Lambda
• 13.
  Zombie Survivor Chat •Decoupling • separate lambda functions for search, chat and activity services • Separate data stores • dynamoDB • Data transformations in API Gateway • Early transformation -> common back-end logic • Security – service isolation & least privilege • Dev Lifecycle • Separate environments • Mocks for early APIs • CloudFormation to stitch it all together
• 14.
  Serverless Framework • Node.jsapplication • Generates CloudFormation templates • You author a REST-ish API and associated functions • It deploys to AWS • Configures Lambda Functions • Configures API Gateway endpoints
• 15.
  Sparta Framework • Serverlessfor golang
• 16.
  Is Serverless anatural step?
• 17.
  What is serverlessreally good for? • Proof of concept • Lean startup • Event-driven applications • IoT • Data analytics
• 20.
  Resources • https://medium.com/@APIdays/mapping-the-api-serverless-market- landscape-1d27d72ffc8d#.3g5xyxtco • https://serverlesscode.com/ •https://github.com/serverless/serverless • http://gosparta.io/ • http://www.meetup.com/Melbourne-Serverless-Meetup-Group/ • https://aws.amazon.com/blogs/compute/surviving-the-zombie- apocalypse-with-serverless-microservices/