Good architects design their diagrams based on the target audience. Business people never enjoy your technical diagrams. Software developers admire who explain the why behind decisions.
This course navigates a real digital banking solution. Starting with the use cases analysis diagram all the way to components diagrams, explaining the why behind each design and architecture decision.
๐ Excalidraw diagrams included
Selected Diagrams
Business people never enjoy your technical diagrams. They appreciate clarity.
The first diagram a good architect shows is a simple Use Cases Analysis diagram โ not a fancy diagram with 37 microservices and 5 databases.
Draw your system as a box in the center, surrounded by its users and the other systems it interacts with.
Selected Diagrams
They want to know the components composing your system and how they communicate.
No direct access is allowed between Public and Data zones. All traffic flow through the Application zone, where strict rules apply.
Shows the components composing our system and how they communicate. Ensuring it supports the main use cases flow is necessary.
Selected Diagrams
Focus on components dependencies setup, and explaining the why behind decisions.
Decompose your system by volatility โ looking for sources of change. Makes sure components dependencies are clear.
Recording the decision ensures future team members understand why an api gateway was selected, and what trade-offs were accepted.
Selected Diagrams
The more details the better. Software developers admire who explains the why behind decisions.
The "Account Gateway" is an interface with CRUD methods that resides inside the business layer. It's the responsibility of the "Account Data Mapper" to implement this gateway interface.
If the payment gateway is slow or temporarily down, the request just stays in the queue until the worker can process it. Users arenโt stuck staring at a loading spinner anymore.