Not to be too critical since I like database startups as much as the next guy, but there is almost nothing original in their approach to database engines. Most of their assertions about existing databases only apply to relatively weak open source databases; on the high-end databases don't work the way they are assuming at all, which makes me wonder how much they actually know about database engine internals generally. Architecturally, DeepDB goes into the same bucket as PostgreSQL in terms of capabilities and scalability, albeit a different design.
As a more technical nitpick, "high availability" does not mean fast restarts. It means never goes down. The design as described is not a high availability architecture.
Bonus observation: if you assert your database engines uses extensive fine-grained locking, don't show a chart with 24 cores at ~100% utilization and call it "efficient". This is what you would expect to see for a poorly designed and very inefficient implementation for this type of architecture. You can be burning all of your CPU and getting very little throughput. A credible presentation would have demonstrated that system throughput scales linearly with the number of cores (unlikely given the description of their internals).