Illustration Image

Cassandra.Link

The best knowledge base on Apache Cassandra®

Helping platform leaders, architects, engineers, and operators build scalable real time data platforms.

2/11/2022

Reading time:1 min

Cassandra – A Brief History of NoSQL

by John Doe


 
 Post Views: 
 4,259
Dear Readers,In this article we will see A Brief History of NoSQL.The term NoSQL was coined by Carlo Strozzi in the year 1998. He used this term to name his Open Source, Light Weight Database which did not have an SQL interface.In the early 2009, when Last.fm wanted to organize an event on open-source distributed databases, Eric Evans, a Rackspace employee, reused the term to refer to databases which are non-relational, distributed, and does not conform to atomicity, consistency, isolation, and durability – four obvious features of traditional relational database systems.In the same year, the “no:sql(east)” conference held in Atlanta, USA, NoSQL was discussed and debated a lot.Ever Since, discussion and practice of NoSQL gained momentum, and NoSQL saw an unprecedented growth.The CAP Theorem (Brewer’s Theorem)One must understand the CAP theorem when one talks about NoSQL databases or in fact when designing any distributed system. CAP theorem states that there are three basic requirements which exist in a special relation when designing applications for a distributed architecture.Consistency:This means that the data in the database remains consistent after the execution of an operation. For example after an update operation all clients see the same data.Availability:This means that the system is always on (service guarantee availability), no downtime.Partition Tolerance:This means that the system continues to function even when the communication among the servers is unreliable, i.e. the servers may be partitioned into multiple groups that cannot communicate with one another.In theory, it is impossible to fulfill all 3 requirements. CAP provides the basic requirements for a distributed system to follow 2 of the 3 requirements. Therefore all of the current NoSQL databases follow the different combinations of the C, A, P.Thank you for giving your valuable time to read the above information. Please click here to subscribe for further updatesKTEXPERTS is always active on below social media platforms.Facebook : https://www.facebook.com/ktexperts/LinkedIn : https://www.linkedin.com/company/ktexperts/Twitter : https://twitter.com/ktexpertsadminYouTube : https://www.youtube.com/c/ktexperts 
Note: Please test scripts in Non Prod before trying in Production.

Illustration Image

Post Views: 4,259

Dear Readers,

In this article we will see A Brief History of NoSQL.

The term NoSQL was coined by Carlo Strozzi in the year 1998. He used this term to name his Open Source, Light Weight Database which did not have an SQL interface.

In the early 2009, when Last.fm wanted to organize an event on open-source distributed databases, Eric Evans, a Rackspace employee, reused the term to refer to databases which are non-relational, distributed, and does not conform to atomicity, consistency, isolation, and durability – four obvious features of traditional relational database systems.

In the same year, the “no:sql(east)” conference held in Atlanta, USA, NoSQL was discussed and debated a lot.

Ever Since, discussion and practice of NoSQL gained momentum, and NoSQL saw an unprecedented growth.

The CAP Theorem (Brewer’s Theorem)

One must understand the CAP theorem when one talks about NoSQL databases or in fact when designing any distributed system. CAP theorem states that there are three basic requirements which exist in a special relation when designing applications for a distributed architecture.

Consistency:

This means that the data in the database remains consistent after the execution of an operation. For example after an update operation all clients see the same data.

Availability:

This means that the system is always on (service guarantee availability), no downtime.

Partition Tolerance:

This means that the system continues to function even when the communication among the servers is unreliable, i.e. the servers may be partitioned into multiple groups that cannot communicate with one another.

In theory, it is impossible to fulfill all 3 requirements. CAP provides the basic requirements for a distributed system to follow 2 of the 3 requirements. Therefore all of the current NoSQL databases follow the different combinations of the C, A, P.

Thank you for giving your valuable time to read the above information. Please click here to subscribe for further updates

KTEXPERTS is always active on below social media platforms.

Facebook : https://www.facebook.com/ktexperts/
LinkedIn : https://www.linkedin.com/company/ktexperts/
Twitter : https://twitter.com/ktexpertsadmin
YouTube : https://www.youtube.com/c/ktexperts

Note: Please test scripts in Non Prod before trying in Production.

Related Articles

cassandra
artificial.intelligence
machine.learning

Architect’s Guide to Using NoSQL for Real-time AI: Part 1

John Doe

6/9/2023

cassandra
nosql

Checkout Planet Cassandra

Claim Your Free Planet Cassandra Contributor T-shirt!

Make your contribution and score a FREE Planet Cassandra Contributor T-Shirt! 
We value our incredible Cassandra community, and we want to express our gratitude by sending an exclusive Planet Cassandra Contributor T-Shirt you can wear with pride.

Join Our Newsletter!

Sign up below to receive email updates and see what's going on with our company

Explore Related Topics

AllKafkaSparkScyllaSStableKubernetesApiGithubGraphQl

Explore Further

cassandra