11–14 of 14 posts
"Now why do this? Because if your way of interacting with the database is encoded in a consistent JSON format, then the server can analyze it easier to decide what to do." It could also parse the SQL query.
"Now why do this? Because if your way of interacting with the database is encoded in a consistent JSON format, then the server can analyze it easier to decide what to do." It could also parse the SQL query.
To be fair, JSON is much, much simpler to parse than SQL.
This wording makes it sound like this is an advantage for the server, that it enables things you otherwise wouldn't be able to do in the server. But even with SQL, something, usually the server, parses the text/string based query into what is essentially a format similar to this. Sharding and clustering would be "easier" too if you didn't need to do them in your application, if the server side stuff just handled it. Removing the need to parse SQL can remove the need to do that from your stack, but the server usually handles this anyway. The way we think about sharding and clustering now usually puts that functionality into the application or into middleware where you need to be aware of it. There's nothing stopping a server from taking a text based SQL query and offloading all those scaling features from the app itself.