Need advice about which tool to choose?Ask the StackShare community!
Kong vs Mashery: What are the differences?
Kong and Mashery are both API management platforms used to control and manage APIs. However, there are key differences between the two that set them apart.
Integration with different infrastructure: Kong is built on top of Nginx and can be deployed on any infrastructure including on-premise, cloud, or hybrid. On the other hand, Mashery is a cloud-native API management solution owned by TIBCO and primarily operates in the cloud environment.
Open-source vs proprietary: Kong is an open-source API gateway that offers a free community edition with basic features and a paid enterprise edition with additional functionalities. Mashery, on the contrary, is a proprietary solution with its features and capabilities limited to what is provided by the vendor.
Flexibility and customization: Kong allows more flexibility and customization through its plugin architecture, which allows developers to extend its functionalities and integrate with other services or systems easily. Mashery, on the other hand, provides less room for customization and relies more on the out-of-the-box features provided by the vendor.
Developer community and ecosystem: Kong has a large and active open-source community that constantly contributes to the platform's development and improvement. This results in a wide range of available plugin options and frequent updates. Mashery, being a proprietary solution, has a smaller developer community and limited ecosystem in comparison.
Deployment options: Kong offers multiple deployment options, including Docker, Kubernetes, and VM-based installations. This provides flexibility and adaptability to different infrastructure requirements. Mashery, being a cloud-native solution, primarily operates in the cloud and may have limitations when it comes to on-premise or hybrid deployments.
Pricing model: Kong's pricing model is based on a subscription and usage-based model, with different tiers available for different levels of support, performance, and features. Mashery, on the other hand, follows a traditional license-based pricing model, which may not be as flexible or scalable for organizations with varying needs.
In Summary, Kong offers more flexibility, customization options, and a larger developer community compared to Mashery, while Mashery provides a cloud-native solution with a more streamlined and controlled environment.
Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.
Pros of Kong
- Easy to maintain37
- Easy to install32
- Flexible26
- Great performance21
- Api blueprint7
- Custom Plugins4
- Kubernetes-native3
- Security2
- Has a good plugin infrastructure2
- Agnostic2
- Load balancing1
- Documentation is clear1
- Very customizable1
Pros of Mashery
- Hard to use1
- Cheese-like1