Skip to main content

Scaling & Production

This module answers two questions every serious project reaches: how does Cardano scale, and how do I take my dApp to production. The first is about throughput and architecture; the second is about reliability, security, and infrastructure. Both build on everything in the earlier modules.

How Cardano scales

Scaling isn't one thing. Cardano scales at several layers, and the right approach depends on your workload.

Layer 1: the base chain

The base chain has bounded capacity per block, so on Layer 1 you scale by using blocks efficiently rather than by sending more independent transactions at a shared piece of state. Because the eUTXO model makes a UTXO spendable only once per block, high-contention designs (like a single shared pool) need the concurrency patterns covered in DeFi on Cardano: order batching (many user intents executed in one transaction) and pool sharding (state split across many UTXOs so transactions run in parallel). At the protocol level, the Ouroboros roadmap includes Leios (input endorsers) aimed at substantially higher throughput.

Layer 2: Hydra

When you need near-instant, near-free, high-frequency transactions, gaming, micropayments, real-time interactions, you move them off the base chain into a Hydra Head: a state channel where a known set of participants transact thousands of times per second, settling back to Layer 1 only to open and close. You pay L1 cost once to open and once to close; everything inside is fast and free.

NeedReach for
More throughput against shared state on L1Order batching / pool sharding
Instant, free, high-frequency transactions among known partiesHydra (Layer 2)
Higher base-layer throughput (future)Ouroboros Leios (roadmap)

Taking a dApp to production

Working on testnet is not the same as running in production. Two pages cover the rest:

  • Going to production: the checklist before you ship to mainnet: testing, security, reliable transactions, optimization, and key safety.
  • Production infrastructure: the stack that serves your dApp the chain: managed APIs vs running your own node, indexers, and how to choose.

Next steps