Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Running web platform with no servers
Similar to Running web platform with no servers (20)
Recently uploaded
Recently uploaded (20)
Running web platform with no servers
- 1. Running Web Platform with no servers
- 2. Marcin Zasepa Tech Lead @ Homegate @zasepma
- 3. 1 2 3 4 AGENDA Homegate Story Architecture Examples of implemented services Summary
- 8. Status - beginning of 2018 Monolithic Application in outdated technology Only Few Engineers
- 9. Bring the value. Now! 1 2 3 Get more skilled engineers on board Make sure they can work efficiently = Micro-Service Architecture Make sure the work we do matters for the users = Serverless
- 10. Core of our Business: Help servers people to find the dream place to live Our Approach = Serverless Do not build / own anything which is not core of our business = Save time and make impact
- 11. Serverless Backend as a Service + Functions as a Service
- 12. Where to go?
- 15. Risks 1 2 3 Vendor will shutdown services, which you rely on Vendor will have an outage of the service Vendor will significantly increase the prices
- 16. Risk - Price Increase - Facts 01 02 03 04 According to the research from TSO Logic AWS has never increased prices AWS reduced the price over 67 times * (as of 24 September 2018) Examples: Recent Fargate Price In some cases reduction by 50%
- 17. 1 year later... 50 developers and growing Serverless services in production generating the value for the end-users
- 18. Technology
- 19. Service A Functions with Business Logic DB SNS Service B DB SNS Service C DB SNS SQS SQS Get all Events from The Past Subscribers with Filter Subscribers API Gateway Functions with Business Logic API Gateway Functions with Business Logic API Gateway System Architecture
- 20. SSO Provisioning Billing Special Purpose Accounts Assume Login Developers Service A Service B Test Stage Accounts Domain Management Authentication Shared Services Service A Service B Production Stage Accounts Domain Management Authentication Shared Services Assume Admin Role Creates / Updates GitLab CI/CD runners Domain Management AWS Cognito Assume Read Only Role Multi-Account Setup
- 21. Multi-Account Reasons Service isolation - APIs, Concurrency Limits, AWS APIs Limits1 Reduce blast radius - isolate failures2 Security - • Which AWS services can be used in the account • Who can login to the account and with what permissions 3 Demarcation of costs and Budget Controlling4
- 22. Validates Synchronously Step Functions (Enrichment) Agent PUBLISH API Gateway SNS Triggers Step Functions Event Name: Listing Published Event Name : Listing Updated Responsible for validation and getting the listing online Listings Importer Service
- 23. Upload Images (3rd Party) Translate in other langs (AWS Translate) Image Recognition Parallel Steps YES BRANCHING NO WAITPOLLING MAX 10 TIMES RETRY RETRYGeo-coding Aggregate Has extra products ? Write to search index (legacy) Is online ? Publish to SNS FINSH START Listings Importer Service
- 25. LISTINGS IMPORTER Publish New Listing Reverse query Elastic Search Creates queues per subscription SQS Map & Reduce START Wait Get Matches Send Step Functions Per User User Defined Time/Frequency Read QUEUE ARNSUBSCRIPTION Check Matches Matching of Subscriptions Price between 1000 And 2000 CHF Rooms number Between 1 & 3 aws:sqs:::queueSubscription2 aws:sqs:::queueSubscription1 Notification Service Notification Send SQS
- 26. Local Development What about testing / debugging services locally?
- 28. 1 2 3 4 LOCAL DEVELOPMENT Forget about local development: Emulation is not comprehensive and brittle Write more tests and run them to shorten the Feedback Loop Tests closer to production tell more Tests in cloud enforces better observability
- 29. DEV 1 Stage DEV 1 DEV 2 DEV 2 Stage Branch 1 Branch 2 Branch 2 Stage Branch 1 Stage GIT MASTER GITLAB CONTROLLED SERVICE TEST ACCOUNT Prod Stage GITLAB CONTROLLED SERVICE PROD ACCOUNT Personal Stacks Development Lifecycle Test Stage
- 30. Summary 1. Steep learning curve when going into cloud 2. Being an early adopters is challenging - Lack of people with production experience - Small community - Learning by doing - Lack of established patterns and good practises - Not much tooling
- 31. Summary - New features implemented within shorter time - Less time spent on maintenance of delivered features - Deliver innovative products making use of AWS Services