Database architecture knowledge hub

Understand active-active databases, high availability, sharding and write coordination.

This hub explains the concepts that surround ShardronDB without treating them as interchangeable. Each guide defines the model, identifies operational tradeoffs, and shows where a coordination layer may or may not fit.

Start here: read the active-active database guide for the broad concept, then compare it with active-passive HA and multi-primary replication before reviewing the ShardronDB architecture.

Database architecture knowledge hub with active-active, sharding, high availability and coordination topics — Search-oriented technical content should answer real architecture questions before introducing the project-specific position.

Core guides

Seven connected topics for database architects, DBAs and platform teams.

The pages are intentionally connected through internal links so readers can move from a general problem to a specific design tradeoff.

Pillar guide

Active-Active Database Architecture

What active-active means, how writable nodes participate, where conflicts appear, and which questions should be answered before production use.

Read the guide → Comparison

Active-Active vs Active-Passive

Compare failover, capacity use, write paths, operational complexity, RTO/RPO considerations and infrastructure economics.

Compare architectures → Availability

Database High Availability

Review redundancy, failover, replication lag, consistency, backups, observability and recovery testing as one complete discipline.

Explore HA principles → Scale

Database Sharding

Understand shard keys, data ownership, request routing, cross-shard operations, rebalancing, backups and hotspots.

Understand sharding → Replication

Multi-Primary Replication

Distinguish multiple writable replicas from broader active-active application and coordination architectures.

Review multi-primary → Integrity

Primary Key Collision Prevention

Why globally unique identifiers matter across shards or writable nodes, and how ShardronDB separates client inserts from trusted internal flows.

Review PK safety → ShardronDB position

Database Coordination Layer

How a gateway-controlled layer can validate requests, route writes, coordinate identity generation and monitor relational nodes.

See the coordination model → References

Research and Official Documentation

Follow primary documentation for PostgreSQL, MySQL, MariaDB, AWS and architecture patterns used as context for public discussion.

Open references → Project architecture

ShardronDB Layer 1 Architecture

Move from general database concepts to the public ShardronDB model: gateway control, node-local ownership, backup placement and PK Guard.

View architecture →

Reading order

Use the topic cluster as an architecture decision path.

Begin with the availability requirement. Then decide whether the workload needs failover, read scaling, write scaling, data distribution, geographic locality, or a combination. Only after those requirements are explicit should a team compare replication, sharding, distributed SQL and coordination-layer options.

Suggested sequence

Define RTO, RPO and consistency requirements.
Compare active-passive and active-active operating models.
Determine whether data must be partitioned.
Define write ownership and conflict rules.
Plan identity generation, backups and observability.
Run a controlled architecture evaluation.