官术网_书友最值得收藏!

Write optimization

Traditional relational and document databases are optimized for read performance. Writing data to a relational database will typically involve making in - place updates to complicated data structures on disk, in order to maintain a data structure that can be read efficiently and flexibly. Updating these data structures is a very expensive operation from a standpoint of disk I/O, which is often the limiting factor for database performance. Since writes are more expensive than reads, you'll typically avoid any unnecessary updates to a relational database, even at the expense of extra read operations.

Cassandra, on the other hand, is highly optimized for write throughput and, in fact, never modifies data on disk; it only appends to existing files or creates new ones. This is much easier on disk I/O and means that Cassandra can provide astonishingly high write throughput. Since both writing data to Cassandra and storing data in Cassandra are inexpensive, denormalization carries little cost and is a good way to ensure that data can be efficiently read in various access scenarios.

Because Cassandra is optimized for write volume, you shouldn't shy away from writing data to the database. In fact, it's most efficient to write without reading whenever possible, even if doing so might result in redundant updates.

Just because Cassandra is optimized for writes doesn't make it bad at reads; in fact, a well-designed Cassandra database can handle very heavy read loads with no problem. We'll cover the topic of efficient data modeling in great depth in the next few chapters.

主站蜘蛛池模板: 莆田市| 乌鲁木齐市| 蓬莱市| 突泉县| 津南区| 吉木萨尔县| 屏东县| 凉山| 宣汉县| 鱼台县| 渭南市| 建水县| 武穴市| 密山市| 合作市| 商城县| 浑源县| 洛扎县| 汾西县| 广元市| 湖州市| 成安县| 清远市| 苗栗市| 沂源县| 临颍县| 大厂| 贡山| 长宁区| 阳江市| 喀什市| 海南省| 达日县| 阜新| 枞阳县| 高台县| 景谷| 嘉义市| 清河县| 灵丘县| 同仁县|