> Because we are essentially inventing our own query language here. And inventing a custom language should be pretty much the last resort, I hope we agree on th

> Because we are essentially inventing our own query language here. And inventing a custom language should be pretty much the last resort, I hope we agree on that. No. I don’t agree at all. Creating a custom query language based on json or lisp or whatever is easy enough, flexible enough, prone to evolution, and helps building an abstraction between the front and the back. With this in mind, the day you decide to query an ElasticSearch instead of the RDBMS, the frontal API doesn’t need to change, there’s juste to update the translation layer to generate an ES query instead of SQL. Exposing SQL to the API is an awful idea.