Based on the requirements for the new project (framework independence, separate deployment of modules, ease of development in a single repository), what questions would you ask and what architecture would you choose?

Initially, it is important to clarify a few points:

• Which modules are planned to be developed and how do they interact?
• What technology stack is preferred or acceptable?
• Are there requirements for performance and scalability?
• What level of isolation and security is necessary for the modules?
• Is there a plan to use micro frontends or a monorepo?

Based on the requirements:

1. Framework independence — it is advisable to choose an architecture based on Web Components or standards not tied to a specific framework.
2. Separate deployment of modules — a micro frontend architecture is suitable, where each module is deployed and updated separately.
3. Ease of development in a single repository — a monorepo with tools like Nx or Lerna can be used, which allow managing dependencies and builds.

Example architecture:

• Each module is a standalone application or component implemented using Web Components or a framework of the team’s choice.
• The common shell loads and integrates modules dynamically.
• Use of a modular system (ES Modules) for code loading.
• CI/CD is configured for deploying each module separately.

This approach ensures independence, flexibility, and ease of development.