mirror of
https://github.com/tiennm99/java-design-patterns.git
synced 2026-05-16 16:59:24 +00:00
Ilkka Seppälä
4108f86177
* Changed database implementation. Removed static objects. * Fix Logs * Fix 40 errors from checkstyle plugin run. 139 left)) * Fix CacheStore errors from checkstyle plugin 107 left * Fix last errors in checkstyle. * Fix sonar issues * Fix issues in VALIDATE phase * Fix Bug with mongo connection. Used "Try with resources" * Add test * Added docker-compose for mongo db. MongoDb db work fixed. * Provided missing tests * Comments to start Application with mongo. * Fix some broken links * Remove extra space * Update filename * Fix some links in localization folders * Fix link * Update frontmatters * Work on patterns index page * Work on index page * Fixes according PR comments. Mainly Readme edits. * fix frontmatter * add missing png * Update pattern index.md * Add index.md for Chinese translation * update image paths * update circuit breaker image paths * Update image paths for localizations * add generated puml * Add missing image * Update img file extensions * Update the rest of the EN and ZH patterns to conform with the new website Co-authored-by: Victor Zalevskii <zvictormail@gmail.com>
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
---
|
|
title: Sharding
|
|
category: Behavioral
|
|
language: en
|
|
tags:
|
|
- Performance
|
|
- Cloud distributed
|
|
---
|
|
|
|
## Intent
|
|
Sharding pattern means divide the data store into horizontal partitions or shards. Each shard has the same schema, but holds its own distinct subset of the data.
|
|
A shard is a data store in its own right (it can contain the data for many entities of different types), running on a server acting as a storage node.
|
|
|
|
## Class diagram
|
|
|
|
|
|
## Applicability
|
|
This pattern offers the following benefits:
|
|
|
|
- You can scale the system out by adding further shards running on additional storage nodes.
|
|
- A system can use off the shelf commodity hardware rather than specialized (and expensive) computers for each storage node.
|
|
- You can reduce contention and improved performance by balancing the workload across shards.
|
|
- In the cloud, shards can be located physically close to the users that will access the data.
|
|
|
|
## Credits
|
|
|
|
* [Sharding pattern](https://docs.microsoft.com/en-us/azure/architecture/patterns/sharding)
|