Skip to content

ADR-002 - Project Structure

Statusaccepted
Date2025-04-01
Decision MakersDardan Bujupaj (AX)

Context

We need a basic project setup to start developing. The first decision we have to make is the repository structure of the project. In the past we have worked with monorepos as well as with individual repositories for each service/system.

Decision

We will use a single monorepo hosted on the Griesser Azure DevOps Environment.

Subfolders will be used to organize the project into different areas. Initially, following folders will be used:

  • frontend: store all code related to UI and frontend
  • backend: store all code needed for backend services and infrastructure
  • docs: store all documentation related to the project

Additional subfolders will be added as needed.

Consequences

The monorepo makes it easier to document, merge and deploy changes that span multiple systems.

Alternatives

  • Multiple Repositories: Would add additional overhead in managing all repositories.
  • Use AX Github Organization: This would have the downside of more complicated workflows for automatic deployments to Azure Cloud Services.