Architecture overview

Balyze is designed as a backend-first SaaS, with a strong emphasis on domain clarity, long-term maintainability, and controlled technical complexity.

At its current ALPHA stage, the architecture focuses on building a solid foundation rather than optimizing for scale or performance prematurely.

Architectural goals

The architecture of Balyze aims to:

The system is intentionally simple, but not simplistic.

Balyze follows a classical MVC approach, extended with explicit domain-oriented layers:

Models
Represent persisted domain entities and their relationships.
Services
Encapsulate business logic and domain rules.
All non-trivial actions are implemented at this level.
Policies / Gates
Handle authorization and ownership rules, independently from business logic.
Enums
Represent finite domain states and transitions (e.g. application lifecycle).

Controllers remain thin and primarily orchestrate requests by delegating to services.

Domain rules are defined before implementation details.

Examples include:

These rules are documented explicitly and enforced consistently at the service layer.

Each layer has a single responsibility:

This separation reduces coupling and makes future changes more predictable.

At the ALPHA stage, the following concerns are intentionally deferred:

These aspects will be addressed progressively once the core domain is validated.

The architecture is expected to evolve, but core principles are intended to remain stable.

Structural changes should be driven by:

Premature abstraction is avoided by design.