4 ms·

eventually consistent database Is an oxymoron

• ArnoVW 6y ago
  In case you didn't know, it's in used as a technical term in distributed computing circles. https://en.m.wikipedia.org/wiki/Eventual_consistency https://en.m.wikipedia.org/wiki/Eventual_consistency
• seangrogg 6y ago
  Alternatives to strong consistency in databases has been around for quite a while...
• trollbaitmate 6y ago
  i feel bad for you
• sjkelleyjr 6y ago
  Lol...hackernews commenters...
• dchyrdvh 6y ago
  Iirc, Spanner is eventually consistent.
  • exacube 6y ago
    spanner is strongly consistent
    • dastbe 6y ago
      spanner does support eventually consistent snapshot reads as well with improved latency benefits (as you're effectively foregoing a transaction).
  • aprao 6y ago
    Cloud Bigtable is eventually consistent, Spanner is strongly consistent.
• deleted 6y ago
  [deleted]
• AtlasBarfed 6y ago
  When you get down to it, between cache coherency across CPUs and memory, disk flush delays and disk caches, every database is eventually consistent. And if you want to operate over a distributed network, which means you WILL have network partitions, then you are subject to CAP and will need eventual consistency mechanisms.
  • jacobparker 6y ago
    > When you get down to it, between cache coherency across CPUs and memory, disk flush delays and disk caches, every database is eventually consistent. This is a false. None of the things you listed preclude consistency. > And if you want to operate over a distributed network, which means you WILL have network partitions, then you are subject to CAP and will need eventual consistency mechanisms. That's not how CAP works. Plenty of distributed CP databases exist.
• vhiremath4 6y ago
  Ask me how I know you've never scaled a high throughput Elasticsearch cluster.
• dang 6y ago
  Please don't post unsubstantive comments here.