Copilot commented on code in PR #4529:
URL: https://github.com/apache/cassandra/pull/4529#discussion_r2621798302
##########
doc/modules/cassandra/pages/architecture/overview.adoc:
##########
@@ -4,15 +4,13 @@
{product} is an open-source, distributed NoSQL database.
It implements a partitioned wide-column storage model with eventually
consistent semantics.
-{cassandra} was initially designed at
https://www.cs.cornell.edu/projects/ladis2009/papers/lakshman-ladis2009.pdf[Facebook]
using a staged event-driven architecture
(http://www.sosp.org/2001/papers/welsh.pdf[SEDA]).
+{cassandra} was created at
https://www.cs.cornell.edu/projects/ladis2009/papers/lakshman-ladis2009.pdf[Facebook]
using a staged event-driven architecture
(http://www.sosp.org/2001/papers/welsh.pdf[SEDA]).
This initial design implemented a combination of Amazon's
https://www.cs.cornell.edu/courses/cs5414/2017fa/papers/dynamo.pdf[Dynamo]
distributed storage and replication techniques and Google's
https://static.googleusercontent.com/media/research.google.com/en//archive/bigtable-osdi06.pdf[Bigtable]
data and storage engine model.
Dynamo and Bigtable were both developed to meet emerging requirements for
scalable, reliable and highly available storage systems, but each had areas
that could be improved.
-{product} was designed as a best-in-class combination of both systems to meet
emerging large scale, both in data footprint and query volume, storage
requirements.
-As applications began to require full global replication and always available
low-latency reads and writes, a new kind of database model was required to meet
these new requirements.
-Relational database systems at that time struggled to meet the requirements.
+{product} was designed to combine the strengths of both of these distributed
database systems to address scaleability, both in terms of data volume and
query throughput. As applications increasingly demanded global replication,
continuous availability, and low-latency reads and writes, a new database model
became necessary, one that traditional relational systems of the time were not
well suited to support.
Review Comment:
The word "scaleability" is misspelled. The correct spelling is "scalability".
```suggestion
{product} was designed to combine the strengths of both of these distributed
database systems to address scalability, both in terms of data volume and query
throughput. As applications increasingly demanded global replication,
continuous availability, and low-latency reads and writes, a new database model
became necessary, one that traditional relational systems of the time were not
well suited to support.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
