Styles for Software Design and Architectures
Styles are the overall structures of an application and of distributed systems. Application architecture includes layered, hexagonal and clean designs, while distributed styles include microservices, event-driven systems and service-oriented designs. Each style puts boundaries and dependencies in different places and carries its own costs.
Stage: Architectural Styles · Part of the Software Design and Architecture roadmap · Last reviewed 19 November 2026
What to learn in Styles
- Draw a layered application and enforce one-way dependencies
- Compare clean architecture with hexagonal architecture
- State the operational costs that microservices add
- Describe an event-driven design with a broker
- Choose between orchestration and choreography for a workflow
- Decide a style from team size, domain and scaling needs
Styles interview questions
What problems come with microservices?
Network failures, latency, distributed data consistency, more deployment and monitoring work, and harder testing and debugging. They also need clear service boundaries. Without strong tooling and team ownership they can be worse than a well-structured monolith.
What is the dependency rule in clean architecture?
Source code dependencies point only inward, towards higher-level policy. Business rules do not depend on frameworks, databases or UI. Outer layers depend on inner abstractions, so details can change without touching the core.
Where Styles fits in the Software Design and Architecture roadmap
Styles belongs to the Architectural Styles stage (advanced level), which takes about 30 hours. Structure systems.
Other units in this stage
Back to the full Software Design and Architecture roadmap