Istio provides a significant saving for us in terms of costs since it is open source.
However, Istio can still come at a price. It has a steep learning curve and might require more manpower hours or outside experts in the beginning of the process. In addition, it also consumes a lot of resources, as it is running on all the pods in our clusters. Istio can consume anywhere between 20ml CPU and 800ml CPU. The default CPU request for the proxy is 100ml CPU. It is hard to estimate how much you will spend until you set up your system.
My experience with pricing, setup cost, and licensing includes being the one who first and foremost does the trial, integration, and architecture design along with the training, and in costing, I take responsibility for that.
Infra , DevSecOps & Automation Architect at Zuellig Pharma
Real User
Top 10
Nov 5, 2024
Istio itself is open-source, but using it involves infrastructure costs due to CPU and memory allocation. Integration with observability tools like Prometheus, Grafana, and Elasticsearch incurs additional costs.
VP of Engineering at a healthcare company with 201-500 employees
Real User
Jan 16, 2021
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.
Connect
Intelligently control the flow of traffic and API calls between services, conduct a range of tests, and upgrade gradually with red/black deployments.
Secure
Automatically secure your services through managed authentication, authorization, and encryption of communication between services.
Control
Apply policies and ensure that they’re enforced, and that resources are fairly distributed among consumers.
Observe
See what's happening with rich automatic tracing, monitoring, and...
Istio provides a significant saving for us in terms of costs since it is open source.
However, Istio can still come at a price. It has a steep learning curve and might require more manpower hours or outside experts in the beginning of the process. In addition, it also consumes a lot of resources, as it is running on all the pods in our clusters. Istio can consume anywhere between 20ml CPU and 800ml CPU. The default CPU request for the proxy is 100ml CPU. It is hard to estimate how much you will spend until you set up your system.
My experience with pricing, setup cost, and licensing includes being the one who first and foremost does the trial, integration, and architecture design along with the training, and in costing, I take responsibility for that.
Istio itself is open-source, but using it involves infrastructure costs due to CPU and memory allocation. Integration with observability tools like Prometheus, Grafana, and Elasticsearch incurs additional costs.
Istio is all open source. So, everything I do is mostly through Google. I'm probably closer to Google in partnership than I am with Istio directly.
We use the tool's open-source version, so there are no hidden fees or additional costs associated with it.
You can deploy Istio free of cost and don't need to pay for it.
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.