Diagram-to-microservices vs monolith-in-disguise
| Signal | Monolith disguised as microservices | Archiet approach |
|---|---|---|
| Service boundaries | Random services/ folders | Derived from application cooperation / component boundaries in blueprint |
| API contracts | Ad hoc REST | openapi.yaml + per-service routes aligned to genome |
| Data ownership | Shared database anti-pattern | Per-service models with explicit integration patterns |
| Deployment | Single container only | docker-compose.yml with service topology from Technology layer |
| Traceability | None | Matrix links diagram element → service → route → test |
How it works
-
Capture the architecture — Upload PRD, paste from Confluence/Lucidchart narrative, or describe services and integrations in the wizard. Microservice intent ("order service," "billing service," event bus) is extracted into the genome.
-
Review the formal model — Model-review UI shows proposed Application Components and relationships before lowering. Ambiguity is surfaced for confirmation — not guessed during render.
-
Render + gate — Choose stack (NestJS, FastAPI, Go, Java Spring Boot, etc.). Output includes inter-service HTTP/event contracts, health endpoints, and compose topology. Delivery gate blocks placeholder secrets and missing auth patterns.
What you receive
- Per-service codebase structure (stack-native modules)
- Shared API contract (
openapi.yamlor equivalent) docker-compose.ymlreflecting service topology- ADRs documenting sync vs async, database-per-service vs shared read models
docs/traceability/matrix.md— diagram element to code mapping
When microservice generation is the right ask
- Event-driven or multi-team systems where boundaries are already drawn on the diagram
- Compliance-heavy domains needing per-service audit scope (PCI, HIPAA segmentation)
- Platform migrations where the diagram exists before the greenfield code
When it is the wrong ask
- Early-stage products with one team and no operational maturity for distributed ops — start monolith-capable (Flask/Django/NestJS modular monolith) and split later using the same genome.
CTA
Bring the diagram semantics, not just the boxes. archiet.com/register — free plan.
FAQ
Do I need an ArchiMate file export?
No. PRD and structured requirements are the primary intake. ArchiMate fidelity is enforced in the genome; native EA imports are on the roadmap.
Which stacks support microservice layouts?
NestJS, FastAPI, Go (chi), Java Spring Boot, and .NET are common choices. Same genome can render different stacks for different deployment targets.
Does Archiet generate Kubernetes manifests?
Docker Compose is included in every web ZIP. Kubernetes/Helm patterns depend on genome infra flags — check your blueprint's deployment section.