mirror of
https://github.com/fleetdm/fleet
synced 2026-05-24 09:28:54 +00:00
1e6e8b1a74
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> Added MDM components to our high level architecture doc. Is it too much? I could see it going either way. My argument for it not being too much is that ultimately it's all very tightly intertwined now and I almost feel like the big picture isn't complete without it --------- Co-authored-by: George Karr <georgekarrv@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| mdm | ||
| modular-monolith | ||
| orchestration | ||
| security-compliance | ||
| software | ||
| high-level-architecture.md | ||
| infrastructure.md | ||
| README.md | ||
Fleet architecture documentation
This directory contains high-level architecture documentation for Fleet.
Overview
- High-level architecture - Overview of Fleet's architecture
- Infrastructure - Documentation on Fleet's infrastructure
- Modular monolith - Fleet's transition to a modular monolith with bounded contexts
Product group architecture
Each product group has its own architecture documentation:
- MDM Architecture - Architecture documentation for MDM
- Orchestration Architecture - Architecture documentation for Orchestration
- Software Architecture - Architecture documentation for Software
Architectural Decision Records
For significant architectural decisions, we use Architectural Decision Records (ADRs) to document the context, decision, and consequences.