Skip to content

Commit e157adb

Browse files
fix: typos
1 parent d89dbda commit e157adb

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1797,11 +1797,11 @@ But why do we need sharding? Here are some advantages:
17971797

17981798
- **Complexity**: Sharding increases the complexity of the system in general.
17991799
- **Joins across shards**: Once a database is partitioned and spread across multiple machines it is often not feasible to perform joins that span multiple database shards. Such joins will not be performance efficient since data has to be retrieved from multiple servers.
1800-
- **Rebalancing**: If the data distribution is not uniform or there is a lot of load on a single shard, in such cases we have to rebalance our shards so that the requests are as equally distributed among the shards as possible.
1800+
- **Rebalancing**: If the data distribution is not uniform or there is a lot of load on a single shard, in such cases, we have to rebalance our shards so that the requests are as equally distributed among the shards as possible.
18011801

18021802
## When to use sharding?
18031803

1804-
Here are some reasons where sharding might be the right choice:
1804+
Here are some reasons why sharding might be the right choice:
18051805

18061806
- Leveraging existing hardware instead of high-end machines.
18071807
- Maintain data in distinct geographic regions.
@@ -1925,7 +1925,7 @@ Where,
19251925

19261926
As VNodes help spread the load more evenly across the physical nodes on the cluster by diving the hash ranges into smaller subranges, this speeds up the re-balancing process after adding or removing nodes. This also helps us reduce the probability of hotspots.
19271927

1928-
## Data replication
1928+
## Data Replication
19291929

19301930
To ensure high availability and durability, consistent hashing replicates each data item on multiple `N` nodes in the system where the value `N` is equivalent to the _replication factor_.
19311931

@@ -2221,7 +2221,7 @@ Message topics authenticate applications that try to publish content, this allow
22212221

22222222
## Examples
22232223

2224-
Here are some technologies commonly used for publish-subscribe:
2224+
Here are some commonly used publish-subscribe technologies:
22252225

22262226
- [Amazon SNS](https://aws.amazon.com/sns)
22272227
- [Google Pub/Sub](https://cloud.google.com/pubsub)
@@ -2287,7 +2287,7 @@ Some common disadvantages of monoliths are:
22872287
- Reduced reliability as a single bug can bring down the entire system.
22882288
- Difficult to scale or adopt new technologies.
22892289

2290-
## Modular monoliths
2290+
## Modular Monoliths
22912291

22922292
A Modular Monolith is an approach where we build and deploy a single application (that's the _Monolith_ part), but we build it in a way that breaks up the code into independent modules for each of the features needed in our application.
22932293

0 commit comments

Comments
 (0)