Serverless on AWS overview - PeachPayments meetup
•Download as PPTX, PDF•
0 likes•116 views
Overview of AWS Lambda, Step-functions and it allows you to innovate faster
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Serverless on AWS overview - PeachPayments meetup
Similar to Serverless on AWS overview - PeachPayments meetup (20)
More from Cobus Bernard
More from Cobus Bernard (20)
Recently uploaded
Recently uploaded (20)
Serverless on AWS overview - PeachPayments meetup
- 1. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T Serverless computing: how to innovate faster Cobus Bernard Technical Evangelist Amazon Web Services @cobusbernard
- 2. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Thecomputing “spectrum” onAWS Amazon EC2 Microsoft SQL Server On Amazon EC2 AWS Lambda Amazon Kinesis Amazon S3 Amazon API Gateway Amazon SQS Amazon DynamoDB AWS IoT Serverless Amazon Cognito Amazon CloudWatch Amazon Athena AWS X-Ray AWS Step Functions Amazon EMR Amazon ElastiCache Amazon RDS Amazon Redshift Amazon Elasticsearch Managed Amazon MQ Amazon SageMaker Amazon Neptune AWS Amazon DocumentDB
- 3. Provider space (managed by AWS) Consumer space (managed by the customer)
- 4. physicalserverVMcontainerfunction Levelofabstraction Provider space (managed by AWS) Consumer space (managed by the customer)
- 5. Amazon EC2 Amazon Lightsail physicalserverVMcontainerfunction Provider space (managed by AWS) Consumer space (managed by the customer) Levelofabstraction
- 6. Amazon EC2 Amazon EKS Amazon Lightsail Amazon ECS physicalserverVMcontainerfunction Provider space (managed by AWS) Consumer space (managed by the customer) Levelofabstraction
- 7. AWS Lambda Amazon EC2 Amazon EKS Amazon Lightsail Amazon ECS physicalserverVMcontainerfunction Provider space (managed by AWS) Consumer space (managed by the customer) Levelofabstraction
- 8. AWS Lambda Amazon EC2 Bare Metal Amazon EKS Amazon Lightsail Amazon ECS physicalserverVMcontainerfunction Provider space (managed by AWS) Consumer space (managed by the customer) Levelofabstraction
- 9. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 10. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. No server or container management Flexible scaling No idle capacity $ High availability Serverless means…
- 11. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Event-drivenarchitectures Services (anything)Event source Serverless Function
- 12. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Web apps DynamoDBLambdaAPI Gateway Browser CloudFront Amazon S3 Cognito
- 13. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWSStepFunctions
- 15. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T Thank you! Cobus Bernard Technical Evangelist Amazon Web Services @cobusbernard
Editor's Notes
- Landscape changing with Fargate and Aurora Serverless. Not complete list, etc.
- Before we begin, lets review what Serverless means. When you use the Amazon Serverless platform, you get to focus on building the applications and apis that matter to your business. Let AWS handle all of the heavy lifting behind the scenes. Scaling becomes super simple. Instead of scaling by adding more servers, you now scale per request. AWS handles all of this for you. You’re ready to serve 100 customers, or thousands of customers as you grow – all without doing anything. Because you no longer have idle instances, you never pay for idle capacity. Finally, you automatically inherit all of the HA, DR, and best practices of AWS.
- Il vero vantaggio che moltissimi dimenticano quando iniziano a progettare architetture serverless è che per loro nature, questo tipo di applicazioni ti permettono di ragionare ed affrontare i problemi tradizionali in modo diverso. Infatti gli eventi sono il componente principale di una architettura serverless, proprio perché il vostro codice (la vostra Lambda Function) viene sempre eseguita in risposta ad un evento (o trigger). Inoltre, le vostre funzioni interagiranno con decine di altri servizi (interni o terzi), e quindi spesso il componente FaaS dell'architettura fa da collante tra i vari microservizi che andrete ad integrare. In questo modo, la quantità di codice che dovrete scrivere (e soprattutto manutenere) sarà ridotta al minimo.