Showcase and architectures
The best way to understand Cratis is to follow a working shape. This page collects runnable samples and architecture patterns that show how the pieces fit together.
Run the samples Clone runnable examples from minimal Chronicle quickstarts to a full-stack library app.
Build the full-stack feature Walk through command, event, projection, query, and React screen in one feature.
Choose your adoption path Use the adoption guide to decide whether to start full stack, Arc-only, Chronicle-only, or one bounded slice.
Reference shapes
Section titled “Reference shapes”| Shape | Use when | Start with |
|---|---|---|
| Full-stack Cratis | You are building a new information system and want the full command, event, read model, and React loop. | Build a full-stack feature |
| Chronicle-first service | You need a durable event history before you need a frontend. | Chronicle getting started |
| Arc over current-state storage | You want typed commands, queries, and generated React proxies without event sourcing yet. | CQRS without event sourcing |
| Components frontend | You already have Arc proxies and want forms, dialogs, tables, and styling conventions. | Components getting started |
| Existing system adoption | You want to introduce Cratis one bounded context or frontend/backend boundary at a time. | Adopting Cratis |
| Operational inspection | You need to inspect events, observers, failed partitions, projections, and jobs. | CLI |
Sample applications
Section titled “Sample applications”- Console quickstart - the smallest event-sourcing loop.
- ASP.NET Core quickstart - Chronicle behind a web API.
- Library app - a full-stack vertical-slice application with Arc, Chronicle, Components, and tests.
Add your example
Section titled “Add your example”If you have a sample, architecture note, migration story, or teaching example that would help other teams, use Feedback and suggestions or open a documentation issue.