[tacker2000]

Hilariously true. Yes, AWS has some services that are cheap and not really replaceable, like S3, but once you come near high performance EC2 and RDS and add multi-region in, you’ll really have a bad time. Believe me, Ive been there and in the end had to migrate most of the applications to another provider or host on prem.

[Pokepokalypse]

I've helped with two migrations, and warned them; they didn't listen.

Last place also did datadog for log aggregation. So Bezos' hands in their pockets, datadog's paws on their money.

[blandflakes]

Logs are something I didn't love self-hosting, but I also don't have a good sense that ELK was really an ideal setup for that. I can imagine running my own hardware, what's out there for logging?

(DD is super expensive, as you've said)

[hughrr]

The only thing I can actually suggest is to avoid the hell out of logging if you can. It’s a really expensive concern and should be treated so from day one. If your system has nothing actionable to log them don’t log it.

At a high level from observations of trying to handle 100Gb a day.

Cloudwatch is inflexible and expensive.

ELK is expensive to run and administer. The commercial variants are even worse.

Splunk is expensive and slow.

Datadog is expensive.

Loki is expensive to run and administer.

ryslogd and grep starts to feel like a viable solution eventually. Then you realise that you need about 50MB of that 100G a day of logs and enlightenment comes.

[blandflakes]

Thanks for the response, yeah that resonates. I think the sheer volume of logs has been what necessitates expensive solutions.

I've found that my current team really relies on those and an event store for observability, and it's just clunky and awful. Logging for, well, logging purposes instead would be a dramatic improvement.

[christophilus]

Eh. S3 is easily replaced by Wasabi. And less easily by minio.

[GormanFletcher]

Wasabi has an important 'gotcha': they charge you for a minimum of 90 days of retention, even if you delete an object seconds after creating it.

https://wasabi.com/paygo-pricing-faq/#minimum-storage-durati...

That detail isn't mentioned anywhere on their pricing page or cost comparison calculator: https://wasabi.com/cloud-storage-pricing/

I don't find that pricing objectionable on its own, but I'm wary of shopping with a vendor that advertises price as their main selling point, but buries such a potentially costly pricing detail.

[hughrr]

Damn that’s cheap on wasabi. No egress fees! Thanks for pointing this one out.

[snuxoll]

Do note that wasabi is aimed for long-term retention of cold data. There's no egress, but there is a fair usage policy (2x data stored IIRC).

[christophilus]

I use it for live data, but I put it behind BunnyCDN. I serve a few terabytes per month using that setup, no problem.

Most real world uses that I’m aware of follow the 80/20 rule, meaning you’ll store much more than you serve. And your hot paths are quickly cached by a CDN.

[ignoramous]

If any AWS service has replacement at this point, it has got to be S3 (unless locked-in via peripheral aws services).

https://wasabi.com, https://backblaze.com, https://min.io some of the ones I've seen frequently mentioned on news.yc