Apache HBase

Exactly.

So systems like MongoDB or HBase, they explicitly chose to sacrifice strict consistency.

And our sources call this the base model, right? Basically, available, soft state, eventual consistency.

Eventual consistency is the absolute key phrase there.

There was a previous startup in the 2010s called Splice Machine, which actually I was an advisor for because the guy, the founder was CMU alumni and he asked me to be, to be an advisor for them.

Um, but they were, cause they were running HBase plus Spark SQL.

Um, but they had a single copy of the data that was a row store.

Um, I mean, people have been wanting these HTAP systems or these hybrid systems since the very beginning.

And we'd actually had this design back in Viewfinder.

We were like, ah, we didn't, we looked around for data sources base to be using in order to build viewfinder on top of we didn't really like the things that were out there the technologies inside google looked better we had the big table we had spanner and whatnot we were looking around you know like hbase existed but i wasn't quite happy and there's some other systems like react and others and you know at one point we're just kind of like you know came up with the design for um cockroach to be an initial design and i was like no no guys we're doing a mobile photo sharing site we shouldn't build distributed you know database so we we Put it on the back burner, which I think was absolutely the right thing.

Maybe, or maybe we should just pivoted away from doing the mobile photo sharing site, given the way things worked out.

And then we got to square and we saw some of the same problems that they were experiencing with data storage systems.