scalability

Scalability concerns how a system responds when usage changes, such as more concurrent visitors, larger datasets or additional background tasks. A scalable system can handle that change by adding or redistributing capacity without rebuilding the whole solution.

Two ways to scale

Vertical scaling gives one machine more computing power, memory or storage. This is often straightforward, but one machine has limits. Horizontal scaling distributes work across more machines or processes. It usually requires more from the architecture because data and tasks must be distributed correctly.

Scaling down is also part of scalability. When demand falls, unused capacity can be reduced. Particularly in cloud infrastructure, this helps match resources to actual usage.

More than extra servers

Scalability depends on more than infrastructure. A slow databaseGlossary · In briefdatabaseA database is a structured collection of data that software can store, retrieve and modify. A database management system controls access to that data.Read more, external integration or heavy process can still become a bottleneck. Measurements and monitoringGlossary · In briefmonitoringMonitoring systematically tracks software, infrastructure or processes through measurements and checks. Deviations can trigger alerts so an administrator can investigate.Read more reveal where the limit lies.

A scalable design does not need to support millions of users from the start. It mainly needs to fit expected growth and peak loadGlossary · In briefpeak loadPeak load is the temporarily high demand on a system when many users, requests or tasks need capacity at the same time.Read more. This leaves room for expansion without adding unnecessary capacity and complexity in advance.