An approach used in several NoSQL databases, including (optionally) Apache Cassandra, where the results of a successful write are not guaranteed to be reflected immediately in subsequent reads. Eventual consistent can be used to provide high availability with lower infrastructure costs than strong consistency.
Other articles
Read All
-
- News
Why pay for a managed service when I could just use a Kubernetes operator?
Managing open source data technologies is a topic that we are very familiar with at NetApp Instaclustr. This blog will set out a range of things that you should consider when thinking about using a Kubernetes operator for as your open source data technology and what to consider when comparing it against using a managed service.
-
- ClickHouse
- Dev Rel
Getting started with vector search on Instaclustr for ClickHouse®: Part 1 – The fundamentals
Introduction In the current excitement around Generative AI (GenAI) and Large Language Models (LLMs), the quest for the perfect vector database has become a focal point for many companies! Indeed, vector storage and vector search are both crucial for many GenAI applications – but are dedicated vector databases truly essential for scaling and optimizing GenAI?…
-
- Apache Kafka
- Dev Rel
Why is Apache Kafka® Tiered Storage more like a dam than a fountain? Part 4: Tiered Storage use cases
In two recent blogs, I investigated the new Kafka Tiered Storage architecture which enables Kafka to stream more (essentially unlimited data) for less cost (by storing more older records on cloud-native storage). In Part 1 I explored how local vs. remote storage works in theory, and in Part 2 I revealed some performance results and…