The problem with SQL databases is that the earliest where designed before the internet became widespread. So they have synchronized clients that do not use HTT

The problem with SQL databases is that the earliest where designed before the internet became widespread. So they have synchronized clients that do not use HTTP or JSON. You need asynchronous clients that do not consume thread context switches. Also you always want to replicate all data in more than one location in real-time because 100% read uptime is really easy to provide, while 100% write uptime is a complex nightmare. I made this database after using MySQL, Oracle and Postgres for 10 years (it's a 2000 line replacement for my needs that these databases filled, a very narrow subset of the features you'll find in legacy databases): http://root.rupy.se http://root.rupy.se