Evaluate Dex

These pages help you decide whether Dex fits your system. Read them in order, or go straight to your question.

Why Dex? shows the problem with an order process that breaks halfway, and how Dex models it as a Flow of Steps.
Dex vs. Databases builds the same process on a database, then with queues and an outbox, then as a Flow, and lists the duties that stay with you.
Dex and Your Database shows how a Step writes to the database you already have, and when to copy Flow data to PostgreSQL.
Dex vs. Other Engines maps Dex to replay-based engines, journal-based runtimes, and database-backed libraries, and says when another tool fits better.
Performance gives measured throughput and latency on one node with S3, what it costs to run, and how to repeat a result.
Limits lists what can surprise a team in production, the release status, and the license.
Failover and Deploys shows what happens when the server or a Worker stops, and how to deploy new code while Flows are open.
Correctness and Expressiveness gives a machine-checked proof of what a crash can and cannot change, and what Dex can express.