doc: Sharding vs partitioning #570
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
johanandren
approved these changes
May 15, 2024
|
um, was thinking about it, but probably not important enough. Data partitioning is still not wrong, even though end goal is database sharding. |
pvlugter
approved these changes
May 16, 2024
| @@ -15,7 +15,7 @@ The Akka Persistence R2DBC plugin allows for using SQL database with R2DBC as a | |||
| * [PostgreSQL JSON](postgres_json.md) | |||
| * [Projection](projection.md) | |||
| * [Configuration](config.md) | |||
| * [Data partitioning](data-partition.md) | |||
| * [Database sharding](data-partition.md) | |||
There was a problem hiding this comment.
Also change the name of the file for links? Or too much hassle with redirecting?
There was a problem hiding this comment.
was also thinking about it, but I don't see it as very important
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trigged by some feedback I looked closer at what others say regarding sharding vs partitioning.Seems like sharding is mostly used for horizontal partitioning to distribute the data across multiple servers. While partitioning is a more generic term it mostly refers to splitting up large tables into smaller tables, but still in one database instance (*vertical scaling").
Our primary goal is horizontal scaling so we should highlight database sharding.
That said, the implementation splits the data into multiple tables (partitioning), which can then optionally be located on different database instances (sharding). The documentation still uses data partition and that it corresponds to a table. I think that is fine, but let me know if it's confusing.