Need advice about which tool to choose?Ask the StackShare community!
Kong vs Yeoman: 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 Yeoman? A set of tools for automating development workflow. Yeoman is a robust and opinionated set of tools, libraries, and a workflow that can help developers quickly build beautiful, compelling web apps. It is comprised of yo - a scaffolding tool using our generator system, grunt - a task runner for your build process and bower for dependency management.
Kong and Yeoman are primarily classified as "Microservices" and "Front End Scaffolding" tools respectively.
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, Yeoman provides the following key features:
- Lightning-fast scaffolding — Easily scaffold new projects with customizable templates (e.g HTML5 Boilerplate, Bootstrap), RequireJS and more.
- Great build process — Not only do you get minification and concatenation
- I also optimize all your image files, HTML, compile your CoffeeScript and Compass files, if you're using AMD, I will pass those modules through r.js so you don't have to.
"Easy to maintain" is the top reason why over 28 developers like Kong, while over 119 developers mention "Lightning-fast scaffolding" as the leading cause for choosing Yeoman.
Kong and Yeoman are both open source tools. Kong with 22.2K GitHub stars and 2.71K forks on GitHub appears to be more popular than Yeoman with 9.23K GitHub stars and 759 GitHub forks.
According to the StackShare community, Yeoman has a broader approval, being mentioned in 204 company stacks & 200 developers stacks; compared to Kong, which is listed in 50 company stacks and 13 developer stacks.
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 Yeoman
- Lightning-fast scaffolding121
- Automation83
- Great build process78
- Open source57
- Yo49
- Unit Testing8
Sign up to add or upvote prosMake informed product decisions
Cons of Kong
Cons of Yeoman
- Even harder to debug than Javascript1
Sign up to add or upvote consMake informed product decisions
What is Kong?
What is Yeoman?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Kong?
What companies use Yeoman?
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