There's a lot more to reliability than just the consensus algo and implementation.

There is more to a database than a raft implementation. A raft implementation would provide data replication between members and leader election. That is just one piece in a distributed database architecture. You then need a storage engine to persist the data, and a query engine to query the data.

To be able to scale, the database would most likely be composed of several raft clusters which brings couple of other challenges: - You need a sharding layer so that the queries can be routed to the right cluster - You need an orchestrator to be able to manage these clusters

It gets trickier as you try to run transactions across multiple raft clusters. You end up needing to implement 2PC.

FoundationDB solves all of the above except for the query engine part (given it is a KV).

You say that like it’s trivial to build a reliable OLTP key value store once you have a correct raft implementation. Never mind real world performance or reliability.

Is there a proven BFT version of that? RAFT aint it