Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
None
-
1
Description
In https://www.couchbase.com/multi-dimensional-scalability-overview
It is said:
While scaling a distributed architecture is great for data, it is a challenge for indexes and queries. Simply put, scaling data speeds up reads and writes but it slows down queries, and while creating indexes speeds up queries it slows down writes. For example, if you scale out your database to support a massive amount of data, your query performance will suffer dramatically because the more nodes participating in a distributed query, the worse it performs. And creating many indexes to improve query performance will negatively impact write performance because writes do not complete until all indexes have been updated. The bottom line is that scaling out, with every database service running on every node, can result in a big drop in efficiency and performance.
|
The 2nd part of the sentence below pretends "writes do not complete until all indexes have been updated" :
And creating many indexes to improve query performance will negatively impact write performance because writes do not complete until all indexes have been updated.
|
As writes are asynchronous (by default), there is no direct relation between writes and indexes updates.
=> this statement is weird, not to say wrong (to me at least).
Can you explain more what is the concept behind this sentence ? Or remove it if needed.
Thank you.