Previewkernable is not released yet: these docs describe work in progress, and things may change before 1.0.Not released yet.Request early access →
Skip to content

Concepts ​

How kernable works and why. Each page is short; the tutorials show the same ideas in code, and the reference has the details.

PageCovers
ArchitectureWhat the kernel does and what your processes do
Event sourcing in kernableAggregates, commands, events, and how it differs from CRUD
DomainsWhat a domain holds, its rules, how it relates to services, a code layout
How the pieces fitCommands, events and queries; aggregates, read models, reactors, middleware and processes, and when you need a process
Order and consistencyOne command per aggregate, listener order, settling, at-least-once delivery
Unique keys and conditionsValues unique across aggregates, commands that require a fact of another aggregate
TrustKeys, grants, signatures, the hash chain
ComplianceThe technical controls kernable covers for ISO 27001, SOC 2, the GDPR and others, and where it stops
Queries and middlewareWhy every read goes through the kernel, and how checks fail closed
Business processesFlows across commands, events and queries, run by the kernel and shown in its UI
Data over timeEvent versions, formats, the vault, snapshots
Failures and recoveryWhat happens when something crashes
Compared with other systemskernable next to event stores, frameworks and logs