How do you work through the architecture — is there an architect in the team, platform, committee?

Depending on the size and structure of the team, the approach to architecture may vary. In my projects, there is usually a dedicated architect or technical lead who sets the main architectural decisions and standards.

If the team is large or the project is critical, an architectural committee or platform is created where architecture decisions are discussed and made, ensuring consistency and scalability of solutions.

In small teams, architecture is developed collaboratively with developers, with regular reviews and discussions. It is important to document architectural decisions and keep them up to date.

Main practices:

• Using architectural patterns and principles (e.g., microservices, CQRS, DDD)
• Conducting architectural reviews
• Formalizing requirements and constraints
• Constant knowledge sharing within the team

This approach helps avoid technical debt and ensures flexibility in project development.