> An HTTP/JSON protocol doesn't have to replace the standard one. So, two protocols? Two standard protocols is rarely better than one. > having such a standar

> An HTTP/JSON protocol doesn't have to replace the standard one. So, two protocols? Two standard protocols is rarely better than one. > having such a standard protocol makes sense in the age of web apps Only if the existing standard protocol cannot work with the "web", and we have plenty of history proving otherwise. Replacing the existing standard with the loose JSON would be, strictly, a downgrade; and unnecessary, because we already do interoperate JSON and SQL. See: PostgREST and the many REST & GraphQL frontends on PostgreSQL. > particularly when NoSQL offerings that are perceived by the market as competitors (leaving aside whether they really are - perception matters more here) do that already This is really more of going into a pig's pen and wrestling with them. A database should do the job of a database. Competing for perception in a market that cannot make sane decisions for itself is how we get MongoDB.