> SQL is a great language for working with state SQL is a great* language for querying relational data.. (* Unless you need to pull relational data out in a t

> SQL is a great language for working with state SQL is a great* language for querying relational data.. (* Unless you need to pull relational data out in a tree like structure rather than flattened and denormalized set of rows, in which case you need to wrap a bunch of logic around it to get that type of output) > you're ultimately playing Relation Stitcher by needing to connect the various pieces together. I don't see how doing this in SQL does away with that. SQL also runs in to the same problem pointed out about Ansible; You, the "meat bio-processor", have to pre-calculate and declare the load order for dependencies (make VPC, then make firewall rule tied to VPC, then make VM tied to VPC and firewall rule), you can't leave the execution order or the decision of conditional execution up to the engine (VPC with that ID found, just get the ID, don't recreate it), it's on you to make each of these decisions... That's easy enough for a toy use case, but any large production system and it'll fall apart from too much context needed.