Cloud Management with Prolog

Funny how we seem to slowly converge toward the correct balance between custom DSL and general PL for problems. We won’t be using a custom DSL for every single problem ( contrary to what lispers initially thought), but we also won’t be using a single general programming language to rule them all.

slightly off topic : maybe this is the right place to ask: i’ve seen a post a few years ago about a revolutionnary language to program the web, very graphical programming oriented, extremely ambitious, but for the life of me i can’t remember its name. Does anyone here think he knows what i’m talking about and could help me ?

I like the idea. An easy way to get resource graphs into an environment that is good at querying such things. I seen a few ideas start this way. They always seem to get to certain point before the two domains (in this case AWS configuration and Prolog) have to work so closely that another tool entirely has to be created (basically a config language close to Prolog but geared toward the problem domain). I am surprised something like this doesn't already exist.

I agree there's a bazillion different headache-inducing ways to skin this cat. I also admit to hacking around in ansible/boto to force it to do what I want, when it doesn't work. I guess I just really don't want to touch prolog.

In the same vein: https://medium.com/@ahelwer/checking-firewall-equivalence-wi...

This is the second post on Prologue/Datalog in two days. I dabbled with these as a rules engine a long time ago, and didn't get very deep. Is there a resurgence?

When you'll master Cloudformation you'll never look other way. Key is to undestand what goes into one stack, no more, no less.

AWS Trust Advisor...