Disclaimer: I quickly put together these thoughts in free-style, sorry if they don’t make too much sense.
Remembering a chat that I had with Dhruv Gupta from Fauna, he asked me why wasn’t I using fauna as my only data store for my app. I just had some flashes of insights that I would like to quickly share in hopes that they will be a bit useful as feedback.
If fauna had a low-code solution alternative to FQL I could speed up my development and venture to dump more things.
I am very careful to add a field to Fauna since I have been burned before with making the schema dirty and therefor had to purge the database and start from scratch. So it seems like it’s easier to add fields than to remove. And when I modify I have the risk of screwing it up.
FQL is a convenient tool, but it is complicated to learn and verbose to read. To build sophisticated queries it is needed to nest a bunch of FQL commands with tons of parenthesis. On top of that there are no unit-tests for this so it’s a shoot-and-pray approach that it isn’t easy to handle. By no means I am thinking of a mutable language replacement. What would be cool is to have a kind of “Integromat.com” for fauna where I could jump in and build nodes that would immutably transform data. That would give me more peace of mind to do some complicated queries and would make it less tedious. Maybe if I was a full-time FQL developer it would be a breeze to build new user-defined-functions but in my case I am full stack and most of the time I’m working on JS and ReasonML. For quick things I don’t mind using FQL, but nested complexities are a drag in FQL.
If I had a low-code tool for fauna and a robust graphQL schema, for sure I would throw in way more data instead of using other third party databases like Monday.com in tandem.