Need advice about which tool to choose?Ask the StackShare community!
Kong vs Tars: What are the differences?
What is Kong? Open Source Microservice & API Management Layer. Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.
What is Tars? A high-performance RPC framework. It is an open-source microservice platform. It contains a high-performance RPC framework and a service management platform. Based on Tars, you can develop a reliable microservice system efficiently It is designed for high reliability, high performance, and efficient service management. By significantly reducing system operation work, developers can focus on business logic and meet fast changes of user requirements..
Kong can be classified as a tool in the "Microservices Tools" category, while Tars is grouped under "Remote Procedure Call (RPC)".
Some of the features offered by Kong are:
- Logging: Log requests and responses to your system over TCP, UDP or to disk
- OAuth2.0: Add easily an OAuth2.0 authentication to your APIs
- Monitoring: Live monitoring provides key load and performance server metrics
On the other hand, Tars provides the following key features:
- Microservices platform
- Multiple programming languages supporting
- High performance
Kong and Tars are both open source tools. It seems that Kong with 25.8K GitHub stars and 3.31K forks on GitHub has more adoption than Tars with 8.35K GitHub stars and 1.98K GitHub forks.
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 Tars
Sign up to add or upvote prosMake informed product decisions
What is Kong?
What is Tars?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Tars?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kong?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+26