Viewing profile — lawnchair
lawnchair
HN member- Joined
- Tue, Aug 03, 2010, 11:45 AM UTC
- HN karma
- 311
- Public activity
- 77 items
- HN profile
- View on Hacker News ↗
About lawnchair
Recent public activity
- story
- story
-
story
Show HN: Fast, Static GitHub Pull Requests
GitHub pull requests used to be fast. Now they're brutally slow, especially with large changes. I got tired of this, so I created Argus. Argus is a fast, static, server-rendered re…
-
comment
Comment #46158647
I have to say that if an incident becomes so overwhelming that nobody can spare even a moment to communicate with customers, that points to a deeper operational problem. A status p…
-
comment
Comment #45847157
We're still figuring out what balance makes sense between openness and sustainability, and we'd rather take the time to get it right than rush into a license we'll regret later. Th…
-
comment
Comment #45846370
Definitely agree. Most teams don't choose a language for purely rational reasons, and we're not pretending we did. We like OCaml, it makes us excited to build. We know the language…
- story
-
comment
Comment #45821078
Finding good candidates is easy.
-
comment
Comment #45814617
We already made it. Thanks for the callout.
-
comment
Comment #45812016
Terrateam | Remote (EU/US timezones) | Full-time | OCaml Terrateam builds GitOps automation for Terraform and OpenTofu. We help large engineering teams plan, review, and apply infr…
- story
-
comment
Comment #45526344
Using another company's funding announcement to shill your own is lame.
-
comment
Comment #45276444
Terraform Cloud does not actually solve this. It moves the state into their service and manages locking centrally, but the underlying model is unchanged. It is still one file with …
-
comment
Comment #45275919
Hi Alex. Great question and definitely something top of mind as we build Stategraph. The short answer is there is always a service layer in front of the database. Users and teams i…
-
comment
Comment #45275560
From my experience the problem at scale isn't that Terraform stops being useful. The problem is how state gets managed. Every IaC approach still has to coordinate changes across sh…
-
comment
Comment #45275126
Agreed. One of the frustrating things about using Terraform or OpenTofu is that all the data is sitting there in state but you can't really query or report on it. Making that infor…
-
comment
Comment #45274859
Regular tools (jq, cat, etc.) still work. That ability doesn't go away.
-
comment
Comment #45274359
We are already in that space [0] though that's not the focus of this post. Working with teams at scale on orchestration is what pushed us to look deeper at state itself and eventua…
-
comment
Comment #45274274
You are right that the simplicity of the state file is a strength and we do not want to lose that. One of our goals with Stategraph is to make state just as easy to inspect through…
-
comment
Comment #45274227
I don't know enough about Pulumi to make a fair comparison on locking granularity. Pulumi's model is pretty different from Terraform/OpenTofu in general and state management is onl…
-
comment
Comment #45274169
The pain really shows up when teams manage large sets of infrastructure in one place with thousands of resources. Even a small change forces a global refresh and a global lock, so …
-
comment
Comment #45274080
I don't think it fixes it. Atmos makes splitting and managing multiple states easier, but it still splits the graph. It doesn't change the underlying execution model.
-
comment
Comment #45273978
Author here. You are right that splitting by microservice reduces overlap. The problem is shared resources never go away such as VPCs IAM or databases so contention shows up there.…
- story
- story