Kong vs Ocelot: 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 Ocelot? A modern fast, scalable API gateway built on ASP.NET core. It is aimed at people using .NET running a micro services / service oriented architecture that need a unified point of entry into their system. However it will work with anything that speaks HTTP and run on any platform that ASP.NET Core supports. It manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service.
Kong and Ocelot can be primarily classified as "Microservices" tools.
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, Ocelot provides the following key features:
- Request Aggregation
- Service Discovery with Consul & Eureka
Kong and Ocelot are both open source tools. Kong with 23.4K GitHub stars and 2.91K forks on GitHub appears to be more popular than Ocelot with 4.12K GitHub stars and 903 GitHub forks.
Sign up to add or upvote prosMake informed product decisions
What is Kong?
What is Ocelot?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions