Chronicle architecture

Chronicle

Kernel and protocol boundaries

Chronicle uses a .NET/Orleans actor-based kernel behind gRPC/HTTP surfaces and supports multiple event stores, namespaces, and persistent event-store subscriptions with outbox/inbox sequences.

🎯Use this page to locate

• the gRPC and HTTP protocol surfaces;
• the .NET/Orleans kernel;
• event-store and namespace runtime scopes; and
• persistent-subscription outbox/inbox sequences.

Runtime shape

Boundary	Owns in this diagram	Does not imply
Protocol surfaces	gRPC and HTTP entry boundaries around the kernel	Every client or tool uses both transports
Kernel	.NET/Orleans runtime	Horizontal scale, throughput, recovery, or topology guarantees
Event stores and namespaces	Separate runtime scopes	Client/provider parity or compatibility breadth
Persistent subscriptions	Event-store subscription state with outbox/inbox sequences	Guaranteed or exactly-once delivery

Related inspection surfaces

Chronicle Workbench provides a bundled local browser surface for authorized inspection of Chronicle runtime state and preview of supported projection behavior.

The Cratis CLI provides terminal workflows for inspecting and diagnosing Chronicle. These statements do not assign either tool to a specific transport in the diagram above.

Architecture is not an operational guarantee

This page does not claim horizontal scale, throughput, guaranteed delivery, exactly-once behavior, client/provider parity, durability tier, compliance, or support for every topology.

Continue

Chronicle overview

Start Chronicle locally and understand what the runtime owns.

Workbench

Inspect the running Chronicle instance from a local browser.

Cratis CLI

Use terminal inspection and diagnostic workflows.