Why We're Building Stategraph: Terraform State as a Distributed Systems Problem
18 comments · devops, distributed
- Comments18
18 comments · devops, distributed
Story details from Lobsters ↗ · linked article on stategraph.dev.
Why We're Building Stategraph: Terraform State as a Distributed Systems Problem was first seen on Lobsters · Hottest on Oct 30, 2026. Since then it has appeared in 1 check on 1 different day. Its best position was #4 of 25, reached on Oct 30, 10:19 UTC. It dropped off the list after Oct 30, 10:19 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
If this works the way they pitch it, it could really save a lot of fiddling with large TF code bases. Breaking up large TF projects into smaller, more manageable states and waiting for long ass plan's burn a lot of expensive ops team time.
This sounds really cool. I'm surprised Hashicorp never did this themselves. That writeup is also a masterclass in technical marketing. Having worked in infra for a long time, I'm curious to see how monetizable this service is. In practice, many Terraform state files end up containing secrets. For a team that wants to…
I’m confused about the usecase. They talk about hundreds of engineers accessing a single state file—when does this happen? In workflows that I’m familiar with, everyone just pushes to GitHub and the CI applies their changes. Individual developers aren’t making changes to production from their laptops, and even manual…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Oct 30, 10:19 UTC, after 1 day of trending.
#4 on Lobsters · Hottest, on Oct 30, 10:19 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Oct 30, 2026 and has been on the list on 1 day (1 check) since.