4 ms·
Is there any reason he's never tried to analyze a "classic" RDBMS like Oracle or SQL Server? I have to imagine they'd clobber a lot of this hipster technology.
by tootie 12y ago
Is there any reason he's never tried to analyze a "classic" RDBMS like Oracle or SQL Server? I have to imagine they'd clobber a lot of this hipster technology.
- samkone 12y agoLol He can't because Oracle licensing forbids to do this kind of work and make the results public.
- tootie 12y agoThank for a real answer. Do you have a source for that assertion. Is Microsoft the same?
- electrum 12y agoHe tested PostgreSQL: https://aphyr.com/posts/282-call-me-maybe-postgres https://aphyr.com/posts/282-call-me-maybe-postgres
- threeseed 12y agoI don't understand how this is comparable though. All of other databases were tested in clustered mode. Why not PostgreSQL as well ?
- rsynnott 12y agoI don't think postgres has a first-party clustering system.
- Jweb_Guru 12y agoPostgres doesn't have a builtin clustered mode, or claim to be totally available (and also, incidentally, doesn't guarantee serializability for hot standby replication targets, which is prominently stated in a bright red box that says "warning" in the documentation on serializable isolation, i.e. the first place you would look). It claims to be CP in a single-node configuration (which it is) and aphyr tested it on those claims. Remember, Jepsen isn't about proving that a database can't violate CAP, nor is it trying to say "all databases are crap." It's about verifying the marketing claims and then determining whether there are any mitigating strategies. The fact that many databases make unreasonable marketing claims is unfortunate, but certainly not a requirement. It's also worth posing this question in reverse: what would happen if these distributed databases were tested in a single-cluster configuration? As noted in the most recent article on Elasticsearch, many of them (e.g. Elasticsearch, Cassandra, and Riak) acknowledge writes before fsync and can therefore lose data due to issues like `kill -9`, power loss, and other exceptional conditions, while Postgres doesn't. For a single-node database this robustness is very important, while he argues that it isn't as important for a distributed one. Because these databases aren't designed to be used as single nodes, aphyr didn't substantially ding them for that. Again, what's important is whether the database does what its documentation says it does when used as its documentation says it should be used.
- deleted 12y ago[deleted]
- wglb 12y agoHere is a bit of an index page: https://aphyr.com/tags/jepsen https://aphyr.com/tags/jepsen. It doesn't appear that he has. And yes, I would guess that they would indeed clobber those written there.
- deleted 12y ago[deleted]
- jhugg 12y agoWell, those systems are largely not distributed, barring SQL Parallel Data Warehouse and, very arguably, RAC. Jepson tests network partitions... so less useful.
- tootie 12y agoThe whole draw of Oracle for the last 20+ years is how well it can replicate across a cluster over a network. Maybe it's not quite the same as how modern KV stores work, but it's still guaranteeing consistency across a network and is therefore a candidate for jepsen testing.