Download to read offline
![Complexity is Almost Everywhere
Our Lives. Environment. [Software] Engineering](https://image.slidesharecdn.com/complexityblr-250812190855-4fd8d05a/75/Embracing-Complexity-in-Serverless-GOTO-Serverless-Bengaluru-11-2048.jpg)
![Refactoring is a process of changing a
software system.
Pre-cloud refactoring focused on the
software programs [code].](https://image.slidesharecdn.com/complexityblr-250812190855-4fd8d05a/75/Embracing-Complexity-in-Serverless-GOTO-Serverless-Bengaluru-75-2048.jpg)
![Complexity is Almost Everywhere
Our Lives. Environment. [Software] Engineering](https://crownmelresort.com/image.slidesharecdn.com/complexityblr-250812190855-4fd8d05a/75/Embracing-Complexity-in-Serverless-GOTO-Serverless-Bengaluru-11-2048.jpg)
![Refactoring is a process of changing a
software system.
Pre-cloud refactoring focused on the
software programs [code].](https://crownmelresort.com/image.slidesharecdn.com/complexityblr-250812190855-4fd8d05a/75/Embracing-Complexity-in-Serverless-GOTO-Serverless-Bengaluru-75-2048.jpg)
More Related Content
![[WSO2Con USA 2018] How to Build an Agile Enterprise](https://cdn.slidesharecdn.com/ss_thumbnails/3howtobecomeanagileenterprise-180717041313-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Embracing Complexity in Serverless! GOTO Serverless Bengaluru
Embracing Complexity in Serverless! GOTO Serverless Bengaluru
- 1. Embracing Complexity inServerless!
- 4.
- 5.
- 6. The human bodyis the most complex system ever created. The more we learn about it the more appreciation we have about how rich system it is. - Bill Gates
- 7. We’re born witha complex system. We Embrace It!
- 8. 1. Acknowledging Complexity Agenda 3.Managing Complexity 2. Understanding Complexity
- 9. #TheServerlessBook #TheSpeakerBook Engineer. Architect.Author AWS Serverless Hero Team Topologies Advocate SheenBrisals.com Sheen Brisals
- 10.
- 11. Complexity is AlmostEverywhere Our Lives. Environment. [Software] Engineering
- 12.
- 13. Self-hosted Systems …To…Cloud Computing
- 14.
- 15. Every application hasan inherent amount of complexity that cannot be removed or hidden. Instead, it must be dealt with either in product development or in user interaction. - Larry Tesler (Tesler’s Law) Law of Conservation of Complexity
- 16. Complexity is NotAlways Bad For Safety. High Performance. To Trust
- 18. Largest passenger airliner Range:14,800 km / 9,200 mi Speed: 903 km/h / 561 mph Altitude: 43,000 ft/ 13,000 m
- 19. Complexity is Oftena Necessity Serve Customers. Tech Evolution. Business Survival
- 20. Kitchen notification Food dispatch Customer notification Checkout Routeplanner Instore orders Online orders More! Stock Phone orders Loyalty Menu Driver tracking Payments Order management Personalization 3rd Party systems Customer service
- 21. Kitchen notification Food dispatch Customer notification Checkout Routeplanner Instore orders Online orders More! Stock Phone orders Loyalty Menu Driver tracking Payments Order management Personalization 3rd Party systems Customer service
- 22.
- 23.
- 24. Complexity is thebehavior of a system whose components interact in multiple ways, so possible interactions are difficult to predict. - Wikipedia Know it!
- 25. The Sign ofComplexity
- 27. The Sign Expressionof Complexity
- 28. It’s a nightmare! Ican’t touch it It’s hopeless It’s just a piece of ****
- 29.
- 30. Source: Balancing Couplingin Software Design
- 31.
- 32. The Two Sidesof Complexity
- 33.
- 34. Org, domain, department, team boundary Communicationline Monolith Microlith Lambdalith Functionlith Distributed System
- 35.
- 36. Simplexity Complex systems builtagainst simplicity principles for manageability! - Dr. Werner Vogels, at AWS re:Invent 2024
- 38. Decompose Complexity! To FindSimplexity!
- 39. Decompose the businessbefore decomposing the systems.
- 40.
- 41. Domain: Ecommerce Subdomain: Products Subdomain:Orders Subdomain: Payments Subdomain: Loyalty Subdomain: Personalization
- 42. Domain: Ecommerce Subdomain: Products Subdomain:Orders Subdomain: Payments Subdomain: Loyalty Subdomain: Personalization Content Catalogue Promotions Stock Next Best Actions Fulfillment Cart Recommenda tions Segments Checkout Rewards Earnings User Payments Fraud Prevention Payment Methods Members
- 43. Domain: Ecommerce Subdomain: Products Subdomain:Orders Subdomain: Payments Subdomain: Loyalty Subdomain: Personalization Content Catalogue Promotions Stock Next Best Actions Fulfillment Cart Recommenda tions Segments Checkout Rewards Earnings User Payments Fraud Prevention Payment Methods Members
- 44. Systems Distribution Domain Boundaries ResponsibilityBoundaries Team Boundaries Ownership: Codebases Cloud Accounts Service Contracts, Types Sync Async
- 45. Communication Complification! Prevent itat All Cost
- 46. Building an Event-DrivenArchitecture (EDA) without a brain is a gateway to a distributed monolith.
- 47. System A System B SystemC System D System E Event Broker Resources / Services Cross-account EventBridge Communication
- 48. System A System B SystemC System D System E
- 49. Some technologies arecomplex by nature. Often, we create complexity with simple technologies! Wikipedia
- 53.
- 54.
- 55. System A System B SystemC System D System E
- 56. System A System B SystemC System D System E Cross-Account Chaos that leads to a Distributed Monolith
- 57. Don’t let… Simplification causescomplification! Cross-account communication leads to cross-account chaos! Event drivers turn into event intruders! Essential Complexity becomes Accidental Complexity!
- 58. System B System C SystemD System E Domain Bus Enterprise Bus
- 59. Architecture Evolution Leverage thePower of Small
- 62.
- 63. Modularity Controls Complexity 1.Eliminates accidental complexity – avoiding poor design. 2. Encapsulates complex parts – preventing complexity spilling across. - Balancing Coupling in Software Design
- 64. Serverless microservice isa composition of cloud services knitted with infrastructure as code (IaC).
- 65. Protect with Patterns PreventComplexity
- 66. Design Patterns ServicePatterns Event-Driven Patterns Integration Patterns Cloud Patterns Storage Patterns Architecture Patterns Sustainability Patterns Serverless Patterns
- 67.
- 68. Anti-corruption Layer (ACL) Protectionfrom Complexity
- 69. Collaboration type Customer-supplier Separateways Cooperation Partnership Shared kernel Conformist Anticorruption layer Open-host service Patterns
- 70. ACL is anintegration pattern between two bounded contexts and acts as a translation layer to map data between two systems to protect their data models.
- 71.
- 72. If a boundedcontext conforms to a mess, it risks becoming a mess itself.
- 73. Continually Refactor! Don’t Stackup Complexity
- 74. Complexity sneaks inall the time and it is something you really need to control. - Dr. Werner Vogels, AWS re:Invent 2024
- 75. Refactoring is aprocess of changing a software system. Pre-cloud refactoring focused on the software programs [code].
- 76. Serverless refactoring isnot just about code rewrite but service re-wiring as well. Serverless allows refactoring at a granular level.
- 77. Program refactoring Infrastructurerefactoring Architecture refactoring Refactoring for cost Cloud service updates Uptake patterns & practices Refactor Complexity!
- 78.
- 79. Being disciplined: Prevent,Protect, & Refactor Avoiding event intruders to eliminate tangled systems Building modular systems that can evolve Decomposing complexity: From top down Acknowledging the need: When, Where, & Why Accepting the essential & avoiding the accidental Embrace complexity by…
- 80. Complexity is inherentin modern systems. Therefore, apply systems thinking and simplicity principles to manage it effectively. Embrace the Essential. Avoid the Accidental.
- 81. #TheServerlessBook #TheSpeakerBook Sheen Brisals Thank You! Engineer.Architect. Author AWS Serverless Hero Team Topologies Advocate SheenBrisals.com