What Drives the need for Database sharding? DATABASE sharding

Wio bottleneck

http://www.agildata.com/database-sharding/

What Drives the need for Database sharding?

Database Sharding is a highly scalable approach for improving the throughput and overall performance of High-transaction, Large Database-centric business applications. Since the inception of the relational database, application engineers and architects have required ever-increasing perform Ance and capacity, based on the simple observation, a business databases generally grow in size over time. Adding to the trend are the extreme expansion of business data due to the evolution of the Internet economy, the I Nformation age, and the prevalence of high-volume electronic commerce.

As any experienced database administrator or application developer knows all too well, it's axiomatic that as the size of an D transaction volume of the database tier incurs linear growth, response times tend to grow logarithmically. This was shown in the following diagram:

Figure 1. The growth in database transactions and volumes have a large impact on response times.

The reasons for the performance and scalability challenges is inherent to the fundamental design of the database Manageme NT systems themselves. Databases rely heavily on the primary three components of any computer:

• Cpu
• Memory
• Disk

Through Benchmark tests, we have the performed, we know that each of the these elements on a single server can only scale T o A given point, and then other measures must is taken. While it's clear that disk I/O is the primary bottleneck, as database management systems has improved they also continue To take greater advantage of CPU and memory. In fact, we had observed that it was the matching of these three factors that determines maximum performance. In other words, cannot add an unlimited number of CPUs (or processing cores) and see a commensurate increase in perfor Mance without also improving the memory capacity and performance of the disk drive subsystem. It is also common to see a diminishing return as resources are added to a single database server. These factors is especially true in mixed-use business transaction systems; Systems that perform a high volume of read and write transactions, as well as supporting generalized business reporting TA SKS.

Therefore, as business applications gain sophistication and continue to grow in demand, architects, developers and Databas E administrators has been presented with a constant challenge of maintaining database performance for mission critical SY Stems. This landscape drives the need for Database sharding.

What Drives the need for Database sharding? DATABASE sharding