Architecture
Orjanda keeps the distance between a business declaration and the surfaces around it intentionally short.
Package layers
Think in layers: the Document declaration, the Registry that knows about it, the derived persistence and API surfaces, and the admin and agent interfaces that operate on it.
Go structyour declaration
→Documentregistered model
→application surfacesderived output
APICRUD surface
↔Admin + agentcontrolled operations
one source of truth · multiple ways to work
Request lifecycle
A request enters through an application surface, is resolved against a registered Document, passes through the relevant permissions and operation rules, and then reaches the derived persistence layer. The response travels back through the same boundary.
Extension points
When generated behavior is not enough, extend at the boundary around your Document rather than duplicating the model. The exact extension interfaces are release-specific and should be read from the v0.1.5 source.
Last updated on