Live data from Hacker News

Almost every infrastructure decision I endorse or regret

cep.dev

271–280 of 644 posts

Re: Almost every infrastructure decision I endorse or regret

#271
post #259

Earlier quoted context omitted.

Not to pick on you, but is SQL not basic knowledge for every software engineer these days? Or have times changed?

Times have changed. If you have C# programmers and they can't do it in Entity Framework/LINQ, then they can't do it.

This seems like a stereotype from 2010s and disconnected from reality today.

Re: Almost every infrastructure decision I endorse or regret

#272

Earlier quoted context omitted.

I don't want to be negative, but this post reads like a list of things that I want to avoid in my career. I did a brief stint in cloud stuff at a FAANG and I don't care to go back to it. Right now I'm engineer No. 1 at a current startup just doing DDD with a Django monolith. I'm still pretty Jr. and I'm wondering if there's a way to scale without needing to get into all of the things the author of this article mentio…

You don't need this many tools, especially really early. It also depends on the particulars of your business. E.g. if you are B2B SaaS, then you need a ton of stuff automatically to get SOC2 and generally appease the security requirements of your customers. That said, anything that's set-and-forget is great to start with. Anything that requires it's own care and feeding can wait unless it's really critical. I think w…

Also don't make microservices if you don't have teams that will independently own them.

Re: Almost every infrastructure decision I endorse or regret

#273
post #266

Earlier quoted context omitted.

Keep in mind, there is an in between.. I would have a hard time doing servers as cheap as hetzner for example including the routing and everything

I do that. In fact I've been doing it for years, because every time I do the math, AWS is unreasonably expensive and my solo-founder SaaS would much rather keep the extra money. I think there is an unreasonable fear of "doing the routing and everything". I run vpncloud, my server clusters are managed using ansible, and can be set up from either a list of static IPs or from a terraform-prepared configuration. The same…

I was more talking about physical backbone connection which hetzner does for you.

We are using hetzner cloud.. but we are also scaling up and down a lot right now

Re: Almost every infrastructure decision I endorse or regret

#274
post #191

Earlier quoted context omitted.

I'm right there with you on Jira. The haters are wrong - it's a decent enough ticket system, no worse than anything else I've used. You can definitely torture Jira into something horrible, but that's not Jira's fault. Bad managers will ruin any ticket system if they have the customization tools to do so.

Using Jira feels like using IBM enterprise web software from 2005, and I am simply not going to make my teams put up with that amount of inanity.

Found the person who never used Lotus Notes haha.

Re: Almost every infrastructure decision I endorse or regret

#275

> Picking AWS over Google Cloud I know this is an unpopular opinion but I think google cloud is amazing compared to AWS. I use google cloud run and it works like a dream. I have never found an easier way to get a docker container running in the cloud. The services all have sensible names, there are fewer more important services compared to the mess of AWS services, and the UI is more intuitive. The only downside I ha…

Totally agree, GCP is far easier to work with and get things up and running for how my brain works compared to AWS. Also, GCP name stuff in a way that tells me what it does, AWS name things like a teenage boy trying to be cool.

Re: Almost every infrastructure decision I endorse or regret

#276
post #266

Earlier quoted context omitted.

I do that. In fact I've been doing it for years, because every time I do the math, AWS is unreasonably expensive and my solo-founder SaaS would much rather keep the extra money. I think there is an unreasonable fear of "doing the routing and everything". I run vpncloud, my server clusters are managed using ansible, and can be set up from either a list of static IPs or from a terraform-prepared configuration. The same…

I was more talking about physical backbone connection which hetzner does for you. We are using hetzner cloud.. but we are also scaling up and down a lot right now

Could you please explain what you mean by "physical backbone connection", as I can't think of a meaning that fits the context.

If you mean dealing with the physical dedicated servers that can be rented from Hetzner, that's what the person you replied to was talking about being not so difficult.

If you mean everything else at the data centre that makes having a server there worthwhile (networking, power, cooling, etc.) I don't think people were suggesting doing that themselves (unless you're a big enough company to actually be in the data centre business), but were talking about having direct control of physical servers in a data centre managed by someone like Hetzner.

(edit: and oops sorry I just realised I accidentally downvoted your comment instead of up, undone and rectified now)

Re: Almost every infrastructure decision I endorse or regret

#277

> Picking AWS over Google Cloud I know this is an unpopular opinion but I think google cloud is amazing compared to AWS. I use google cloud run and it works like a dream. I have never found an easier way to get a docker container running in the cloud. The services all have sensible names, there are fewer more important services compared to the mess of AWS services, and the UI is more intuitive. The only downside I ha…

> I have never found an easier way to get a docker container running in the cloud We started using Azure Container Apps (ACA) and it seems simple enough. Create ACA, point to GitHub repo, it runs. Push an update to GitHub and it redeploys.

Azure Container Apps (ACA) and AWS AppRunner are also heavily "inspired" by Google Cloud Run.

Re: Almost every infrastructure decision I endorse or regret

#278
post #276

Earlier quoted context omitted.

I was more talking about physical backbone connection which hetzner does for you. We are using hetzner cloud.. but we are also scaling up and down a lot right now

Could you please explain what you mean by "physical backbone connection", as I can't think of a meaning that fits the context. If you mean dealing with the physical dedicated servers that can be rented from Hetzner, that's what the person you replied to was talking about being not so difficult. If you mean everything else at the data centre that makes having a server there worthwhile (networking, power, cooling, etc.…

With "routing" I meant the backbone connection, which is included in the hetzner price.

Aka if I add up power (including backup) + backbone connection rental + server deprication I can not do it for the hetzner price..

That was quite imprecise, sorry about that.

Re: Almost every infrastructure decision I endorse or regret

#279

Earlier quoted context omitted.

I work at a startup and most of the stuff in the article covers things we use and solve real world problems. If you're looking for successful businesses, indie hackers like levelsio show you how far you can get with very simple architectures. But that's solo dev work - once you have a team and are dealing with larger-scale data, things like infrastructure as code, orchestration, and observability become important. Ku…

How many people if I may ask? And how many TPS for your services? I am hoping I can get away with a simple monolith for a very long time.

30-40 people; not much TPS but we're not primarily building a web app; we have event-driven data pipelines and microservices for ML data.

If you're primarily building a web app, a monolith is fine for quite a while, I think. But a lot of the stuff in the post is still relevant even for monoliths - RDS, Redis, ECR, terraform, pagerduty, monitoring/observability.

Re: Almost every infrastructure decision I endorse or regret

#280

> The markup cost of using RDS (or any managed database) is worth it. Every so often I price out RDS to replace our colocated SQL Server cluster and it's so unrealistically expensive that I just have to laugh. It's absurdly far beyond what I'd be willing to pay. The markup is enough to pay for the colocation rack, the AWS Direct Connects, the servers, the SAN, the SQL Server licenses, the maintenance contracts, and a…

Some orgs are looking at moving back to on prem because they're figuring this out. For a while it was vogue to go from capex to opex costs, and C suite people were incentivized to do that via comp structures, hence "digital transformation" ie: migration to public cloud infrastructure. Now, those same orgs are realizing that renting computers actually costs more than owning them, when you're utilizing them to a signif…

Funny story time.

I was once part of an acquisition from a much larger corporate entity. The new parent company was in the middle of a huge cloud migration, and as part of our integration into their org, we were required to migrate our services to the cloud.

Our calculations said it would cost 3x as much to run our infra on the cloud.

We pushed back, and were greenlit on creating a hybrid architecture that allowed us to launch machines both on-prem and in the cloud (via a direct link to the cloud datacenter). This gave us the benefit of autoscaling our volatile services, while maintaining our predictable services on the cheap.

After I left, apparently my former team was strong-armed into migrating everything to the cloud.

A few years go by, and guess who reaches out on LinkedIn?

The parent org was curious how we built the hybrid infra, and wanted us to come back to do it again.

I didn't go back.

Post reply on HN