Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #10575

R

Robert Yokota

Personal blog · yokota.blogdatasystemsprogramming

Robert Yokota's personal blog at yokota.blog covers data, systems and programming. Since 2017, 7 different Hacker News readers have linked it 19 times, most often “CAP: Don't settle for eventual consistency”. It is still writing: the last post was on 2025-10-07, and you can follow it by feed.

Visit the blog
19mentions?
7HN people?
2017–2025first – last linked?
Links on Hacker News per year · peak 5 in 2018

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

HN readers link this blog for posts on distributed systems: the CAP theorem and eventual consistency, and a 2019 post on building a relational database on Kafka (KarelDB). Comments cite it without judging it.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. CAP: Don't settle for eventual consistency
    3 people · 3 mentions · first linked 2017-02-17
  2. Building a Relational Database Using Kafka
    3 people · 3 mentions · first linked 2019-09-23
  3. Stream-Relational Processing Platforms
    2 people · 2 mentions · first linked 2018-03-05

What Hacker News says?

  1. Here is what Google has to say about 'moving the "C" part up into your application': “We also have a lot of experience with eventual consistency systems at Google. In all such systems, we find developers spend a significant fraction of their time building extremely complex and error-prone mechanisms to cope with eventual consistency and handle data that may be out of date. We think this is an unacceptable burden to…

    Comment linking /2017/02/17/dont-settle-for-eventual-consistency

    on “The Limits of the CAP Theorem”
  2. Submitted Building a Relational Database Using Kafka as a story · 121 points

    HN discussion
  3. KCache is an in-memory Java cache where all writes are sent to a Kafka topic and then applied locally by any instances listening to that topic, providing an eventually-consistent cache. Great for scaling a small dataset that can fit on a single-node with easy replication and a full log of all updates in the Kafka topic. KarelDB adds relational querying, schema/table management, transactions, and a SQL interface on t…

    Comment linking /2019/09/23/building-a-relational-database-using-kafka/

    on “Kafka Spawns Open-Source KarelDB”
  4. Submitted CAP: Don't settle for eventual consistency as a story · 89 points

    HN discussion
  5. https://yokota.blog/2019/09/23/building-a-relational-databas...

    Comment linking /2019/09/23/building-a-relational-database-using-kafka/

    on “Kafka Spawns Open-Source KarelDB”
  6. Submitted In-Memory Analytics for Kafka Using DuckDB as a story · 5 points

    HN discussion
  7. What they're trying to explain is that so-called AP systems do not have 100% availability either. The CAP theorem applies to very specific scenarios that are not necessarily common - it is a much more narrow theorem then "CP vs AP" implies. For example, if your network partitions are usually small (i.e. there exists a majority outside the partition) and you can avoid routing requests to the minority partition (e.g.…

    Comment linking /2017/02/17/dont-settle-for-eventual-consistency/

    on “ACID transactions in a globally distributed database”
  8. Submitted Playing Chess with Confluent Schema Registry as a story · 3 points

    HN discussion
  9. Submitted Building a Graph Database Using Kafka as a story · 3 points

    HN discussion
  10. Submitted KCache: an In-Memory Cache Backed by Kafka as a story · 3 points

    HN discussion
  11. Submitted JSON Schema Compatibility and the Robustness Principle as a story · 2 points

    HN discussion
  12. Submitted The Hitchhiker's Guide to Stream Processing as a story · 2 points

    HN discussion
  13. Submitted Stream-Relational Processing Platforms as a story · 2 points

    HN discussion
  14. Submitted Don't Settle for Eventual Consistency as a story · 2 points

    HN discussion
  15. Submitted Understanding JSONata as a story · 1 points

    HN discussion
  16. Submitted Keta: A Metadata Store Backed by Apache Kafka as a story · 1 points

    HN discussion
  17. Submitted Using KCache with a Persistent Cache as a story · 1 points

    HN discussion
  18. Submitted KDatalog: Kafka as a Datalog Engine as a story · 1 points

    HN discussion
  19. Submitted Stream-Relational Processing Platforms as a story · 1 points

    HN discussion

Search all of HN for yokota.blog