60-database:cassandra
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| 60-database:cassandra [2019/03/01 23:31] – [Use cases] Roge | 60-database:cassandra [2019/03/25 13:40] (Version actuelle) – Roge | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| ====== Cassandra ====== | ====== Cassandra ====== | ||
| + | {{tag> | ||
| ===== Use cases ===== | ===== Use cases ===== | ||
| - | From https:// | + | From [[https:// |
| - | //"Ideal Cassandra | + | //"The ideal Cassandra |
| - | It turns out that Cassandra is really very good for some applications. | + | |
| - | 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 | ||
| + | * //There is no need for joins or aggregates.// | ||
| + | //Some of my favorite examples of good use cases for Cassandra are:// | ||
| - | * Writes exceed reads by a large margin. | + | * // |
| - | * Data is rarely updated and when updates are made they are idempotent. | + | * //Storing time series data (as long as you do your own aggregates).// |
| - | * Read Access is by a known primary key. | + | * //Tracking pretty much anything including order status, packages etc.// |
| - | * Data can be partitioned via a key that allows the database to be spread evenly across multiple nodes. | + | * //Storing health tracker data.// |
| - | * There is no need for joins or aggregates. | + | * //Weather service history.// |
| + | * //Internet of things status and event history.// | ||
| + | * // | ||
| + | * //Email envelopes—not the contents."// | ||
| - | 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:31