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

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.

主站蜘蛛池模板: 大余县| 平山县| 六安市| 扶沟县| 日照市| 城步| 宣恩县| 克东县| 平罗县| 汨罗市| 杭锦旗| 新平| 贵溪市| 贵定县| 临湘市| 比如县| 交口县| 南溪县| 神木县| 大丰市| 习水县| 图片| 鄱阳县| 盐津县| 景泰县| 南丰县| 高青县| 蒙阴县| 友谊县| 湖口县| 余干县| 鄂尔多斯市| 临安市| 玉溪市| 邵东县| 虞城县| 岱山县| 阜平县| 比如县| 乌兰浩特市| 上饶县|