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…
I returned to AWS and was reminded why I left
91–100 of 684 posts
Re: I returned to AWS and was reminded why I left
#92Why do people even bother with cloud? I’ve a couple of apps doing a few million a day. I am using Hetzner and before that used DigitalOcean. Mind you, for close to a decade. People are unnecessarily complicating stuff, and these clouds can go very expensive very quickly. Recently, I came across a company and they were spending $20k a month on GCP. I am like, are you kidding me, $20K for the kind of stuff you do??? It…
> burning money in cloud
I suspect there's two reasons why this happens.
One is just the disassociation with opex that seems ever present in the VC model. The other is that many startups settle in on a ops solution before hiring ops and the cost of switching isn't that attractive until they're faced with a dwindling runway and a down round.
Re: I returned to AWS and was reminded why I left
#93GCP would be perfect if they didn't have a history of randomly dropping quotas on startups, causing them downtime
Re: I returned to AWS and was reminded why I left
#94> 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…
That he is complaining about his email being down or that he trusted AWS at all with email?
Re: I returned to AWS and was reminded why I left
#95Years 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…
> 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 don’t want to be the one defending AWS, but I don’t think that this is a valid reason not to like them. I mean, pric…
Re: I returned to AWS and was reminded why I left
#96Re: I returned to AWS and was reminded why I left
#97Earlier 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…
Walmart pulling up top a small town, opening a single business, paying everyone minimum wage is not 'competition is good'. Just try a little bit of understanding.
Even if it weren't AWS, someone else with enough determination could use the same open source code to create a compelling alternative taking away business from the original authors. Trying to use social norms to make people not do that is not effective. You need mechanisms that can be enforced via legal procedures to be effective.
Re: I returned to AWS and was reminded why I left
#98Earlier quoted context omitted.
> it's really weird to say that the forks "resulted" in the license changes when those forks where a response to the license changes But those license changes were a response to how AWS was monetizing their work in ways unsustainable for the upstream projects.
> But those license changes were a response to how AWS was monetizing their work in ways unsustainable for the upstream projects Or seen from the other side, these projects chose initial licenses that didn't fit with their wants for how others should use their project, in this mind. If you use a license that gives people the freedom to host your project as a service and make money that way, without paying you, and yo…
Re: I returned to AWS and was reminded why I left
#99Years 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…
> 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 don’t want to be the one defending AWS, but I don’t think that this is a valid reason not to like them. I mean, pric…
But that's the problem: The complexity of doing that properly is pretty much the same as just doing your own hardware (which is what I'm working with most of the time - handling stuff on physical servers). And at that point the question should be why you're paying AWS so much money and pay your people to automate AWS workflows when you could just pay them to automate workflows on physical hardware, which would be way cheaper to run than the AWS instances.
Re: I returned to AWS and was reminded why I left
#100Years 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…
If it bothers you that you need to open two tabs for cross-checking the costs, you may want to avoid every cloud provider, not just AWS.
Once you have NAT gateways, CloudFront, S3, auto scaling, loadbalancers, etc, calculating the cost becomes an art rather than an exact science. And if you don't use these, there is no point of using AWS, there are plenty of "cheap" VPS providers.