Identity, users, products, and medication logs are split into dedicated service APIs.
What this system is
Project Evergreen is the backend platform for recording and managing evergreen usage data. It is built as a modular .NET system with separate APIs, containerized infrastructure, event-driven messaging, and Keycloak-based authentication.
Core pieces
Keycloak handles login, tokens, clients, and role-based access across the stack.
MongoDB stores application data while RabbitMQ supports asynchronous workflows.
The stack runs in Docker and includes Raspberry Pi deployment support and admin tooling.
Why it exists
The goal is to provide a maintainable backend with clear service boundaries, predictable local development, and a deployment path that works both in development and on constrained hardware.
- Clean Architecture keeps business logic isolated from transport and infrastructure concerns.
- CQRS separates commands and queries so behavior stays explicit.
- Docker Compose provides a repeatable runtime for local work and Raspberry Pi deployments.
- Operational tooling covers logging, metrics, authentication, and admin access.
What you can expect
This page is intentionally short. If you need the full technical setup, deployment notes, and service details, use the repository README and docs.