Learn the truth.

The nature of non-distributed databases means that sharding for the purposes of scaling or performance has some pros and cons. Sharding breaks the developer expectations around strict serializability, externalizable behaviors and overall ACID system attributes. This creates more complexity in the application code to attempt to cope – and leaves developers working to overcome database problems. Learn more about why, how – and what to do about it.

Register for access

    Thank you for registering!

    You’ve already registered.


    This is a technical analysis of the nature of sharding non-distributed systems. It includes a looking at primary key selection, rebalancing considerations, and the effect on transactional consistency.

    There are alternatives.

    Regatta is the first of a new category of database system: OLxP databases. OLxP systems are modern cloud native distributed architectures. OLxP scale linearly without conceding any loss of consistency like what you see with sharded systems. OLxP systems are extremely performant and also extremely efficient. Unlike anything before them – OLxP systems can perform complex analytics directly on transactional data with no ETL, Datapipelines, time delay.

    Tell non-distributed legacy systems to go shard themselves.

    Learn more, subscribe and try Regatta for yourself!

      Thanks for subscribing!

      You’re already a subscriber – thank you!

      Skip to content