Need advice about which tool to choose?Ask the StackShare community!

Micro

34
51
+ 1
2
Ocelot

60
254
+ 1
0
Add tool

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:

  • API
  • CLI
  • Web UI

On the other hand, Ocelot provides the following key features:

  • Routing
  • 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.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Micro
Pros of Ocelot
  • 1
    Great flexibility
  • 1
    Nice tooling
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    What is Micro?

    Micro is a framework for cloud native development. Micro addresses the key requirements for building cloud native services. It leverages the microservices architecture pattern and provides a set of services which act as the building blocks

    What is Ocelot?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Micro and Ocelot as a desired skillset
    CBRE
    United Kingdom of Great Britain and Northern Ireland England London
    CBRE
    United Kingdom of Great Britain and Northern Ireland England London
    CBRE
    United States of America Texas Houston
    CBRE
    United Kingdom of Great Britain and Northern Ireland England Gloucester
    What companies use Micro?
    What companies use Ocelot?
    See which teams inside your own company are using Micro or Ocelot.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Micro?
    What tools integrate with Ocelot?
      No integrations found
      What are some alternatives to Micro and Ocelot?
      Istio
      Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.
      Kong
      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.
      Zuul
      It is the front door for all requests from devices and websites to the backend of the Netflix streaming application. As an edge service application, It is built to enable dynamic routing, monitoring, resiliency, and security. Routing is an integral part of a microservice architecture.
      Jersey
      It is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. It provides it’s own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development.
      linkerd
      linkerd is an out-of-process network stack for microservices. It functions as a transparent RPC proxy, handling everything needed to make inter-service RPC safe and sane--including load-balancing, service discovery, instrumentation, and routing.
      See all alternatives