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

361–370 of 684 posts

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

#361

Post by catlifeonmars »

ChrisBland wrote: post #17
benoau wrote: post #12

Earlier quoted context omitted.

What amazes me is how Heroku absolutely nailed what most web apps need nearly 20 years ago.

I miss heroku dearly. somewhere at Salesforce there is an exec who killed the product and shifted it to enterprise and is now looking at the vibe coding revolution seeing their opportunity missed.

More likely than not they’re probably long gone, or have completely forgotten. The idea that someone out there regrets that decision is laughable. The fact that it’s laughable is sad.

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

#362

Post by tedivm »

jeremyjh wrote: post #315
ipaddr wrote: post #56

Earlier quoted context omitted.

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.

They knew what they were doing. They released OSS to build traction and a community. In some cases, the community contributed quite a lot to the quality of the software - even if not a lot of code. It never would have gained any traction or interest from enterprise buyers without that. Then that valuable software they had already given away was used to build a business that couldn’t create enough value on top of it.…

AWS literally paid for developers for the redis project, including the salary of core members. It's not like they didn't contribute back to the community.

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

#363

Post by clickety_clack »

aljgz wrote: post #49

Years ago, I joined a company, took over a dev team and was asked to launch the product in 3 months. They were using AWS, so I logged in the account to add a few more machines. Right there, in front of my eyes, were the signs of an adversarial, abusive relationship. The UI to fire up a new machine did not show me the price. I had to look up the price in another table that did not have the specs. I had to have the two…

People don’t seem to realize how simple pricing can be made for the user. I switched to digital ocean too, and it’s great. I think people think it’s not really engineering if it’s not complicated, so they stick with these insane AWS/GCP/Azure setups. But it’s not 2012 anymore, this stuff has been figured out and commoditized, and managing your cloud setup should be “easy” for 99% of products.

Edit: and when I say “99% of products”, I mean “99% of products where the team thinks they are building something too complicated for a simple setup”

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

#364

Post by zsoltkacsandi »

zsoltkacsandi wrote: post #195
sillyfluke wrote: post #163

Earlier quoted context omitted.

Now explain why they don't have a killswitch for a user defined spending limit.

You can set up cost-based alerts (actual or forecasted) that send notifications via email or SNS. Based on this you can set up automations, such as applying an IAM policy to prevent further resource creation, shut down resources, etc.

Interesting to see that some people assumed there are no kill-switch mechanism, and when it turns out they just did not know about it, the (totally valid and factful) comment gets downvoted because it is against their initial assumption. Not what I would have expected on a professional forum.

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

#365

Post by tedivm »

ceejayoz wrote: post #138
ncruces wrote: post #106

Earlier quoted context omitted.

That's fair, but forking the FOSS version is also an adequate response.

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

AWS literally did that. They paid for full time developers to contribute back to the redis code base, including core redis developers. If you actually look at the redis code base the majority of it was written by people who never worked for redis.

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

#366

Post by BirAdam »

noprocrasted wrote: post #267
sandruso wrote: post #124

Earlier quoted context omitted.

100%. I'm not really sure why we all agreed that deployment is somehow the hardest thing that you need to outsource when setting the linux server is one the richest experience you can get and it will pay dividents forever.

There's a multibillion dollar industry that lives only because they managed to successfully convince an entire generation of "engineers" to become helpless and not be able to serve an HTTP response using their own hardware even if their life depended on it.

It’s easy to convince developers of a thing if it starts with: “you don’t need to learn X anymore”

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

#367

Post by bironran »

GCP has it's own share of issues.

...

I was writing a long vent about GCP but the mix of issues we had, just in the last few weeks, was too identifying and I don't want to sour an already tremulous relationship, as much as I'd like to spill it all here.

Let's just sum it up with resource crunch and degraded services because, apparently, when one customer signs a $200B deal [1] all the "just a few $10M" get thrown to the wayside.

AWS is also affected. Time to go to Azure? I never thought I'd say those words.

[1] https://www.engadget.com/2165585/anthropic-reportedly-agrees...

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

#368

Post by ceejayoz »

ipaddr wrote: post #353
ceejayoz wrote: post #204

Earlier quoted context omitted.

Good. E-mail based 2FA is bad, and they appear to support TOTP too as an option, as they should. Wish they supported U2F though.

Why is email based 2fa bad but phone good? There are classes of issues you get through phone 2fa compared to email

Typically, you can also reset password via email, so it's really only one factor. Compromised email = compromised server.

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

#369

Post by jeremyjh »

tedivm wrote: post #362
jeremyjh wrote: post #315

Earlier quoted context omitted.

They knew what they were doing. They released OSS to build traction and a community. In some cases, the community contributed quite a lot to the quality of the software - even if not a lot of code. It never would have gained any traction or interest from enterprise buyers without that. Then that valuable software they had already given away was used to build a business that couldn’t create enough value on top of it.…

AWS literally paid for developers for the redis project, including the salary of core members. It's not like they didn't contribute back to the community.

They pay for a lot more open source work than that as well, but they also don't get to make any special claims for doing that. None of it is charity - it is simply in the collective interest of a lot of tech companies to commoditize and share the costs of infrastructure software. Even shaming freeloaders is uncalled for and against the ethos of OSS, which is sort of implied in making your statement.

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

#370

Post by BirAdam »

da02 wrote: post #134
rglover wrote: post #109

You can accomplish a lot by just having a basic knowledge of Linux sysadmin. I was clueless and then learned some systemd-and-curl-fu. Will never forget the "holy sh*t, this is deceptively simple" moment. A bit more research and I found that beyond convenience and specialty APIs, you really just don't need a lot of this stuff to run a healthy system (since reducing absolute cloud dependence, my reliability has gone t…

How do you deal with the few minutes of downtime when you do kernel/OS/software upgrades?

You put nginx or Haproxy in front of the hosts, drop the one that needs maint from the pool, and re-add once it’s ready.
Post reply on HN