AWS Elastic Beanstalk vs Mule ESB

• 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

• It is best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
• Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
• Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
• Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.

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

• Make sure to not over-engineer shared components. It can complicate development
• Create a roadmap for where you are going - if not, you may miss components
• I suggest getting support, otherwise it could be a difficult learning curve

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

• Overall a great tool for complex integrations

Read full review