Alternatives to Consul logo

Alternatives to Consul

etcd, Zookeeper, SkyDNS, Ambassador, and Kubernetes are the most popular alternatives and competitors to Consul.
1.1K
1.4K
+ 1
206

What is Consul and what are its top alternatives?

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.
Consul is a tool in the Open Source Service Discovery category of a tech stack.
Consul is an open source tool with 25.7K GitHub stars and 4.2K GitHub forks. Here’s a link to Consul's open source repository on GitHub

Top Alternatives to Consul

  • etcd
    etcd

    etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master. ...

  • Zookeeper
    Zookeeper

    A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. ...

  • SkyDNS
    SkyDNS

    SkyDNS is a distributed service for announcement and discovery of services. It leverages Raft for high-availability and consensus, and utilizes DNS queries to discover available services. This is done by leveraging SRV records in DNS, with special meaning given to subdomains, priorities and weights (more info here: http://blog.gopheracademy.com/skydns). ...

  • Ambassador
    Ambassador

    Map services to arbitrary URLs in a single, declarative YAML file. Configure routes with CORS support, circuit breakers, timeouts, and more. Replace your Kubernetes ingress controller. Route gRPC, WebSockets, or HTTP. ...

  • Kubernetes
    Kubernetes

    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions. ...

  • Redis
    Redis

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams. ...

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

  • Eureka
    Eureka

    Eureka is a REST (Representational State Transfer) based service that is primarily used in the AWS cloud for locating services for the purpose of load balancing and failover of middle-tier servers. ...

Consul alternatives & related posts

etcd logo

etcd

253
372
24
A distributed consistent key-value store for shared configuration and service discovery
253
372
+ 1
24
PROS OF ETCD
  • 11
    Service discovery
  • 6
    Fault tolerant key value store
  • 2
    Bundled with coreos
  • 2
    Secure
  • 1
    Privilege Access Management
  • 1
    Consol integration
  • 1
    Open Source
CONS OF ETCD
    Be the first to leave a con

    related etcd posts

    Zookeeper logo

    Zookeeper

    660
    921
    42
    Because coordinating distributed systems is a Zoo
    660
    921
    + 1
    42
    PROS OF ZOOKEEPER
    • 11
      High performance ,easy to generate node specific config
    • 8
      Kafka support
    • 8
      Java
    • 5
      Spring Boot Support
    • 3
      Supports extensive distributed IPC
    • 2
      Used in ClickHouse
    • 2
      Supports DC/OS
    • 1
      Embeddable In Java Service
    • 1
      Curator
    • 1
      Used in Hadoop
    CONS OF ZOOKEEPER
      Be the first to leave a con

      related Zookeeper posts

      SkyDNS logo

      SkyDNS

      8
      19
      2
      Distributed service for announcement and discovery of services
      8
      19
      + 1
      2
      PROS OF SKYDNS
      • 2
        Srv discovery for etcd
      CONS OF SKYDNS
        Be the first to leave a con

        related SkyDNS posts

        Ambassador logo

        Ambassador

        76
        178
        4
        Open source, Kubernetes-native API Gateway for Microservices built on Envoy
        76
        178
        + 1
        4
        PROS OF AMBASSADOR
        • 3
          Edge-proxy
        • 1
          Kubernetes friendly configuration
        CONS OF AMBASSADOR
          Be the first to leave a con

          related Ambassador posts

          Kubernetes logo

          Kubernetes

          49.6K
          43.1K
          639
          Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
          49.6K
          43.1K
          + 1
          639
          PROS OF KUBERNETES
          • 162
            Leading docker container management solution
          • 126
            Simple and powerful
          • 104
            Open source
          • 75
            Backed by google
          • 56
            The right abstractions
          • 24
            Scale services
          • 19
            Replication controller
          • 10
            Permission managment
          • 7
            Simple
          • 7
            Cheap
          • 7
            Supports autoscaling
          • 4
            Reliable
          • 4
            Self-healing
          • 4
            No cloud platform lock-in
          • 3
            Quick cloud setup
          • 3
            Open, powerful, stable
          • 3
            Scalable
          • 3
            Promotes modern/good infrascture practice
          • 2
            Captain of Container Ship
          • 2
            A self healing environment with rich metadata
          • 2
            Cloud Agnostic
          • 2
            Runs on azure
          • 2
            Backed by Red Hat
          • 2
            Custom and extensibility
          • 1
            Golang
          • 1
            Expandable
          • 1
            Gke
          • 1
            Easy setup
          • 1
            Sfg
          • 1
            Everything of CaaS
          CONS OF KUBERNETES
          • 15
            Poor workflow for development
          • 15
            Steep learning curve
          • 8
            Orchestrates only infrastructure
          • 4
            High resource requirements for on-prem clusters
          • 2
            Too heavy for simple systems
          • 1
            Additional vendor lock-in (Docker)
          • 1
            More moving parts to secure
          • 1
            Additional Technology Overhead

          related Kubernetes posts

          Conor Myhrvold
          Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.5M views

          How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

          Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

          Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

          https://eng.uber.com/distributed-tracing/

          (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

          Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

          See more
          Yshay Yaacobi

          Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

          Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

          After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

          See more
          Redis logo

          Redis

          52K
          39.5K
          3.9K
          Open source (BSD licensed), in-memory data structure store
          52K
          39.5K
          + 1
          3.9K
          PROS OF REDIS
          • 881
            Performance
          • 539
            Super fast
          • 510
            Ease of use
          • 441
            In-memory cache
          • 321
            Advanced key-value cache
          • 190
            Open source
          • 179
            Easy to deploy
          • 163
            Stable
          • 152
            Free
          • 120
            Fast
          • 40
            High-Performance
          • 39
            High Availability
          • 34
            Data Structures
          • 31
            Very Scalable
          • 23
            Replication
          • 20
            Pub/Sub
          • 20
            Great community
          • 17
            "NoSQL" key-value data store
          • 14
            Hashes
          • 12
            Sets
          • 10
            Sorted Sets
          • 9
            Lists
          • 8
            BSD licensed
          • 8
            NoSQL
          • 7
            Integrates super easy with Sidekiq for Rails background
          • 7
            Async replication
          • 7
            Bitmaps
          • 6
            Keys with a limited time-to-live
          • 6
            Open Source
          • 5
            Strings
          • 5
            Lua scripting
          • 4
            Hyperloglogs
          • 4
            Awesomeness for Free!
          • 3
            Transactions
          • 3
            Runs server side LUA
          • 3
            outstanding performance
          • 3
            Networked
          • 3
            LRU eviction of keys
          • 3
            Written in ANSI C
          • 3
            Feature Rich
          • 2
            Performance & ease of use
          • 2
            Data structure server
          • 1
            Simple
          • 1
            Channels concept
          • 1
            Scalable
          • 1
            Temporarily kept on disk
          • 1
            Dont save data if no subscribers are found
          • 1
            Automatic failover
          • 1
            Easy to use
          • 1
            Existing Laravel Integration
          • 1
            Object [key/value] size each 500 MB
          CONS OF REDIS
          • 14
            Cannot query objects directly
          • 2
            No secondary indexes for non-numeric data types
          • 1
            No WAL

          related Redis posts

          Robert Zuber

          We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

          As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

          When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

          See more

          I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

          We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

          Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

          We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

          Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

          See more
          Istio logo

          Istio

          3.3K
          1.3K
          45
          Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
          3.3K
          1.3K
          + 1
          45
          PROS OF ISTIO
          • 13
            Zero code for logging and monitoring
          • 8
            Service Mesh
          • 7
            Great flexibility
          • 4
            Powerful authorization mechanisms
          • 4
            Ingress controller
          • 3
            Easy integration with Kubernetes and Docker
          • 3
            Full Security
          • 3
            Resiliency
          CONS OF ISTIO
          • 15
            Performance

          related Istio posts

          Shared insights
          on
          IstioIstioDaprDapr

          At my company, we are trying to move away from a monolith into microservices led architecture. We are now stuck with a problem to establish a communication mechanism between microservices. Since, we are planning to use service meshes and something like Dapr/Istio, we are not sure on how to split services between the two. Service meshes offer Traffic Routing or Splitting whereas, Dapr can offer state management and service-service invocation. At the same time both of them provide mLTS, Metrics, Resiliency and tracing. How to choose who should offer what?

          See more
          Anas MOKDAD
          Shared insights
          on
          KongKongIstioIstio

          As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

          See more
          Eureka logo

          Eureka

          273
          696
          68
          AWS Service registry for resilient mid-tier load balancing and failover.
          273
          696
          + 1
          68
          PROS OF EUREKA
          • 21
            Easy setup and integration with spring-cloud
          • 9
            Web ui
          • 8
            Health checking
          • 7
            Monitoring
          • 7
            Circuit breaker
          • 6
            Service discovery
          • 6
            Netflix battle tested components
          • 4
            Open Source
          CONS OF EUREKA
            Be the first to leave a con

            related Eureka posts