Introduction

{% embed url="https://github.com/Elders/Cronus/issues/281" %}

Welcome to the Cronus Manual!

{% embed url="https://docs.google.com/presentation/d/1illYm0Mok2ADVb8KRMPwiB-rh2n5ZPu2r5pOLkyFpTc/edit?usp=sharing" %}

{% embed url="https://viewer.diagrams.net/?highlight=0000ff&layers=1&nav=1#RddHNEoIgEADgp%2BGuy4zV2awunTx0ZmQTZtB1kEbr6dMBM8Y6sXy7sPwwnjfj2YpOXUmiYZDIkfEjA4Akg2mY5eklTSFIbbUMtkKpXxgwCfrQEvuo0BEZp7sYK2pbrFxkwloa4rI7mbhrJ2rcQFkJs9Wblk553cNu9QvqWi2d0%2BzgM41YisNNeiUkDV%2FEC8ZzS%2BR81Iw5mvn1lnfx605%2Fsp%2BDWWzdjwVTsO49TaIv4sUb" %}

{% embed url="https://docs.google.com/drawings/d/1DoH08MBLwAa2ERJxVMRsy3HLC8pxMNZ5Nu8V9jAFxuE/edit?usp=sharing" %}

Cronus provides the Cronus Framework to help build applications centred on three core concepts - CQRS (Command Query Responsibility Segregation) / Event Sourcing and DDD (Domain Driven Design).

While many types of applications can be built using Cronus, it has proven to be very popular for microservices architectures. Cronus provides an innovative and powerful way of sensibly evolving to event-driven microservices within a microservice architecture.