Events, not rows
Every change is an event in a signed log. Watch them arrive, from which service, with what data.
Event sourcingA demo of kernable
Members borrow drills and ladders, stewards hand them out, late returns cost a fee. Three services in three languages work on it together: TypeScript for accounts and the API, Rust for the catalog and loans, Python for members, fees and reports. kernable keeps their events, checks every request, runs the loan's process and holds the personal data.
You get a club of your own: four people to be, a dozen items, loans in every state. Nothing leaves the demo (no mail is sent), the data is made up, and everything is erased daily at 03:30 UTC.
Every change is an event in a signed log. Watch them arrive, from which service, with what data.
Event sourcingOne active loan per item, unique item codes, no retiring what is lent: checked at commit, across services.
Unique keys and requirementsOwners, stewards, members: the kit's middleware decides every command and query in the kernel, and says why.
AuthorizationA loan handed out is followed: a reminder, then overdue, a late fee and a notice. Returning it ends the case.
Business processesPhone numbers and addresses live in the vault, not the log. "Forget me" erases them everywhere; the log stays whole.
ErasureA reservation ends by itself; item photos go to the kernel's file store; rate limits live in its cache.
SchedulingSign in once: the TypeScript, Rust and Python services each check the same token with their own kit.
The kitsDownload every event of your club. Run the demo yourself: the same code, from the repository.
ExportThe demo is a small, ordinary kernable application: the kernel from kernable.com/install.sh, the SDKs from npm, PyPI and crates.io, and the kit copied into each service with kernable-sdk add kit.
curl -fsSL https://kernable.com/install.sh | sh
git clone https://github.com/kernable/kernable-demo
cd kernable-demo && scripts/run.sh # then open http://127.0.0.1:8080