Scaling Software Architecture: 101 and Best Practices

Transcript

1. Scaling Software Architecture 101 and Best Practices
2. Disclaimer Presentations are intended for educational purposes only and not to replace independent professional judgment. The views and opinions expressed in this presentation do not necessarily reflect the official policy or position of blibli.com. Audience discretion is advised.
3. Who am I? • Alex Xandra Albert Sim • Principal Research and Development Engineer at blibli.com • alex.sim@gdn-commerce.com • bertzzie(.sim)
4. What is SOFTWARE ARCHITECTURE?
5. The highest-level breakdown of a system into its parts
6. System Parts Academics IS Finance IS Bank A Bank B HR IS IT IS
7. Structural Elements
8. Interfaces
9. Architectural decisions are hard to change
10. Multiple architectures in one big system is normal
11. Architecture changes over time
12. the GOALS OF ARCHITECTURE
13. Expose the structure of the system Hiding the implementation details while
14. Realize all of the use cases and scenarios
15. Address the requirements of various stakeholders
16. Handle both functional and quality requirements
17. TYPES OF SOFTWARE ARCHITECTURE (WEB)
18. Monolithic Architecture Image source: http://bits.citrusbyte.com/microservices/
19. Monolithic Architecture Pros • Cross cutting component integration is easy • Communication between layers / components are fast Cons • Long development cycle • Scaling problem • 1 problematic part == whole app down
20. Microservice Architecture User Membership System Order System Messaging System Payment System API Gateway
21. Microservice Architecture – User Registration User Membership System Order System Messaging System Payment System API Gateway
22. Microservice Architecture - Purchase User Membership System Order System Messaging System Payment System API Gateway
23. Microservices Architecture Pros • Fault tolerant • Service independence means fast and easy development / deployment • Easier to add / remove stuff Cons • Operational complexity is VERY high • Contracts between services are hard to maintain • Hard to get right. Lot of teams fall into “distributed monolith” rather than “microservice”
24. Event-Driven Architecture User API Gateway Membership System Order System Messaging System Payment System Event Broker
25. Event-Driven Architecture – User Registration User API Gateway Membership System Event Broker Order System Payment System Messaging System 1 2 3 4
26. Event-Driven Architecture - Purchase User API Gateway Event Broker Membership System Order System Messaging System Payment System 1 2 3 4 4 4
27. Event-Driven Application Pros • Very low coupling • Simple to setup and scale Cons • Data consistency is hard. Eventually consistent instead of ACID • Complexity is through the roof • Flow of program is hard to trace / learn
28. Why and How to do SCALING ARCHITECTURE
29. Scalability Capability of a system to handle work that scales linearly with the resources it uses.
31. How to Scale: Vertical Scaling 2 CPU 4 GB RAM 200 IOPS storage 100 Mb/s Network 8 CPU 16 GB RAM 400 IOPS storage 1000 Mb/s Network
32. How to Scale: Horizontal Scaling 2 CPU 4 GB RAM 200 IOPS storage 100 Mb/s Network 2 CPU 4 GB RAM 200 IOPS storage 100 Mb/s Network 2 CPU 4 GB RAM 200 IOPS storage 100 Mb/s Network 2 CPU 4 GB RAM 200 IOPS storage 100 Mb/s Network 2 CPU 4 GB RAM 200 IOPS storage 100 Mb/s Network
33. How to Scale: Horizontal Scaling (2) Load Balancer Service A Service A Service A Service A
34. Evolving Architecture to Scale Monolithic Microservice Event-Driven
35. Monolithic to Microservice: Step 1 Load Balancer Service A Service A Service A /cart /login /search Database
36. Monolithic to Microservice: Step 2a Load Balancer Service B Service A Service A /cart /login /search Database Database
37. Monolithic to Microservice: Step 2b Load Balancer Service B Service A Service C /cart /login /search Database Database Database
38. How to Split Services? • From the least depended ones • By business function • Replace one by one • Potentially need to re-org too! • Test extensively per new service deployment!
39. QUESTION AND ANSWERS
40. Thank You