AWS Elastic Beanstalk vs IBM Cloud Managed Istio

• 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

• Layers transparently onto existing applications
• Allows control of access and rules to be developed
• Creates metrics for usage

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

• Some more functionalities added could improve it better.
• Better technical user guidance.

Read full review

• Greatly reduced time in setting up and deploying test environments has saved a lot of hours and money.
• Near-zero maintenance means that we don't spend any time tending to servers, the app containers just work.
• The initial learning curve is a little steep to get services hosted in Elastic Beanstalk talking to external services like Redis, MongoDB, etc; but once one understands the pattern, development is a breeze.
• The command line interface has enabled us to build many utility scripts that simplify our development workflow, thereby saving time.

Read full review

• It reduced the complexity of network mesh (ingress/egress services).
• One tool with many solutions. No need to integrate monitoring tools or notification tools.
• It reduced the number of lines of YAML code.
• It reduced the number of labor hours.

Read full review