Download to read offline
More Related Content
![Choosing the right messaging service for your serverless app [with lumigo]](https://cdn.slidesharecdn.com/ss_thumbnails/choosingtherightmessagingserviceforyourserverlessappwithlumigo-201217193955-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Enterprise Serverless Adoption. An Experience Report
Enterprise Serverless Adoption. An Experience Report
- 1. Enterprise Serverless Adoption AnExperience Report Sheen Brisals The LEGO Group sheenbrisals
- 2. Sheen Brisals Engineer. Architect.Writer. Speaker. Leader. AWS Serverless Hero @ The LEGO Group Ex Oracle, Hewlett-Packard, Omron, TATA sheenbrisals sbrisals.medium.com sheen-brisals
- 3. ▪ Serverless @LEGO.com ▪ Growing Serverless Teams ▪ Serverless Best Practices ▪ Serverless & Sustainability Agenda
- 4.
- 6.
- 9. January 2022 More than20 Squads More than 100 Engineers More than 80 Microservices More than 350 Lambda functions
- 10. Summer 2021 More than12 Squads More than 80 Engineers More than 60 Services More than 300 Lambda functions
- 11. Summer 2019 Just 2Teams Around 20 Engineers Around 20 Services Under 100 Lambda functions
- 12. November 2018 Just 2Teams Around 20 Engineers Around 10 Services Around 50 Lambda functions
- 13. Spring 2018 2 Teams 10Engineers Zero Serverless
- 14. September 2018 First Lambdafunction VPC Node.js + React Elastic Beanstalk container Server contents Server contents Tax Products CRM Fulfillment Rewards AWS Cloud SaaS VPC Gateway Server contents Corporate data center Amazon API Gateway AWS Lambda function
- 16.
- 17.
- 18.
- 19. Team Environment organisation innovative experimentation trust motivation ownership responsible risk taking selfbelief self-govern fast action
- 20.
- 21. Pilot Engineer(s) Attitude Aptitude architecture security programming passionfor tech hunger to learn ‘can do’
- 22.
- 23. Team Enabler coach mentor Role techie passionate Characteristics architectcommitted engineer business friendly leader agile
- 24.
- 25.
- 26.
- 27.
- 28. Serverless Mind Serverless requiresa "mind-shift" to see the products as event-driven orchestration of managed services, knitted with infrastructure code, to bring the best value
- 29.
- 30. The Victories Team Outcome PoC MVP Servicein PROD Trust Confidence Respect Stakeholder Opinion
- 31.
- 32. The Awesome Team ownership culture community contributions engineersas architects releases features velocity awesome team DevOps practices
- 33. Serverless Engineer “A softwareengineer who is innovative, efficient, capable of building secure, cloud first and cost effective functional solutions using managed services.”
- 34.
- 35. Trim Distractions Distractions conflicts of interest communication hurdles over-engineering practices re-invention mindset nocustomer benefit no business value wandering tech thoughts process overload low productivity complacency always awesome
- 36.
- 37. The Retrospective tech debt reduction technology uptake service refactoring process changes team adjustments bonding activities training& workshops team hackathon experts sessions
- 38.
- 39. New Teams awesome team amazingteam A team super team
- 40.
- 41.
- 42. Cloud provider Framework Team Skills CI CD Language Devtools Security Data Agree on Guiding Principles
- 43. Agree on GuidingPrinciples • Development language • Use of managed services • Framework • Cloud account structure • Code repository • Solution design process • API guidelines • Service contracts
- 44. Perform Solution Design •Technical agility • Engineering clarity • Business visibility • Service longevity https://bit.ly/3tPEe7D
- 45. Incremental & IterativeApproach design review agree develop • Start small and evolve • MVP mindset • Solution first. Perfection next • Iterate and improve • Speed matters in business
- 46. Agile, iterative, andautomated serverless development is like a gravity defying take-off. Once launched, there’s no stopping! Sheen Brisals
- 47. Security & ThreatModelling • Security from the start • Data privacy • GDPR & Compliance • Service protection https://qrgo.page.link/aiQsb
- 48. DevOps and Automation •Account separation • Infrastructure as Code • Grow CI/CD pipeline • Inspire a DevOps culture • Service ownership
- 49.
- 50. Well-Architected Service Audit •Service criticality • Alarms & alerts • Structured logging • Release settings - canary • Serverless Lens audit • Security & privileges • Data privacy measures • Service documentation
- 51.
- 52. Sustaining is aprocess of keeping something going for a prolonged period by nurturing it with a continuous provision of nourishment to ensure its growth and existence.
- 53. Serverless Sustainability Triangle Cloud ProductProcess Sustainability in Serverless
- 54. Serverless Sustainability Triangle Cloud ProductProcess Sustainability in Serverless Building sustainable serverless solutions Following sustainable development processes Applying cloud best practices Sustainability of the cloud Sustainability in the cloud
- 55. Sustainable Products • Domains,context, and boundaries • Independent smaller microservices • Defined contracts Modularity • Loosely coupled services • Event-driven architecture • Asynchronous communication Extensibility • Structured logging • Distributed tracing • Measurable metrics Observability
- 56. Sustainable Processes Follow agiledevelopment practices – be flexible and practical Adapt lean principles - to reduce waste Change the throw-away prototype or PoC culture – think product longevity Evolve the product in iterations – minimum viable to maximum valuable product Embrace refactoring as part of the development cycle – to keep the solution fresh Automate all possible processes – promotes just the required resources usage
- 57. Sustainable Environment: Cloud Sharedresponsibility between us (customers) and AWS
- 58. Sustainable Environment: Cloud Renewable energy Efficientpower & cooling Sustainability of the Cloud Development language Data stores & policies Sustainability in the Cloud Server population Right sizing resources Shared resources On-demand scaling Compute & storage tiers options Managed services AWS Customer
- 59. Data and storage pattern Compute and infra pattern User behaviour pattern Devand deployment pattern Software architecture pattern Sustainable Environment Best Practices
- 60. Cloud Best Practices:User Behaviour Pattern • Greener region selection • Plan for high volume user events • Clear temporary user content • Deploy services closer to the customer base • Perform caching at the edge
- 61. Cloud Best Practices:Software & Architecture • Adopt async & event-driven architecture • Queues and buffer to smoothen load • Design queries to fetch just the required data • Run low priority task during off peak • Run jobs during the day when carbon intensity for power is lowest
- 62. Cloud Best Practices:Compute & Infrastructure • Optimise lambda functions • Vary lambda resources as per the need • Arm/Graviton2 processors for Lambda • Use managed services • Prefer services that scale horizontally
- 63. Cloud Best Practices:Data & Storage • Classify data and tag resources • Right datastore for right data & access pattern • Remove unwanted data with TTL & policies • Move data to apt storage as per access frequency • Avoid high volume data movement across regions
- 64. Cloud Best Practices:Development & Deployment • Maximise dev & test environment utilization • Keep systems up to date • Automate pipeline resource lifecycle • Use managed device farms
- 65. ▪ Start small& simple and scale up ▪ Grow your engineers & teams ▪ Guardrails and best practices ▪ Sustainability of product, process, and the world To Close…
- 66.