Outils du site

Quelle époque terrible que celle où des idiots dirigent des aveugles. [William Shakespeare]

60-database:cassandra

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Prochaine révision
Révision précédente
60-database:cassandra [2019/03/01 23:30] – créée Roge60-database:cassandra [2019/03/25 13:40] (Version actuelle) Roge
Ligne 1: Ligne 1:
 ====== Cassandra ====== ====== Cassandra ======
  
 +{{tag>Cassandra BD DB}}
  
 ===== Use cases ===== ===== Use cases =====
  
-From https://blog.pythian.com/cassandra-use-cases/+From [[https://blog.pythian.com/cassandra-use-cases/|https://blog.pythian.com/cassandra-use-cases/]]
  
-//"Ideal Cassandra Use Cases +//"The ideal Cassandra application has the following characteristics:// 
-It turns out that Cassandra is really very good for some applications.+ 
 +  * //Writes exceed reads by a large margin.// 
 +  * //Data is rarely updated and when updates are made they are idempotent.// 
 +  * //Read Access is by a known primary key.// 
 +  * //Data can be partitioned via a key that allows the database to be spread evenly across multiple nodes.// 
 +  * //There is no need for joins or aggregates.// 
 +//Some of my favorite examples of good use cases for Cassandra are:// 
 + 
 +  * //Transaction logging: Purchases, test scores, movies watched and movie latest location.// 
 +  * //Storing time series data (as long as you do your own aggregates).// 
 +  * //Tracking pretty much anything including order status, packages etc.// 
 +  * //Storing health tracker data.// 
 +  * //Weather service history.// 
 +  * //Internet of things status and event history.// 
 +  * //Telematics: IOT for cars and trucks.// 
 +  * //Email envelopes—not the contents."//
  
-The ideal Cassandra application has the following characteristics: 
  
-  * Writes exceed reads by a large margin. 
-  * Data is rarely updated and when updates are made they are idempotent. 
-  * Read Access is by a known primary key. 
-  * Data can be partitioned via a key that allows the database to be spread evenly across multiple nodes. 
-  * There is no need for joins or aggregates. 
-Some of my favorite examples of good use cases for Cassandra are: 
-  * Transaction logging: Purchases, test scores, movies watched and movie latest location. 
-  * Storing time series data (as long as you do your own aggregates). 
-  * Tracking pretty much anything including order status, packages etc. 
-  * Storing health tracker data. 
-  * Weather service history. 
-  * Internet of things status and event history. 
-  * Telematics: IOT for cars and trucks. 
-  * Email envelopes—not the contents."// 
Dernière modification : 2019/03/01 23:30