Architectural changes with serverless
•
2 likes•1,112 views
As we move into the world of Serverless, there are a few architectural changes that we are starting to see amongst the early adopters.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Architectural changes with serverless
Similar to Architectural changes with serverless (20)
More from Yan Cui
More from Yan Cui (20)
Recently uploaded
Recently uploaded (20)
Architectural changes with serverless
- 3. “Netflix for sports” offices in London, Leeds, Katowice and Tokyo
- 4. “Netflix for sports” offices in London, Leeds, Katowice and Tokyo We’re hiring! Visit engineering.dazn.com to learn more. follow @DAZN_ngnrs for updates about the engineering team.
- 5. 2014
- 11. “Serverless”
- 13. Gojko Adzic It is serverless the same way WiFi is wireless. http://bit.ly/2yQgwwb
- 14. Serverless means… don’t pay for it if no-one uses it don’t need to worry about scaling don’t need to provision and manage servers
- 15. “Function-as-a-Service” AWS Lambda Azure Functions Google Cloud Functions Auth0 Webtask Spotinst Functions Kubeless IBM Cloud Functions
- 16. AWS Lambda
- 17. AWS Lambda API Gateway IOT SNS Kinesis CloudWatch
- 21. SERVERLESS WILL FUNDAMENTALLY CHANGE HOW WE BUILD BUSINESS AROUND TECHNOLOGY AND HOW YOU CODE. Simon Wardley
- 22. more Scalable (and scales faster!)
- 23. Cheaper (don’t pay for idle servers)
- 24. Resilience (built-in redundancy and multi-AZ)
- 25. idea production choose language + framework master language + framework figure out deployment configure AMI configure ELB configure autoscaling capacity planning over-provision for launch are we doing microservices? configure CI/CD
- 26. idea production choose language + framework master language + framework figure out deployment configure AMI configure ELB configure autoscaling capacity planning over-provision for launch are we doing microservices? configure CI/CD
- 27. idea production greater Velocity from idea to product
- 29. Less ops responsibility on your shoulders
- 32. mm.. I notice some trends here
- 34. event-driven
- 36. events are an enabler for COMPOSABILITY
- 38. Kinesis
- 39. Kinesis API Gateway AWS Lambda API GatewayAWS Lambda service-A service-B
- 40. Kinesis API Gateway AWS Lambda API GatewayAWS Lambda service-A service-B
- 41. Kinesis API Gateway AWS Lambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda
- 42. Kinesis API Gateway AWS Lambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda DynamoDBIOT
- 43. Kinesis API Gateway AWS Lambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda DynamoDBIOT
- 44. Kinesis API Gateway AWS Lambda API GatewayAWS Lambda service-A service-B AWS Lambda AWS Lambda AWS Lambda DynamoDBIOT AWS Lambda AWS Lambda
- 45. build loosely-coupled system through events
- 46. service A service B service C service D bounded context bounded context
- 47. service A service B service C service D bounded context bounded context
- 48. service A service B service C service D
- 50. service A service B service C service D
- 51. service A service B service C service D
- 53. service A service B service C service Dbackward-compatible?
- 55. bounded context DON’T use events to orchestrate workflows within the same bounded context
- 56. bounded context adds unnecessary complexity to logging, tracing, and end-to-end reporting
- 57. bounded context the workflow doesn’t exist as a standalone concept, but as the sum of a series of loosely connected parts
- 58. Step Functions use Step Functions instead
- 59. Step Functions don’t forget to emit events from the workflow
- 60. Step Functions so others can react to state changes that happened as part of the workflow
- 62. service-ful
- 63. “we want to work with services, not servers”
- 65. “in the midst of all these new problems, do you wanna waste time running your own infrastructure right now?” - Austen Collins, CEO Serverless Inc
- 67. “use as many managed services as you can” - Ben Kehoe, Cloud Scientist iRobot
- 69. “I want to build a data pipeline”
- 70. S3 Buckets
- 71. S3 Buckets IAM
- 74. S3 BucketsKinesis Streams Kinesis Firehose KMS MacieIAM
- 75. S3 BucketsKinesis Streams AWS Lambda KMS MacieIAM Kinesis Firehose
- 76. S3 BucketsKinesis Streams AWS Lambda KMS MacieIAM AWS Lambda Kinesis Firehose
- 77. S3 BucketsKinesis Streams AWS Lambda AWS Lambda KMS MacieIAM AWS Lambda Kinesis Firehose
- 78. S3 BucketsKinesis Streams AWS Lambda AWS Lambda KMS MacieIAM AWS Lambda DynamoDB ElasticSearch Kinesis Firehose
- 79. S3 BucketsKinesis Streams AWS Lambda AWS Lambda KMS MacieIAM AWS Lambda Google BigQuery Kinesis Firehose
- 80. S3 BucketsKinesis Streams AWS Lambda AWS Lambda Athena QuickSight KMS MacieIAM AWS Lambda Kinesis Firehose
- 81. S3 BucketsKinesis Streams AWS Lambda AWS Lambda Athena QuickSight KMS MacieIAM AWS Lambda Kinesis Firehose
- 86. functions are ephemeral by design
- 88. secure sensitive data both at rest and in-transit
- 94. principle of Least Privilege
- 95. keep functions single-purposed & apply per function policies
- 97. Recap
- 98. Serverless means… don’t pay for it if no-one uses it don’t need to worry about scaling don’t need to provision and manage servers
- 99. idea production greater Velocity from idea to product
- 102. “use as many managed services as you can” - Ben Kehoe, Cloud Scientist iRobot