Scaling Your Architecture for the Long Term
Download as PPTX, PDF2 likes746 views
The document discusses strategies for scaling software architecture, emphasizing the transition from monolithic to microservices architectures to enhance velocity and sustainability. Key lessons include the importance of modular architecture, event-driven communication, and quality assurance in achieving scalability. Continuous delivery and developer productivity are also highlighted as critical factors in maintaining effective software development practices.
Scaling Your Architecture for the Long Term
- 1. Scaling Your Architecture for the Long Term Randy Shoup @randyshoup
- 4. STARTING SCALING OPTIMIZING https://ittybiz.com/s-curve/ Single Team Rapid iteration @randyshoup Monolithic architecture
- 5. STARTING SCALING OPTIMIZING https://ittybiz.com/s-curve/ Many Teams Velocity and Scalability @randyshoup Microservice architecture Single Team Rapid iteration Monolithic architecture
- 6. STARTING SCALING OPTIMIZING https://ittybiz.com/s-curve/ Fewer Teams Efficiency and Sustainability @randyshoup Consolidating architecture Many Teams Velocity and Scalability Microservice architecture Single Team Rapid iteration Monolithic architecture
- 7. STARTING SCALING OPTIMIZING https://ittybiz.com/s-curve/ Fewer Teams Efficiency and Sustainability @randyshoup Consolidating architecture Many Teams Velocity and Scalability Microservice architecture Single Team Rapid iteration Monolithic architecture
- 8. STARTING SCALING OPTIMIZING https://ittybiz.com/s-curve/ Fewer Teams Efficiency and Sustainability @randyshoup Consolidating architecture Many Teams Velocity and Scalability Microservice architecture Single Team Rapid iteration Monolithic architecture
- 9. STARTING SCALING OPTIMIZING https://ittybiz.com/s-curve/ Fewer Teams Efficiency and Sustainability @randyshoup Consolidating architecture Many Teams Velocity and Scalability Microservice architecture Single Team Rapid iteration Monolithic architecture (~1% of all applications) SCALING
- 10. Architecture Evolution ā¢ eBay ā¢ 5th generation today ā¢ Monolithic Perl ļ Monolithic C++ ļ Java ļ microservices ā¢ Twitter ā¢ 3rd generation today ā¢ Monolithic Rails ļ JS / Rails / Scala ļ microservices ā¢ Amazon ā¢ Nth generation today ā¢ Monolithic Perl / C ļ Java / C++ ļ microservices
- 11. No one starts with microservices ā¦ Past a certain scale, everyone ends up with microservices @randyshoup ā¦ but most never reach that scale
- 12. Scalability Lessons ā¢Modular Architecture ā¢Event-Driven Communication ā¢Quality and Reliability ā¢Continuous Delivery
- 13. Scalability Lessons ā¢Modular Architecture ā¢Event-Driven Communication ā¢Quality and Reliability ā¢Continuous Delivery
- 15. Modular Architecture ā¢ One domain: One team: One / few service(s) o Organization ļ§ reflects ļØ Architecture (āConwayās Lawā) ā¢ Autonomy and Accountability o Team can independently design, develop, deploy, operate its service(s) o Team owns its service(s) end to end @randyshoup
- 16. Modular Architecture ā¢ Abstraction and Encapsulation o Fault isolation o āOptimalā technology stack o Performance optimization o Security boundary ā¢ Isolated persistence o All operations through published service interface o No backdoor access to database (!) @randyshoup
- 17. Modular Architecture ā¢ Strict interface discipline o Well-specified interface contract o Forward- and backward-compatibility o Testable and mockable ā¢ Domains grow and divide over time o Teams and services split like ācellular mitosisā ā¢ Service ecosystem o Services call others, which call others, etc. o Graph, not a strict layering @randyshoup
- 18. Scalability Lessons ā¢Modular Architecture ā¢Event-Driven Communication ā¢Quality and Reliability ā¢Continuous Delivery
- 19. Event-Driven Communication ā¢ Service publishes an event when state changes o Statement that some interesting thing occurred o Represents a semantic domain event ā¢ Events are a first-class part of a service interface ā¢ 0 | 1 | N consumers subscribe to the event @randyshoup
- 20. Event-Driven Communication ā¢ Decouple domains and teams o Abstract o Asynchronous ā¢ Decouple producer and consumer services o 0 | 1 | N consumers o Decoupled availability o Independent scalability o Reduced latency o Smoother load characteristics @randyshoup
- 21. Event-Driven Communication ā¢ Formal Interface o Well-specified event schema o Testable and mockable o Forward- and backward-compatibility @randyshoup
- 22. Event-Driven Communication ā¢ Standardized event bus o Event persistence and replays o Event ordering and duplication o Delivery guarantees o ā¦ ā¢ Do not roll your own (!) o This stuff is deceptively complicated o There are decades of research and experience o Itās probably not your core competency @randyshoup
- 23. Scalability Lessons ā¢Modular Architecture ā¢Event-Driven Communication ā¢Quality and Reliability ā¢Continuous Delivery
- 24. Quality and Reliability ā¢ Quality and Reliability are āPriority-0 featuresā ā¢ Equally important to users as product features and engaging user experience @randyshoup
- 25. Automated Testing ā¢ Tests help you go faster o Tests are āsolid groundā o Tests are the safety net ā¢ Tests make better code o Confidence to break things o Courage to refactor mercilessly ā¢ Tests make better systems o Catch bugs earlier, fail faster @randyshoup
- 26. Developer Productivity ā¢ 75% reading existing code ā¢ 20% modifying existing code ā¢ 5% writing new code https://blogs.msdn.microsoft.com/peterhal/2006/01/04/what-do-programmers-really-do-anyway-aka-part-2-of-the-yardstick-saga/ @randyshoup
- 27. Developer Productivity ā¢ 75% reading existing code ā¢ 20% modifying existing code ā¢ 5% writing new code https://blogs.msdn.microsoft.com/peterhal/2006/01/04/what-do-programmers-really-do-anyway-aka-part-2-of-the-yardstick-saga/ @randyshoup
- 28. Vicious Cycle of Technical Debt Technical Debt āNo time to do it rightā Quick- and-dirty
- 29. Virtuous Cycle of Investment Solid Foundatio n Confidence Faster and Better Quality Investment
- 30. Scalability Lessons ā¢Modular Architecture ā¢Event-Driven Communication ā¢Quality and Reliability ā¢Continuous Delivery
- 31. Continuous Delivery ā¢ Deploy services multiple times per day o Tighter feedback loop for build -> measure -> learn cycle o Faster time to value ā¢ More solid systems o Release smaller units of work o Smaller changes to roll back or roll forward o Faster to repair, easier to understand, simpler to diagnose @randyshoup
- 32. Continuous Delivery ā¢ Repeatable Deployment Pipeline o Low-risk, push-button deployment o Rapid release cadence o Rapid rollback and recovery @randyshoup
- 33. Feature Flags ā¢ Configuration āflagā to enable / disable a feature for a particular set of users o Independently discovered at eBay, Facebook, Google, etc. ā¢ More solid systems o Decouple feature delivery from code delivery o Rapid on and off o Develop / test / verify in production @randyshoup
- 34. Scalability Lessons ā¢Modular Architecture ā¢Event-Driven Communication ā¢Quality and Reliability ā¢Continuous Delivery