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

I returned to AWS and was reminded why I left

fourlightyears.blogspot.com

Post reply on HN
Print view View original

221–230 of 684 posts

Re: I returned to AWS and was reminded why I left

#221

Post by graemep »

djyde wrote: post #33

I've transitioned between cloud services and self-hosting a few times: 1. Vercel Phase My first project used Vercel. Since my project was Next.js, the experience was decent. But as my project gained some users, I found that even for projects under 100 users, I needed to pay $20 per month. Since my service didn't require high performance, this cost felt steep. 2. Self-host Phase (Hetzner + Coolify) Later, I started se…

> Even though they were containerized with Docker, managing them was still troublesome

Did docker make it easier?

The only issue I have with PostgreSQL is a bit of migration effort moving to new major versions.

> I needed to pass various system and environment variables between services, which was very tedious.

Was docker making this harder?

Re: I returned to AWS and was reminded why I left

#222

Post by benoau »

the__alchemist wrote: post #171
ceejayoz wrote: post #44

Earlier quoted context omitted.

That won't last. https://www.heroku.com/blog/an-update-on-heroku/

Uhoh. I don't know what that means, but I unfortunately detect double-speak.

No longer developing new features or offering new contracts, but eVerYtHinG iS FiNe.

Re: I returned to AWS and was reminded why I left

#224

Post by graemep »

embedding-shape wrote: post #66
chuckadams wrote: post #11

Earlier quoted context omitted.

You can just spin up a raw VPS on EC2 or Lightsail, give it a public IP, and call it a day. You aren't required to implement every enterprise pattern in the book.

If there is any single service I'd avoid on AWS it's Lightsail, it'll cost you a lot more than almost anything out there, is slow as molasses (even tiny services can need tens of minutes to deploy) and you'll experience random failures not even AWS reps can explain to you. Avoid at all costs. It's a ghost of its former self, but I'd probably still rather use Heroku today than being forced to use Lightsail even once a…

I have only use lightsail for one project with two VPSs, but it just works like a VPS (two, because we have another for staging). Price is competitive.

Its not my favourite, but its not terrible.

Re: I returned to AWS and was reminded why I left

#225

Post by dijit »

swasheck wrote: post #189
dijit wrote: post #173

Earlier quoted context omitted.

Honestly, this is so divorced from reality that I'm curious if you've ever actually spoken to a CFO before.

please educate instead of insult. happy to hear your response. that is why we’re here, after all.

Sure. CFOs optimise for fewer vendor relationships; fewer invoices, fewer things to talk about during compliance, less reconciliation overhead. Consolidated spend also improves their negotiating position. So when AWS offers good-enough Elasticsearch bundled into an existing relationship, it wins regardless of whether the original is better supported or better value.

"More efficiently" means procurement efficiency, not operational efficiency. They're not the same thing.

Re: I returned to AWS and was reminded why I left

#226

Post by nijave »

znpy wrote: post #34

> Of course I do not pay for premium support, so I have to wait the 24 hours that they said it would take them to reply. It's 3 days and AWS support has not replied. The writing has been on the wall for a few years now, and this is particularly evident to those thar have worked at AWS: Amazon is in its day-2 era. Amazon being in its day-2 era means that most of what has been written in the past twenty years about Ama…

Imo AWS support is pretty decent compared to other vendors. Azure was by far the worst I've ever dealt with--engineers becoming adversarial and passing blame in tickets without actually resolving anything.

I've had some run-ins with poor AWS support and have even gotten bill credits/refunds when they offered incorrect advice. It really depends on the service but in general they're fairly good.

Re: I returned to AWS and was reminded why I left

#227

Post by andrepd »

ipaddr wrote: post #56
rpdillon wrote: post #50

Earlier quoted context omitted.

They have a problem with their business model, then. License changes to a formerly open source project are costly. The community reacts very strongly when license terms change after they've come to depend on a product, and they should. Why do we apply this standard to MongoDB but not to Apache, Linux, Postgres, or MariaDB? One purpose of an open source license is to allow many providers to provide the service. As I'v…

Competition would mean Amazon creating their own software. Taking software others made and using your monopoly eco-system and scale to drive the original creator out of the game kills the product. Many support breaking up Amazon so others could compete not killing small entities and growing Amazon.

There's a lesson there then, isn't there? Use GPL

Re: I returned to AWS and was reminded why I left

#228

Post by kassner »

panny wrote: post #104
finaard wrote: post #84

> My business email system still does not work. This is always the weird things in those rants. He's complaining that after 4 days his mails are offline. Now I'm doing a mix of physical servers in rented rackspace, and rented servers - but even there I can have billing mixups where they deactivate servers for no good reason. And to get email working again the limiting factor would be the DNS TTL - new servers would b…

>new servers would be online somewhere else within hours of it going down Yeah, no that's not how it works with email. You have to build reputation for weeks or receivers throttle you.

It is pretty much unacceptable to have a domain bouncing emails, so I’d be out of the provider before the MX TTL even expires.

For outgoing emails, reputation is a huge issue, but at the same time it’s also fairly trivial to set up a (different) 3rd-party (gmail, outlook, sendgrid, whatever) with previous reputation so you can get back communicating.

Re: I returned to AWS and was reminded why I left

#229

Post by ceejayoz »

chii wrote: post #207
ceejayoz wrote: post #138

Earlier quoted context omitted.

Yes. But so would financially contributing to the folks who did the work.

If those folks wanted money for their work, they should be charging a price for it.

That’s what they eventually did, yes.

But it’s ok to be voluntarily grateful for hard work.

Re: I returned to AWS and was reminded why I left

#230

Post by aorloff »

sudosteph wrote: post #123

I'm surprised by the author's hate towards DynamoDB. It's probably one of my favorite AWS Services. Great availability and no operational overhead. Cost was pretty minimal too each time I've used it, but you do need to spend some time architecting your data model up front, and that requires reading service docs and understanding it.

Dynamo, and a lot of the other services mentioned (Lambda) have very specific use cases. Do not use happy fun key value store as your database.
Post reply on HN