Herb: Multi-DC Replication Engine for Uber’s Schemaless Datastore

Re:Herb: Multi-DC Replication Engine for Uber’s Schemaless D... by damm on Friday July 27, 2018 @03:33AM (#17624156)

Go ahead and downvote this; but where's the source?

Otherwise isn't this pointless bragging?

[ Parent | on HN ]

Re:Herb: Multi-DC Replication Engine for Uber’s Schemaless D... by takeda on Friday July 27, 2018 @11:46PM (#17631399)

So according to this post they created geographically distributed, multi master (with a mesh topology) that is always consistent.

Either they created a holy grail of databases, or an opportunity to write a great Post-Mortem in the future.

[ Parent | on HN ]

Re:Herb: Multi-DC Replication Engine for Uber’s Schemaless D... by throwaway123402 on Saturday July 28, 2018 @01:38AM (#17631736)

It's a little unclear from the article, but based on

> Since the system supports asynchronous replication, our data centers eventually become consistent. Writes are considered complete as soon as the remote data center acknowledges it.

I assume its eventually consistent (so AP).

I wish they compared why normal mysql async replication fails for them and they needed to build this though.

[ Parent | on HN ]

Re:Herb: Multi-DC Replication Engine for Uber’s Schemaless D... by thdxr on Saturday July 28, 2018 @12:54AM (#17631615)

Or it's just incredibly slow and not always available

[ Parent | on HN ]

Re:Herb: Multi-DC Replication Engine for Uber’s Schemaless D... by miohtama on Friday July 27, 2018 @11:22PM (#17631337)

It is not pointless for Uber. Please read it as a job advertisement for scalable database experts.

[ Parent | on HN ]