Istio Overview

Istio is the #1 ranked solution in our list of top Service Mesh tools. It is most often compared to Kong Kuma: Istio vs Kong Kuma

What is Istio?

Intelligently control the flow of traffic and API calls between services, conduct a range of tests, and upgrade gradually with red/black deployments.

Automatically secure your services through managed authentication, authorization, and encryption of communication between services.

Apply policies and ensure that they’re enforced, and that resources are fairly distributed among consumers.

See what's happening with rich automatic tracing, monitoring, and logging of all your services.

Pricing Advice

What users are saying about Istio pricing:
  • "It is on the less expensive side. It provides a significant saving for us in terms of cost and other things. It is open-source. We just download it from the open-source framework and use it."

Filter Reviews

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
VP of Engineering at a healthcare company with 201-500 employees
Real User
Top 10Leaderboard
Balances load well, saves effort, and is open-source and free

What is our primary use case?

We are using the Istio framework as the service mesh for our microservices. We use it as a load balancer for the network traffic that is coming in. We have HTTP traffic that is coming into our service, and this traffic has to go to multiple other services. Typically, in microservice, you have a class of servers that need to talk to each other. There is a proxy server that talks to these servers on the mesh layer.

Pros and Cons

  • "The load balancing, service application, and monitoring of the life of the service are valuable features. We use it for authentication of call services, load balancing the calls among the service providers on service instances, and monitoring the health of the services."
  • "For our use case that we applied it to, there were graph queues and the calls that were coming in. There were the things that we couldn't apply at the time, but it kind of worked."

What other advice do I have?

As with all evaluations, it depends on what you are benchmarking it against. When we look at how we evaluated it and how we arrived at it, in our case, it worked out quite well. There is no pricing involved because we are using open-source. We simply download it and then incorporate it into our code. Now, from that perspective, if the company has a good number of developers who are willing to read, understand, and adapt to the culture of innovation, this doesn't become an issue. These are the things that people will have to do. No matter which tool you use, you will have to eventually get to…