I have not undetaken a serious analysis of AresDB; and on their part, Uber has not - to my knowledge - published any in-depth design description or benchmark re

I have not undetaken a serious analysis of AresDB; and on their part, Uber has not - to my knowledge - published any in-depth design description or benchmark results. I definitely see some key useful concepts mentioned in that blog post, but there are others which I don't really see presented (or that are associated with what's described as future work). I realize it's FOSS, but - I can't just go read their sources. My intuition says that they're probably doing a decent-but-not-optimal job for their own use-case and are not planning on developing it into something more general. Specifically, the fact that they only accept their own query language is fishy. I also note that the public repository on GitHub has not been updated for about half a year. --- Caveat: Ares might be brilliantly designed and implemented, I can't really fault them for anything with any certainty. Just speculating here.