Technology Stack¶

This page defines the standard technologies used across NovaTrek Adventures microservices and platform infrastructure.

Application Runtime¶

Spring Boot¶

Spring Boot is the application framework for all NovaTrek microservices. It provides:

• Embedded web server — each service runs as a self-contained JAR with an embedded Tomcat server; no external application server required
• Auto-configuration — convention-over-configuration wiring for data sources, JPA, security, health checks, and metrics
• Actuator endpoints — standardized /actuator/health, /actuator/info, and /actuator/metrics endpoints used by Azure Container Apps health probes
• Dependency injection — constructor-based injection via Spring's IoC container
• Profile-based configuration — application.yml with environment-specific overrides (application-dev.yml, application-prod.yml)

Each service follows the standard Spring Boot project layout:

services/svc-{name}/
├── build.gradle.kts              # Dependencies, plugins, versions
├── Dockerfile                    # Multi-stage build → distroless JRE runtime
└── src/
    └── main/
        ├── java/.../
        │   ├── controller/       # REST endpoints (@RestController)
        │   ├── service/          # Business logic (@Service)
        │   ├── repository/       # Data access (@Repository, Spring Data JPA)
        │   ├── model/            # JPA entities (@Entity)
        │   ├── dto/              # Request/response DTOs
        │   └── config/           # Spring configuration (@Configuration)
        └── resources/
            ├── application.yml   # Spring Boot configuration
            └── db/migration/     # Flyway SQL migrations (V1__, V2__, ...)

Data Persistence¶

Each service owns its own PostgreSQL database schema — no shared databases between services. Schema migrations are managed by Flyway with versioned SQL scripts.

Hosting: Azure Database for PostgreSQL Flexible Server with continuous WAL archiving and 7-day point-in-time recovery.

Messaging and Events¶

Event schemas are defined in AsyncAPI specifications under architecture/events/. Services publish domain events (e.g., checkin.completed, reservation.confirmed) that other services consume without direct coupling.

Containerization and Deployment¶

Container Apps provides automatic scaling (0-2 replicas for dev, configurable for prod), built-in health probes against Spring Boot Actuator endpoints, and zero-downtime rolling deployments.

Observability¶

All services emit structured JSON logs and OpenTelemetry traces. Application Insights provides end-to-end request tracing across service boundaries.

Infrastructure as Code¶

See Platform Operations for the full pipeline inventory and deployment flows.

Security and Quality¶

Documentation and Architecture¶