Tell us about how tasks were distributed in your team and how architectural decisions were made.

Our team distributed tasks based on the specialization and experience of the members. Usually, tasks were divided into:

• Business logic development
• Working with the database
• Creating REST API
• Testing and documentation

Architectural decisions were made collectively at technical meetings. Typically, one or two experienced developers acted as architects, proposed options, and the team discussed the pros and cons. An important factor was adherence to SOLID principles, modularity, and scalability.

For example, when choosing between monolith and microservices, we evaluated load, deadlines, and support complexity. The decision was documented in the architectural documentation and discussed with the team and managers.