Serverless Functions OR Microservices
Download as PPTX, PDF0 likes375 views
The document discusses the evolution of legacy systems to microservices and serverless architectures, highlighting their successful persistence due to adaptability. It presents various technical considerations, offering insights on deployment, scalability, and maintenance from business, developer, and user perspectives. Ultimately, it emphasizes the need for a structured approach to connect multiple services while managing associated challenges.
Serverless Functions OR Microservices
- 1. The key thing to note is that legacy systems are only legacy because they’ve been successful enough to last this long.
- 3. legacy systems successful enough to last this long
- 4. Dreamer, Technology Enthusiast, Speaker, Trainer, People 1st, Microsoft Azure MVP, Crafter, Endava, Dreamer
- 10. Loosely coupled Deployable independently High maintainable and testable Organized on top of business needs and capabilities
- 11. Loosely coupled Deployable independently High maintainable and testable Organized on top of business needs and capabilities
- 15. Event triggered Ephemeral No infrastructure to manage Pays per execution
- 16. Event triggered Ephemeral No infrastructure to manage Pays per execution Writing a function that incorporates a business logic and deploy it
- 18. Execution Time Technology Stack Environment Scaling
- 20. Microservices • Short or long requests • Few seconds • Long execution time Serverless • Short life • Few seconds • Under 300s
- 21. Microservices • Short or long requests • Few secconds • Long execution time Serverless • Short life • Few seconds • Under 300s
- 22. Microservices • Short or long requests • Few secconds • Long execution time Serverless • Short life • Few seconds • Under 300s
- 24. Microservices Serverless Different stacks Limited tech stacks External dependencies Multiple stacks Legacy code Legacy dependencies
- 25. Microservices • Cluster • Nodes type • Container OS • OS Updates • Stack patches Serverless • No infrastructure configuration • Easy configuration • Focus on code • Write and deploy
- 26. Microservices • Same environment • Isolated from infrastructure Serverless • Environment agnostic • No dependencies
- 27. Microservices • Node spin-up latency • Warm-up Serverless • Scale on the fly • Fast warm-up • Dynamic scaling • No boundaries
- 29. Understand how to connect multiple microservices or functions to fulfil a business requirement Each service or collection of functions shall be seen as individual projects with their own team, pipeline and lifetime Middleware and internal communication
- 30. Understand how to connect multiple microservices or functions to fulfil a business requirement Each service or collection of functions shall be seen as individual projects with their own team, pipeline and lifetime Middleware and internal communication
- 31. Understand how to connect multiple microservices or functions to fulfil a business requirement Each service or collection of functions shall be seen as individual projects with their own team, pipeline and lifetime Middleware and internal communication
- 33. K8 Cluster
- 34. K8 Cluster
- 36. Business Perspective • Operation costs • Agility • Pay per run • Maintenance costs Developer Perspective • No system administration • Monitoring • No backend infrastructure • Scalable by design User Perspective • Faster updates • Pluggable • Cheaper • Flexible
- 37. Business Perspective • Vendor lock • Cost not predictable • Risks from 3rd parties providers Developer Perspective • Unclear best practices • Execution duration • Operational tools User Perspective • Wrong architecture can increase latency
- 38. Operating system Maintenance and support (e.g. operation system updates, security patches) Monitoring of the OS Deployment mechanism App Deployment & Configuration Infrastructure management
- 39. Need to use external services to be able to deliver the same functionality Overcome the limitations of disk space, RAM and execution duration Legacy dependencies to different stacks or systems
- 40. Need to use external services to be able to deliver the same functionality Overcome the limitations of disk space, RAM and execution duration Legacy dependencies to different stacks or systems Operating system Maintenance and support Monitoring of the OS Deployment mechanism App Deployment & Configuration Infrastructure management
- 43. Hybrid App Microservices Serverless Proxy Emit Request
- 44. Hybrid App Microservices Serverless Proxy Emit Request
- 47. To sum up
- 48. Bare-metal • Hardware as unit of scale • Physical hosting env is abstract IAAS • OS as unit of scale • Hardware is abstract PAAS • Application as unit of scale • OS is abstract Serverless • Functions as unit of scale • Language runtime is abstract
- 49. divide partitioning replicate/local redundancy sync data consistency Cost control tools Code sharing versioning Process teams Select interface, middleware and channel