Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Almost every infrastructure decision I endorse or regret

cep.dev

Post reply on HN
Print view View original

541–550 of 644 posts

Re: Almost every infrastructure decision I endorse or regret

#541

Post by skrtskrt »

colechristensen wrote: post #53
CSMastermind wrote: post #10

So by and large I agree with the things in this article. It's interesting that the points I disagree with the author on are all SaaS products: > Moving off JIRA onto linear I don't get the hype. Linear is fine and all but I constantly find things I either can't or don't know how to do. How do I make different ticket types with different sets of fields? No clue. > Not using Terraform Cloud No Regrets I generally recom…

PagerDuty’s cheapest plan is $21 per user month OpsGenie’s cheapest is $9 per user month but arbitrarily crippled, the plan anybody would want to use is $19 per user month So instead of a factor of ten it’s ten percent cheaper. And i just kind of expect Atlassian to suck. Datadog is ridiculously expensive and on several occasions I’ve run into problems where an obvious cause for an incident was hidden by bad behavior…

Grafana OnCall can be self hosted for free or you can pay $20 a month, and still always have the option to migrate to self hosting if you want to save money

Re: Almost every infrastructure decision I endorse or regret

#542

Post by mjfisher »

aniforprez wrote: post #493
mjfisher wrote: post #347

Earlier quoted context omitted.

No, Jira loading is relatively OK and on par with other SPAs. It's got a CTRL+SHIFT+P style actions menu for tickets which helps cut down on point and click pain (especially for linking issues etc). Setting up statues and workflows and how they map to a board is relatively straightforward. There are lots of things where Jira falls short, but the pain points on an under-resourced self hosted instance of ten years ago…

Does Jira still have multiple flavours of markdown for different fields and editors? Last I used it, it used a different flavour for creating and editing a ticket. Also another flavour for bitbucket. None of these were compatible and it would convert between them in the backend but I was left confused every time when I would have to switch formatting styles

I remember that from a while back, and getting annoyed - it doesn't appear to be something that annoys me at the moment so it might have been fixed, but on reflection I tend to just use the default rich text editor now.

It takes markdownish input but converts it to rich text as you type - so asterisk-space starts a bullet point list, etc.

I actually can't remember if it has a dedicated markdown mode anymore; the rich text editing supports the usual shortcuts that mean I tend to stick with it.

Re: Almost every infrastructure decision I endorse or regret

#543

Post by morsecodist »

andreif wrote: post #514
geraldhh wrote: post #359

Earlier quoted context omitted.

why is that?

Why it's weird to blame them for product names? Because their purpose slightly different. I can see where negativity comes from and understand, but product name is a lot less important as consistent API experience. AWS is the best among big players by far, hats off and well-done to their teams and leadership. I hope the others will finally learn and follow.

My issue isn't just with the names themselves but they are emblematic of AWS's overall mentality. They want to have the AWS(TM) solution to X business case while other cloud providers feel more like utilities that give you building blocks. This obviously works for them and many of their customers I just personally don't care for it. It is probably to do with the level of complexity I am working at (*which is not very complex).

Also, I don't think trying to emulate AWS's support and consistent API makes sense as a strategy for other cloud providers. They will never beat AWS at their own game, it is light years ahead. If cloud providers want to survive they need to fill a different niche and try different things.

Re: Almost every infrastructure decision I endorse or regret

#544

Post by overstay8930 »

hardolaf wrote: post #432
jq-r wrote: post #297

Earlier quoted context omitted.

> but I'm just going to say that we run a few 8XL and 12Xl RDS instances and we pay ~40% off the sticker price. Genuinely curious, how do you that? We pay a couple of million dollars per year and the biggest spend is RDS. The bulk of those are 8xl and 12xl as you mention and we have a lot of these. We do have savings plans, but those are nowhere near 40%.

Yeah 40% seems like a pipedream. I was at a Fortune 500 defense firm and we couldn't get any cloud provider to even offer us anything close to that discount if we agreed to move to them for 3-4 years minimum. That org ended up not migrating because it was significantly cheaper to buy land and build datacenters from scratch than to rent in the cloud.

There are basically no discounts in govcloud

Re: Almost every infrastructure decision I endorse or regret

#545

Post by KronisLV »

tormeh wrote: post #389
jwr wrote: 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…

When talking about Hetzner pricing, please don’t change the subject to AWS pricing. The two have nothing in common, and intuition derived from one does not transfer to the other.

> The two have nothing in common

If all you need are some cloud servers, or a basic load balancer, they are pretty much the same.

If you need a plethora of managed services and don't want to risk getting fired over your choice or specifics of how that service is actually rendered, they are nothing alike and you should go for AWS, or one of the other large alternatives (GCP, Azure etc.).

On the flip side, if you are using AWS or one of those large platforms as a glorified VPS host and you aren't doing this in an enterprise environment, outside of learning scenarios, you are probably doing something wrong and you should look at Hetzner, Contabo, or one of those other providers, though some can still be a bit pricey - DigitalOcean, Vultr, Scaleway etc.

Re: Almost every infrastructure decision I endorse or regret

#546

Post by yellow_lead »

maccard wrote: post #402
yellow_lead wrote: post #264

Earlier quoted context omitted.

If you can do all that in 30 minutes (or even a few hours), I would love to read an article/post about your setup, or any resources you might recommend.

I've just done it a dozen times at this point. Hello world from gin-gonic [0], terraform file with a DO K8s cluster [1] and load balancer, and CI/CD [2] on deploy. There's even time to make a cuppa when you run terraform. We use this for our internal services at work, and the last time I touched the infra was in 2022 according to git [0] https://github.com/gin-gonic/gin [1] https://gist.github.com/donalmacc/0efbb0b37…

Thanks! Does DO K8s come with sufficient monitoring / logging or do you add anything?

Re: Almost every infrastructure decision I endorse or regret

#547

Post by overstay8930 »

davedx wrote: post #267

Utter insanity. So much cost and complexity, and for what? Startups don’t think about costs or runway anymore, all they care about is “modern infrastructure”. The argument for RDS seems to be “we can’t automate backups”. What on earth?

Everyone who says they can run a database better than Amazon is probably lying or Has a story about how they had to miss a family event because of an outage.

The point isn’t that you can’t do it, the point is that it’s less work for extremely high standards. It is not easy to configure multi region failover without an entire network team and database team unless you don’t give a shit about it actually working. Oh yea, and wait until you see how much SOC2 costs if you roll your own database.

Re: Almost every infrastructure decision I endorse or regret

#548

Post by crazygringo »

tw04 wrote: post #130
macNchz wrote: post #31

Earlier quoted context omitted.

> Sure, maybe if you are some sort of SaaS with a need for a small single DB, that also needs to be resilient, backed up, rock solid bulletproof.. it makes sense? But how many cases are there of this? Most software startups these days? The blog post is about work done at a startup after all. By the time your db is big enough to cost an unreasonable amount on RDS, you’re likely a big enough team to have options. If yo…

>By the time your db is big enough to cost an unreasonable amount on RDS, you’re likely a big enough team to have options. By the time your db is big enough to cost an unreasonable amount on RDS, you've likely got so much momentum that getting off is nearly impossible as you bleed cash. You can buy a used server and find colocation space and still be pennies on the dollar for even the smallest database. If you're doi…

> you've likely got so much momentum that getting off is nearly impossible as you bleed cash.

Databases are not particularly difficult to migrate between machines. Of all the cloud services to migrate, they might actually be the easiest, since the databases don't have different API's that need to be rewritten for, and database replication is a well-established thing.

Getting off is quite the opposite of nearly impossible.

Re: Almost every infrastructure decision I endorse or regret

#549

Post by jgalt212 »

andreif wrote: post #515
jgalt212 wrote: post #405

Earlier quoted context omitted.

It's nice when things do what they say on the tin. That being said, it's hard to build a "brand" when you start out with a generic name.

How many popular products have you named and launched? Naming products is hard to meet both usability and marketing objectives. This has never been as big of a problem for me, as GCPs APIs for example. Those are the true evil. Product names I care little for.

> How many popular products have you named and launched?

One, and you often times only need one.

Post reply on HN