Frontend-driven database access aka. "The Ultimate Endpoint" #566
Description
Hi guys! I just wanted to share some ideas for the production usage of AskQL. I mean business case - which actually can be an idea for another product using AskQL :)
Use case
Imagine a legacy system having its own MySQL, Oracle, MongoDB database. You're a frontend developer building some new features and you need a single, additional piece of information from this DB. Wait - you need to match it and join with some other data from the REST endpoint.
OK, now you're writing down your specs into JIRA and waiting. Waiting, and ... waiting. In some extreme cases, the backend folks from another department that is handling the database maintenance are needing weeks if not months to deploy this change to prod. And you're blocked.
They can potentially think of GraphQL but it's still is not that elastic. If you need some heavy processing (like merging the data with REST API resources) you gonna still develop a middleware fetching the data first from GQL, then REST, and then mixing it all together. With AskQL you don't need to.
Now, imaging having a single JS endpoint with AskQL server and the resources - generated (think: prisma.io) or coded by these backend folks exposing you a set of data tables and collections.
Now, the whole app development is driven by frontend guys. They can send out the whole micro-askql application against this endpoint.
Moreover, it simplifies the data access - because the access language is always the same: AskQL and not MongoDB/JS or SQL.