Spend less time on sharding logic
CamusDB partitions data and routes each write to the leader of the partition that owns its key range.
Why look closer
Four practical reasons to explore CamusDB
Keep concurrency rules in the database
Committed reads, conflict detection, and Serializable transactions help protect application invariants.
Make risky changes easier to reverse
Branch a database before an experiment, or relink a root database or table while its drop is still retained.
Run business logic next to the data
Load reviewed C# code into the server as SQL functions, row triggers, and transactional procedures. Every microservice and every operator session then follows the same rules.
See it in SQL
Explore real CamusDB workflows
Serializable is the default. Make it explicit when two updates must behave as one atomic transaction.
Read the consistency guideCommit related writes togetherConsistency
BEGIN;
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
UPDATE accounts SET balance = balance - 100 WHERE id = "A";
UPDATE accounts SET balance = balance + 100 WHERE id = "B";
COMMIT;
See the tools
Query and operate from the browser or the terminal
Query from the browserBrowse schemas, run SQL, and inspect results in the Web Console, without a SQL client on each machine.
Read the Web Console guide 
Read a plan as a flowRun EXPLAIN in the Web Console and see each operator as a diagram, from the source tables to the result.
Read about plan flows 
Check a node at a glanceOpen the HTTP port of a node to see its health, load, engine metrics, and slow queries. The dashboard is read-only.
Read the dashboard guide 
Work from the terminalcamus-cli runs SQL with syntax highlighting, autocompletion, and multiline statements.
Read the camus-cli guide 
Keep the catalog, editor, and results in viewcamus-cli --tui shows the catalog, the SQL editor, and the results on one screen.
Read about full-screen mode Evaluate it for yourself
See whether CamusDB fits your use case
Run the server locally from NuGet or Docker, or deploy a cluster with the Kubernetes Operator. Then follow the tutorial and review the current scope.