...except that it's not :)
FLXBL is fully instrumented, every operation is traced and logged, meaning that - if you want to have a private/enterprise deployment of FLXBL, your DevOps/engineering team already has everything wired up, out of the box, with pre-made Grafana dashboards.


Mailwarm
How do you handle changes over time, like migrations and keeping generated clients in sync?
@karimbenkeroum Great question!
We currently look at migrations as breaking and non-breaking.
The non-breaking migrations are generally create/safe field type changes.
The breaking ones are the ones where you might lose a portion of your data.
Schemas are versioned, which means that you can freely move from version X to Y to Z to X or B, or whatever else.
The generated clients can be guarded by the CLI - https://www.npmjs.com/package/@flxbl-dev/cli
which you can run in "watch"/dev mode, which pools constantly for changes.
There's also a generated metadata json file that informs you of the current active version.
Thank you!
Best of luck Marko, product looks very interesting. We currently have implemented in-house GraphQL server for Crana.AI but will keep an eye on this as it might help us on some smaller projects.
@vladdy_dotcom Thank you very much Vlad!