Engine Yard vs. IBM Cloud Managed Istio

It is best for rapidly getting your application to the cloud without worrying about standing up cloud infrastructure

Incentivized

It is a perfect application when you have multiple users and/or developers and you want to create rules and standards for access and the ability to change access levels. The reporting of usage is good, but adding more granularity into the metrics that have been used to measure are not specific enough. They provide detail but drilling into the detail would be more appropriate i.e. access to the baseline data.

Incentivized

• Quick deployments
• Easily integrate your code from GitHub
• Ability to recover site quickly to different zone when AWS has a widespread outage

Incentivized

• Debug issues
• Monitoring
• allows many services form many different sources

• Embracing new Amazon Web Servicess(AWS) features
• Security groups need more granularity
• Audit trails of what happens by who in environment, especially when VM is deleted

Incentivized

• Still missing functionalities for a full usage as traffic director.

Incentivized

Ease of use

Incentivized

Training and usage support available

Incentivized

More closely aligns to native AWS

Incentivized

1) One-stop solution for all the complex network connectivity managed by [IBM Cloud Managed Istio]. 2) Nice dashboard to understand the flow. 3) Easy to troubleshoot the service if any one of the APIs is not responding. 4) We can integrate it with Azure Kubernetes service and other cloud provider Kubernetes services. 5) Monitoring the health of the pods can be easily configured and alerts can be triggered very accurately with this tool.

Incentivized

• Positive in the sense that we can deploy new applications quickly for MVP

Incentivized

• Management burden is reduced resulting in positive ROI.
• Application is being seamlessly instrumented with good impact on business.

Incentivized