At our company, we frequently use Retool to create projects for our clients. With Retool continuously introducing new features, its capabilities now extend far beyond just building a basic admin tool. We are now building complete digital platforms with some more complex use cases.
In these complex scenarios, we sometimes need to execute 7 or 8 queries in a row (on the same data source). This poses a risk of data inconsistency if something goes wrong. A solution is setting up a backend that supports transactional operations:
- Execute Query 1
- Execute Query 2
- Execute Query 3
We could then access this through an API. While this is a viable solution, it implies moving away from "low code" solutions and reverting to more traditional "high code" approaches for certain aspects.
I'm keen to learn about how others in the community handle such situations. I'd also be interested in hearing from @Retool regarding any plans to incorporate transactional capabilities in their roadmap.
Thank you in advance for your insights!