Architecture Deep Dives¶
These are the detailed specifications behind the Architectural Overview.
Read the overview first: it establishes the workflow engine, the entity dependency graph and the WebSocket event contract that every document here assumes. Each page below then specifies one subsystem in depth, and each is written as a set of rules to follow rather than a narrative — they are the constraints a change in that area has to satisfy.
| Document | Read it when you are… |
|---|---|
| Microservice Architecture | Changing the split between AICA and the shared @liferay/accelerator-sdk, or deciding which layer new code belongs in. |
| Workflow, State & Batching | Touching workflow state, batch correlation, WebSocket progress events, or how media is attached to entities. |
| Liferay API Constraints | Writing anything that filters or queries Liferay's Headless REST or GraphQL APIs. Explains the filter-in-memory mandate and the OData patterns that actually work. |
| E2E Verification & LDM Orchestration | Working on end-to-end verification, or on the Liferay Docker Manager (LDM) orchestration that drives it. |
| Frontend & UI Standards | Building or changing client-extension UI, and you need the layout, density and component conventions. |
Related¶
- Architectural Overview — start here.
- System Map — which client extension owns what.
- Upstream Bugs & Limitations — the platform defects some of these constraints exist to work around.
- Documentation index — all AICA documentation.
Last Reviewed: 2026-09-20