Elara is a microservices backend focused on inventory management and unit-of-measure governance.

This project was conceived and developed autonomously by @andresbetov, with a strong focus on production-grade software practices, long-term maintainability, and technical clarity.

Elara currently implements two core business capabilities:

1. Inventory domain (inventory-service): inventory item lifecycle management (create, update, delete, get by id, pagination, and search).
2. Unit-of-measure domain (unit-of-measure-service): UOM catalog and UOM status lifecycle used as reference data for inventory validation.

The rest of the platform services support these domains as infrastructure components.

Detailed contracts and examples are documented in each service repository:

• inventory-service README
• unit-of-measure-service README

Elara is structured as a decoupled Spring Cloud ecosystem where each service owns a specific responsibility:

This separation of concerns enables independent evolution, safer deployments, and clear service ownership boundaries.

1. Clients call api-gateway.
2. Gateway resolves target services through discovery-service.
3. Services bootstrap configuration from config-service, backed by centralized-configuration.
4. inventory-service validates UOM dependencies against unit-of-measure-service through discovery-aware service communication.
5. Secrets are sourced via Vault integration in supported profiles.

This model keeps domain services focused on business rules while platform services handle cross-cutting infrastructure concerns.

• Layered architecture (controller -> service -> repository -> mapper -> DTO), with explicit boundaries and low coupling.
• Strict validation at API and persistence levels (jakarta.validation, entity constraints).
• Centralized error contracts using typed exception hierarchies and global handlers.
• OpenAPI-first documentation with reusable schemas and concrete JSON examples.
• Testing discipline across controller, service, repository, mapper, exception, and utility layers.
• Build-enforced quality gates with JaCoCo thresholds in Maven lifecycle.
• Externalized configuration and secret management (Config Server + profile-specific config + Vault integration).
• Production-friendly observability patterns via structured logging conventions and explicit operational contracts.

These are implementation-level decisions that directly improve reliability, maintainability, and scalability.

• Quality gates in build (JaCoCo thresholds enforced in Maven lifecycle):
  • inventory-service pom.xml
  • unit-of-measure-service pom.xml
• Testing standards and patterns:
  • inventory-service TESTING_GUIDE.md
  • unit-of-measure-service TESTING_GUIDE.md
• Service-level architecture and runtime contracts:
  • api-gateway README
  • config-service README
  • discovery-service README
  • centralized-configuration README

This README intentionally describes only what is currently documented and implemented in this architecture scope:

• inventory item management,
• unit-of-measure and unit-of-measure-status management,
• the platform services that support those domains (gateway, discovery, config, centralized configuration).

It does not claim additional implemented business modules in this profile beyond that scope.

Automatically synchronized list of repositories and latest commits in the Elara organization.

Last updated: 4/13/2026, 1:48:54 AM

The commits table above is maintained by an automated updater in the .github repository, using GitHub App authentication and targeted README updates.
Implementation details are available here: elara-app/.github/src.

For readers who want full technical context, this project is accompanied by a 281-page guide that documents the architecture from zero, explains why each major decision was made, details trade-offs (pros/cons), and describes the quality framework and engineering standards applied across implementation: Creating Elara App - Software Development (The document is in Spanish).