Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by iowej23oij on Monday July 18, 2022 @01:21PM
(#32140775)
I can create a fully functional website in 1 minute using Azure Web Apps, but it will take me 2 days to configure millions of options for AWS Beanstalk... So definitely Azure is better, because AWS is extremely overengineered and needs a lot of administration overhead.
[ Parent
| on HN ]
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by master_crab on Monday July 18, 2022 @01:25PM
(#32140809)
The fact that you are considering Beanstalk leads me to believe you have some timely gaps in your AWS knowledge.
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by iowej23oij on Monday July 18, 2022 @01:37PM
(#32140940)
With many hundreds of services every single person has gaps in AWS knowledge.
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by 202206241203 on Monday July 18, 2022 @02:13PM
(#32141462)
Strange names also help hiding the semi-duplicate products.
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by bratbag on Monday July 18, 2022 @01:33PM
(#32140892)
I can get a website up in around a minute with aws amplify.
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by surfer7837 on Monday July 18, 2022 @03:31PM
(#32142480)
No-one uses Elastic Beanstalk -- use ECS instead. With ECS Copilot you can do it in 1/2 commands.
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by tracker1 on Monday July 18, 2022 @06:13PM
(#32144700)
I thought Beanstalk was decent for Docker before they had EKS and (whatever the new thing is called) though.
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by tracker1 on Monday July 18, 2022 @06:12PM
(#32144689)
Kind of agree on that, but I almost feel the opposite with AWS Lambda vs Azure Functions... The advantage of functions, is of course direct access options over http.
Re:My Poor Experience With Azure (or why I'm sticking with AWS)
by kup0 on Wednesday July 20, 2022 @11:00AM
(#32166696)
It is amusing that the replies/suggestions to your post recommend multiple different AWS solutions instead of Beanstalk. Definitely confirms the problem of AWS having a confusing amount of overlapping products