First, database distributed increase resiliency and reduce risk. If a single-instance database goes offline (due to a power outage, machine failure, scheduled maintenance, or any other reason), all application services that depend on it will also go offline. In contrast, database distributed are often configured with copies of the same data across multiple instances, so if one instance goes offline, other instances can pick up the shortfall, allowing the application to continue running.

Different database distributed types and configurations handle outages differently, but in general almost all database distributed should be able to handle outages better than single-instance databases.

For this reason, database distributed are becoming an increasingly popular choice, especially for mission-critical workloads and any data that needs to remain available at all times.

Second, database distributed are usually easier to scale. In the context of a growing business, storage and compute demands on databases grow over time, and not always at a predictable rate.

Trying to keep up with this on a single-instance database is hard - you either pay more than you need so your database has "room to grow" in terms of storage and compute power, or you have to navigate regular hardware upgrades and migrations to ensure A DB instance always runs on a machine that can handle the current load.