Hystrix vs Kubernetes

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

Hystrix

133
132
+ 1
2
Kubernetes

40.3K
34.3K
+ 1
628
Add tool

Hystrix vs Kubernetes: What are the differences?

Developers describe Hystrix as "Latency and fault tolerance library". Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable. On the other hand, Kubernetes is detailed as "Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops". 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.

Hystrix belongs to "Fault Tolerance Tools" category of the tech stack, while Kubernetes can be primarily classified under "Container Tools".

Some of the features offered by Hystrix are:

  • Latency and Fault Tolerance
  • Realtime Operations
  • Concurrency

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

  • Lightweight, simple and accessible
  • Built for a multi-cloud world, public, private or hybrid
  • Highly modular, designed so that all of its components are easily swappable

Hystrix and Kubernetes are both open source tools. Kubernetes with 55.1K GitHub stars and 19.1K forks on GitHub appears to be more popular than Hystrix with 17.7K GitHub stars and 3.63K GitHub forks.

Google, Slack, and Shopify are some of the popular companies that use Kubernetes, whereas Hystrix is used by Intuit, Zalando, and Bodybuilding.com. Kubernetes has a broader approval, being mentioned in 1046 company stacks & 1096 developers stacks; compared to Hystrix, which is listed in 12 company stacks and 8 developer stacks.

Decisions about Hystrix and Kubernetes
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.5M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Hystrix
Pros of Kubernetes
  • 2
    Cirkit breaker
  • 159
    Leading docker container management solution
  • 124
    Simple and powerful
  • 101
    Open source
  • 75
    Backed by google
  • 56
    The right abstractions
  • 24
    Scale services
  • 18
    Replication controller
  • 9
    Permission managment
  • 7
    Supports autoscaling
  • 7
    Simple
  • 6
    Cheap
  • 4
    Reliable
  • 4
    No cloud platform lock-in
  • 4
    Self-healing
  • 3
    Quick cloud setup
  • 3
    Open, powerful, stable
  • 3
    Scalable
  • 3
    Promotes modern/good infrascture practice
  • 2
    Cloud Agnostic
  • 2
    Runs on azure
  • 2
    Backed by Red Hat
  • 2
    Custom and extensibility
  • 2
    Captain of Container Ship
  • 2
    A self healing environment with rich metadata
  • 1
    Golang
  • 1
    Easy setup
  • 1
    Everything of CaaS
  • 1
    Sfg
  • 1
    Expandable
  • 1
    Gke

Sign up to add or upvote prosMake informed product decisions

Cons of Hystrix
Cons of Kubernetes
    Be the first to leave a con
    • 13
      Poor workflow for development
    • 11
      Steep learning curve
    • 5
      Orchestrates only infrastructure
    • 2
      High resource requirements for on-prem clusters

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Hystrix?

    Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.

    What is 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.

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

    What companies use Hystrix?
    What companies use Kubernetes?
    See which teams inside your own company are using Hystrix or Kubernetes.
    Sign up for Private StackShareLearn More

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

    What tools integrate with Hystrix?
    What tools integrate with Kubernetes?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Kubernetesetcd+2
    2
    1033
    Dec 8 2020 at 5:50PM

    DigitalOcean

    GitHubMySQLMongoDB+11
    2
    2003
    PythonDockerKubernetes+7
    3
    725
    May 21 2020 at 12:02AM

    Rancher Labs

    KubernetesAmazon EC2Grafana+12
    3
    1271
    Apr 16 2020 at 5:34AM

    Rancher Labs

    KubernetesRancher+2
    2
    810
    PythonDockerKubernetes+14
    11
    2127
    What are some alternatives to Hystrix and Kubernetes?
    Akka
    Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM.
    Envoy
    Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
    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.
    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.
    Polly
    It is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner.
    See all alternatives