Re:DynamoDB to Postgres: Why and How
by tootie on Wednesday June 21, 2017 @02:23PM
(#14606525)
I think if you're swimming a sea of options you look for any port and Aphyr's blog gives you all sorts of ammo to eliminate choices even if they're only failing on microscopic edge cases that will never affect your small-scale project.
[ Parent
| on HN ]
Do you really think network partitions are an edge case? Jepsen doesn't actually do anything particularly edge-casey -- it just introduces network partitions and verifies that the cluster doesn't do any crazy things.
(There are also relatively common cases it doesn't test, e.g. hard power-off.)
Re:DynamoDB to Postgres: Why and How
by manigandham on Wednesday June 21, 2017 @04:49PM
(#14607812)
Jepsen is not microscopic edge-cases. It is the heart of the distributed system promises that database vendors make but routinely do not meet.
If you would rather go back to trusting marketing speak instead, good luck to you.
I think the fact that most of the DBs that failed the Jepsen test are also running thousands of successful production installs is the counterargument.
Re:DynamoDB to Postgres: Why and How
by manigandham on Friday June 23, 2017 @01:20AM
(#14617177)
That's not much of an argument and "successful" is pretty subjective. Many teams have found issues where vendors have claimed otherwise, very common with mongodb and elasticsearch.
There are also thousands of problems that happen with no public reporting and no vendor is going to willingly release details of their support cases, especially when they're being paid to fix their own problems.
There's nothing but positive outcomes from jepsen and holding databases to strict standards to see if they actually meet the goals they state.