[zellyn]

Having watched and participated in an online call (mentioned in another comment here), there were two big things that were strikingly cool about MassDriver:

* It turns the connections between components owned by different IaC tools/systems into _typed_ JSON. Think patch panels, where the connections are fully typed.

* Kelsey mentioned that you can introspect on the metadata in the live system using absolutely anything you want, down to just bash scripts. So it's _very_ hackable

[coryodaniel]

Hey! How's it been? I followed you on bsky a few days ago!

Glad you liked it! Yeah, the typed connections are a big part of what makes Massdriver powerful. It makes sure infrastructure components integrate right without devs having to worry about all the low-level details.

We're expanding the graph metadata with a querying system coming out of alpha soon that lets you ask stuff like "Where are all my t3 instances in production?" or "Which services are using a kubernetes version less than 1.25" Makes it way easier to understand what’s running where.

And since it’s all API-first, it’s easy to write quick scripts for reporting or automating changes across environments.

[Aeolun]

Isn’t that something you’d easily get out of any IaC tooling dashboard?

I’ll admit a graph query makes it easier, but the information is there.

[dwill-mdcloud]

There are probably some dashboards that can give you that information easily. Where having the graph is interesting is scripting something that can test changes to a widely used module. With all of your config behind an API you could pull the live config of every instance of that module, run your change against it, and then trigger a deployment of each one of the modules in isolation with the new code. The least interesting part of the API is search.