Micro vs Ocelot: What are the differences?
Micro: A microservice toolkit. Micro provides the core requirements for building and managing microservices. It consists of a set of libraries and tools which are primarily geared towards development in the programming language Go, however looks to solve for other languages via HTTP using a Sidecar; 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.
Micro and Ocelot can be primarily classified as "Microservices" tools.
Some of the features offered by Micro are:
- Web UI
On the other hand, Ocelot provides the following key features:
- Request Aggregation
- Service Discovery with Consul & Eureka
Micro and Ocelot are both open source tools. Micro with 6.72K GitHub stars and 561 forks on GitHub appears to be more popular than Ocelot with 4.12K GitHub stars and 903 GitHub forks.