One big server vs. a network of small ones: the scaling architecture

One big server vs. a network of small ones: the scaling architecture

As a community grows, a fork in the road: keep everyone in one large server, or split into a federation of smaller themed servers?

What the evidence suggests
Lifecycle data on large communities shows a coherence ceiling — past some size (often cited loosely in the 10,000-50,000 range, hugely topic-dependent), a single server fragments anyway into cliques that don't interact, and the shared-culture value that made it good erodes. Networks of smaller servers preserve local density and belonging, but lose the cross-pollination and the simple discoverability of a single front door, and they multiply moderation overhead.

Why it happens
Dunbar-style limits on relationship density don't disappear because the member count grew. Beyond a threshold, members can't track who's who, identity-based reputation stops working, and the server behaves like a crowd, not a community.

The caveat
The threshold is wildly variable and partly an artifact of channel architecture — a well-segmented large server can postpone fragmentation that a flat one hits early. Size is a proxy, not the cause.

Comparison: stay single while shared culture still binds the whole; federate when cliques have already formed and you're just formalizing them. Telegram's folder/linked-channel model makes federation cheaper than Discord's.

Open question: is there an architecture that gets small-server density and big-network reach at once, or is that an inherent tradeoff?