AWS Elastic Beanstalk vs Red Hat OpenShift

• 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

• The same as many similar K8 vendor solutions, OpenShift provides a managed Kubernetes environment with advanced facilitative components built-in.
• It provides the life cycle management/monitoring toolset to help users better visualize and understand both the application and infrastructure environment.
• Provides the scaling and recovering mechanism to ensure the high resilience of the application.
• CI/CD pipeline integration following the DevOps concept.

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

• The shift from v2 to v3 was a huge transition, and Red Hat [OpenShift] really failed at making this step easy for users - their documentation at the time was fairly lacking
• When things go wrong it can be hard to diagnose

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

• Reduce [the] friction of monitoring environments. This leads to [a] quicker troubleshooting process.
• Completely remove the need to authenticate each and every time you want to check on a specific environment.
• Faster deployment workflow increases [the] efficiency of developers when testing in lower environment containers.

Read full review