Sprint26: Architecting for Scalability
In software, a "quick fix" today is often a technical debt nightmare tomorrow. In the third session of the Sprint26 series, we dive into the most critical phase of the lifecycle:
Software Architecture & Design.
Drawing from SWEBOK Chapters 2 and 3, we will explore the high-stakes decisions that define a system's lifespan. From choosing between a Monolith and Microservices to applying the SOLID principles, this session is about learning to think like a Software Architect.
What we’ll cover:
Architecture Styles: Comparing Layered, Monolithic, and Microservices patterns.
Design Fundamentals: Mastering SOLID, cohesion, coupling, and the separation of concerns.
The Price of Pivot: Understanding why architectural decisions are expensive to undo and how to make them with confidence.
The Codelab:
We’re moving from theory to blueprint. In this lab, we will:
Map out the Zetu Architecture Diagram.
Select and justify the Tech Stack for the project.
Design a robust Data Model (Groups, Members, Contributions, Payouts).
Draft a professional API Contract using the OpenAPI specification.