How do you approach architecture design? Where do you start?

When designing architecture, I start with understanding the requirements: functional, non-functional (performance, scalability, security), and constraints.

Next:

1. I identify the main components of the system and their interactions.
2. I choose appropriate architectural patterns (e.g., microservices, monolith, event-driven).
3. I work out interfaces and module boundaries for loose coupling.
4. I plan data storage and interaction with external services.
5. I consider scalability and fault tolerance.

In Go, it is important to consider language features: simplicity, efficient goroutine handling, standard libraries. For example, for web services, I often choose REST or gRPC, using contexts to manage timeouts and cancellations.

Ultimately, the architecture should be understandable, maintainable, and aligned with the project requirements.