You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To address the load concentrated on the database, we need to introduce a MongoDB Sharded Cluster and apply appropriate sharding rules to the collections for a solution.
The Yorkie cluster stores almost all data, including documents and changes representing edits, in MongoDB. It has been observed that in real-world service scenarios, the majority of the load is concentrated on the database rather than the application servers, as was the case with Yorkie's predecessor, Kaleido.
The text was updated successfully, but these errors were encountered:
We need to determine which sharding method is appropriate for Yorkie and what kinds of sharding method MongoDB supports.
For example, ranged sharding would be efficient if a range of documents is frequently queried. Additionally, hash sharding would be ideal for massively-scalable workloads because it distributes data evenly.
Description:
This description is written by @sejongk
To address the load concentrated on the database, we need to introduce a MongoDB Sharded Cluster and apply appropriate sharding rules to the collections for a solution.
Why:
The Yorkie cluster stores almost all data, including documents and changes representing edits, in MongoDB. It has been observed that in real-world service scenarios, the majority of the load is concentrated on the database rather than the application servers, as was the case with Yorkie's predecessor, Kaleido.
The text was updated successfully, but these errors were encountered: