AWS Elastic Beanstalk vs Azure App Service

• AWS Elastic Beanstalk was easy to implement, we only had to insert the application code to have it up and running in a few minutes. This helps us to launch company campaigns for different areas such as marketing, commercial and human resources.
• It has a fast learning curve, since the training material of the platform is public on the manufacturer's portal, furthermore it is easy to interact and intuitive for developers.
• The productivity of the equipment is optimized since they are not worrying about preparing the platform or infrastructure, they only have to attend to what is required by the application and its operation and this maintenance.
• The indicators and metrics that it has, ensure that the application cannot be saturated and have a performance problem, with AWS Elastic Beanstalk the application can scale resources when needed automatically.

Read full review

• Single source for ALL of our apps.
• Revision control is easy with the info we embed into the apps.

Read full review

• Limited to the frameworks and configurations that AWS supports. There is no native way to use Elastic Beanstalk to deploy a Go application behind Nginx, for example.
• It's not always clear what's changed on an underlying system when AWS updates an EB stack; the new version is announced, but AWS does not say what specifically changed in the underlying configuration. This can have unintended consequences and result in additional work in order to figure out what changes were made.

Read full review

• Abstraction of computing resources like Heroku does with dynos.
• Azure Portal overall is pretty bloated and that affects managing Azure App Service applications.

Read full review

• till now we had not Calculated ROI as the project is still evolving and we had to keep on changing the environment implementation
• it meets our purpose of quick deployment as compared to on-premises deployment
• till now we look good as we also controlled our expenses which increased suddenly in the middle of deployment activity

Read full review

• Azure App Service has allowed us to quickly deploy high-budget projects very quickly, netting us a healthy profit vs the cost to develop. (We make, on average, about 10x what it costs to get up and running per project thanks to how easy it is to implement a skeleton framework.)
• Costs are low to run the services thanks to the scaling functionality that comes with Azure App Service. We can utilize less resources during slow times and save hundreds of dollars per month vs costs of traditional servers.

Read full review