Appearance
Concepts
How kernable works and why. Each page is short; the tutorials show the same ideas in code, and the reference has the details.
| Page | Covers |
|---|---|
| Architecture | What the kernel does and what your processes do |
| Event sourcing in kernable | Aggregates, commands, events, and how it differs from CRUD |
| Domains | What a domain holds, its rules, how it relates to services, a code layout |
| How the pieces fit | Commands, events and queries; aggregates, read models, reactors, middleware and processes, and when you need a process |
| Order and consistency | One command per aggregate, listener order, settling, at-least-once delivery |
| Unique keys and conditions | Values unique across aggregates, commands that require a fact of another aggregate |
| Trust | Keys, grants, signatures, the hash chain |
| Compliance | The technical controls kernable covers for ISO 27001, SOC 2, the GDPR and others, and where it stops |
| Queries and middleware | Why every read goes through the kernel, and how checks fail closed |
| Business processes | Flows across commands, events and queries, run by the kernel and shown in its UI |
| Data over time | Event versions, formats, the vault, snapshots |
| Failures and recovery | What happens when something crashes |
| Compared with other systems | kernable next to event stores, frameworks and logs |
