TrustRadius Insights for IBM Cloud Managed Istio are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Ease of Use and Implementation: Multiple users have found the platform to be cloud-managed, making it very easy to use and implement. They appreciate the simplicity in adoption that this feature offers, allowing for a smooth transition for teams integrating the platform into their workflow.
Effective Cluster Management: Reviewers have highlighted the platform's capabilities in managing cluster connectivity, ingress/egress network configuration, and providing a user-friendly dashboard for monitoring application health. This functionality reduces complexity, especially benefiting new users as they navigate through various aspects of cluster management effortlessly.
Security Features and Monitoring Capabilities: Users have praised the platform's ability to ensure pods' security by running only with specific users. They also appreciate its strengths in traffic management, including robust security features such as access control measures and comprehensive monitoring capabilities that enhance overall operational efficiency.
It is beeing used only by IT department to manage the mesh traffic. Periodic updates helps us to deal with daily issues. We use it to communicate microservices such us Microsoft Azure App Services, Azure SQL among others. Also it help us finding and solving the issues with different type of reports.
Pros
Debug issues
Monitoring
allows many services form many different sources
Cons
the software upates sometimes get problems
need more documentation
should have a better customer support
Likelihood to Recommend
If you have many API calls, If you need quick issue debugging or If you want to connect many sources, this software is good for your company, Having the monitoring and the reporting in one system, also is a plus
IBM Cloud Managed Istio is being used across our organization and not only in few particular departments. It's being used mainly for the management of different microservices which takes care of connecting them with each other across the network. It's also secure and provides flexibility irrespective of which vendor is providing the microservices.
Pros
It is cloud managed and very ease to use.
Implementation is simple and can be easily adopted.
It lessens the complexity and hence is very good for the new users.
Cons
Some more functionalities added could improve it better.
Better technical user guidance.
Likelihood to Recommend
IBM Cloud Managed Istio is best suited for small to mid-scale enterprises especially the startups who have a requirement of cloud managed services from experts in the industry. However, it could be a little less appropriate for the bigger market players who have their own infrastructure and can easily manage on their own and are just looking for some traffic management services.
VU
Verified User
Analyst in Information Technology (5001-10,000 employees)
We are into banking services. All our applications are microservices and we have multiple microservices for example Azure app services, Databricks, Azure SQL managed services, etc., [all of] which communicate with each other for a response. Managing the network services communication for each service is a complex process in Azure Kubernetes Services. So we integrated IBM Cloud Managed Istio with AKS cluster. Now with this new integration, it helps us to manage the routing of services, [where] we can very easily define traffic rules (i.e. ingress and egress networks). It helps to debug application connectivity issues with different types of graphs, i.e. useful in debugging.
Yes, it is used across the whole organization.
Pros
Managing the cluster, i.e. pods connectivity
Managing the ingress/egress network configuration for routing of service flow
Nice dashboard for monitoring the health of application
Trigger alerts to pager duty if something goes wrong to appropriate team
Pods (container) security, i.e. it will only run with specific users also got resolved
Cons
Complex to understand. IBM needs to provide more example documentations.
Updating the [IBM Cloud Managed Istio] to latest version can sometimes break the application.
Implementation of integration of [IBM Cloud Managed Istio] with other tools like Grafana, Sumologic for monitoring is very complex; it can be improved.
Likelihood to Recommend
Clearly, the [IBM Cloud Managed Istio] tool is very useful when you have multiple services and each service is connecting with other services through APIs in different networks. To manage this type of complex network, [IBM Cloud Managed Istio] is very useful. It comes with a license that can increase the billing of your project so make sure if your application network mesh, monitoring cannot be managed on your own then you can use it.
If your application is not very complex then you have many tools available like Grafana, Prometheus, Sumo Logic, which you can integrate individually with your cluster and implement. In this type of scenario, it is better to not use [IBM Cloud Managed Istio] and it will serve your purpose as well.
We started out using the software [IBM Cloud Managed Istio] within a small part of one of the divisions. It rapidly spread to usage through the entire product line. We are in the process of rolling it out to other product lines within the entire organization. We are able to create more visability to ongoing projects that previously were managed in silos without knowing start and or end dates and the details.
Pros
Layers transparently onto existing applications
Allows control of access and rules to be developed
Creates metrics for usage
Cons
Training material for new users
Generating specific reports
Adding metrics to existing report
Sharing reports among user groups
Likelihood to Recommend
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.
It's used across the organization as a microservices traffic manager.
Pros
Traffic management
Security
Monitoring
Cons
Still missing functionalities for a full usage as traffic director.
Likelihood to Recommend
Currently use for traffic management for IOT edge devices and their sensor data flows. IoT generates lots of data and this data needs to processed at the edge devices before sending the processed result to cloud. Hence there is always ingress and egress data traffic in and out of the IoT edge devices which needs traffic management
VU
Verified User
Engineer in Information Technology (1001-5000 employees)
