Re:Amazon Translate
by kahnjw on Friday March 01, 2019 @05:29PM
(#19285973)
On the other hand some services from AWS are downright bad. For instance, Elastic Beanstalk is an operational nightmare. The one selling point is that it's easy to get started with, but from there it seems they rely on ops lock-in to pay the bills for this product. It's slow, clunky, and opaque. There are much better alternatives that don't force you to tradeoff usability and lock-in for initial ease of use.
[ Parent
| on HN ]
Remember that some services live their life (peak growth and in top 10 list of management), do their job (stable phase) and then run out of steam (tech landscape change, corporate priorities change). It is natural for folks to eventually move off beanstalk into lambda, ecs and forgate. In it peak, beanstalk was the go to service to set up an auto scaling app from code. People have moved on into containers and serverless now. Not so much about beanstalk being bad.
Re:Amazon Translate
by DanFeldman on Friday March 01, 2019 @06:42PM
(#19286387)
Then again, ELB was amazing a few years back when the tooling for dealing with AWS/GCP/Azure was not as mature. ELB wrapped a huge percentage of the use cases (webapps) in one or two configs.
Sure, now there's a ton of better/more scaleable/cheaper options, but ELB was great before.