Elemental Architecture

An organizational application architecture: the compositional elements a program is built from and the rules that bind them, independent of language. What the elements are and how they relate is defined here; how each element is implemented emerges at its first consumer and is documented in the repository that builds it.

The architecture's purpose is optimizing supply-chain boundaries. A minimal, deliberate dependency surface is one of its core principles, not a posture its standards choose privately. The boundary works in two dimensions: it mitigates what a dependency admits into the architecture, and it establishes the clean maintenance boundaries that keep capabilities flexible, scalable, and maintainable for the long haul. A handful of deliberately sourced dependencies can be held pinned and current; fifty cannot. The minimal-footprint principle states this purpose in principle form; an implementing standard draws its own dependency line as an enhancement of it, tightening and never loosening. A framework-heavy standard in the same language is not a competing implementation of Elemental; it does not implement Elemental at all.

The architecture keeps two inheritances: the separations of domain-driven design and the query/command operation model of CQRS. It deliberately drops the vocabulary DDD accumulated around them (aggregates, value objects, repositories, command buses), because that vocabulary existed to keep monolithic applications coherent. In a system of many narrowly scoped services, each application is small enough that the six elements below describe its entire design. "Feature" was considered as a further element and rejected: every candidate feature is one domain, a Domain Service and the Entities it composes, so the term would only relabel what the elements already describe. Features stay informal prose.

The elements

Top to bottom:

The rules

Principles

The architecture's principles are cataloged at principles/; every standard and module beneath the architecture satisfies them, and a lower level may tighten one and never loosen it:

A note on "Domain Service"

"Domain Service" deliberately narrows a term domain-driven design uses more broadly: here it is always the public interface over one domain, rooted in one Entity. Engineers onboarding from a DDD background should read the definition above rather than assuming the inherited, broader one.

Implementing standards

A standard declares the architecture it implements in its definition. Go Elemental is the first implementing standard; its web service template is the first code expression of the elements.

Keyboard shortcuts

Settings