But that, of course, now means you are implementing transactions. Which is one of the hardest things to implement in a distributed environment in a correct, scalable, and performant manner. Frankly, I would be very hesitant to trust such an implementation, if it wasn't the core competency of the developers who wrote it.
(Or unless they are just calling something else that implements the transactions, but at that point again you are just a very thin layer on top of a database.)
The actual request was for a composable language, with 4 operations as one example. But a language isn't limited to just four operations.
By the way, this exists in the FHIR spec as a transaction Bundle:
https://www.hl7.org/fhir/bundle-transaction.json.html
But that, of course, now means you are implementing transactions. Which is one of the hardest things to implement in a distributed environment in a correct, scalable, and performant manner. Frankly, I would be very hesitant to trust such an implementation, if it wasn't the core competency of the developers who wrote it.
(Or unless they are just calling something else that implements the transactions, but at that point again you are just a very thin layer on top of a database.)