Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
1–10 of 247 posts
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#2Thanks for sharing, really helpful to see your thinking. I haven't fully embraced FaaS myself but never regretted it either.
Curious to hear more about Renovate vs Dependabot. Is it complicated to debug _why_ it's making a choice to upgrade from A to B? Working on a tool to do app-specific breaking change analysis so winning trust and being transparent about what is happening is top of mind.
When were you using quay.io? In the pre-CoreOS years, CoreOS years (2014-2018), or the Red Hat years?
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#3It's weird that one of the reasons that you endorse AWS is that you had regular meetings with your account manager but then you regret premium support which is the whole reason you had regular meetings with your account manager.
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#4I see you regret Datadog but there's no alternative - did you end up homebrewing metrics, or are you just living with their insane pricing model? In my experience they suck but not enough to leave.
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#5This is the best post to HN in quite some time. Kudos to the detailed and structured break-down.
If the author had a Ko-Fi they would've just earned $50 USD from me.
I've been thinking of making the leap away from JIRA and I concur on RDS, Terraform for IAC, and FaaS whenever possible. Google support is non-existent and I only recommend GC for pure compute. I hear good things about Big Table, but I've never used in in production.
I disagree on Slack usage aside from the postmortem automation. Slack is just gonna' be messy no matter what policies are put in place.
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#6I would love to read more about the pros and cons of using a single database, if anyone has pointers to articles
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#7Great post. I even wouldn’t mind more details, especially about datadog, or as others pointed out, the kind of contradiction with aws support.
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#8> Picking Terraform over Cloudformation: Endorse
I, too, prefer McDonald's cheeseburgers to ground glass mixed with rusty nails. It's not so much that I love Terraform (spelled OpenTofu) as that it's far and away the least bad tool I've used in the space.
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#9This is the best post to HN in quite some time. Kudos to the detailed and structured break-down. If the author had a Ko-Fi they would've just earned $50 USD from me. I've been thinking of making the leap away from JIRA and I concur on RDS, Terraform for IAC, and FaaS whenever possible. Google support is non-existent and I only recommend GC for pure compute. I hear good things about Big Table, but I've never used in i…
What do you use if not slack? OPs advice is standard best practice. Respect peoples time by not expecting immediate response, and use team or function based channels as much as possible.
Other options are email of course, and what, teams for instant messages?
Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)
#10I disagree on Kubernetes versus ECS. For me, the reasons to use ECS are not having to pay for a control plane, and not having to keep up with the Kubernetes upgrade treadmill.