Hystrix vs Kubernetes

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


+ 1

+ 1
Add tool

Hystrix vs Kubernetes: What are the differences?


Hystrix and Kubernetes are two popular technologies used in the field of software development and deployment. While both serve different purposes, they share some similarities but also have some key differences.

  1. Scalability and Fault Tolerance: Hystrix is a library that provides fault tolerance and latency tolerance for distributed systems. It helps in preventing cascading failures and provides fallback options when errors occur. On the other hand, Kubernetes is an open-source container orchestration platform that enables the management and scaling of containerized applications. It automates the deployment, scaling, and management of containers across multiple hosts, making it easy to achieve fault tolerance and scalability.

  2. Application Level vs Infrastructure Level: Hystrix operates at the application level, providing fault tolerance and resilience features to individual applications. It helps in handling failures and recovering from them gracefully within the application. Kubernetes, on the other hand, operates at the infrastructure level, managing the deployment and scaling of containerized applications across a cluster of machines. It provides a higher-level abstraction for managing and orchestrating applications, making it easier to automate various tasks.

  3. Granularity of Control: Hystrix offers a fine-grained control over the behavior of individual service calls within an application. It allows developers to define various parameters like timeouts, circuit-breaker thresholds, and concurrency limits at a per-service-call level. Kubernetes, on the other hand, works at a higher level of abstraction and provides control over the entire application or microservice. It allows developers to define scaling rules, resource limits, and deployment strategies for the entire application or set of services.

  4. Monitoring and Metrics: Hystrix provides detailed monitoring and metrics for the individual service calls and helps in analyzing the performance and behavior of the services. It offers insights into various aspects like request volumes, error rates, circuit breaker state, and latency distributions. Kubernetes, on the other hand, provides monitoring and metrics at the infrastructure level. It offers insights into resource utilization, application metrics, and health status of the containers and nodes.

  5. Flexibility and Portability: Hystrix is a library that can be used in various programming languages and frameworks. It can be integrated with existing applications without major changes to the codebase. Kubernetes, on the other hand, is a platform that can be used with any container runtime and supports multiple programming languages. It provides a flexible and portable environment for deploying and managing applications.

  6. Scope of Management: Hystrix is focused on the management of resilience and fault tolerance within an individual application or service. It provides features like circuit breakers, fallbacks, and timeouts for making the application more resilient to failures. Kubernetes, on the other hand, is a platform that manages the entire lifecycle of applications. It handles tasks like deployment, scaling, rolling updates, and self-healing of applications.

In summary, Hystrix and Kubernetes are different in terms of their focus, scope, and level of abstraction. Hystrix provides application-level fault tolerance and resilience features, while Kubernetes offers infrastructure-level container orchestration and management capabilities.

Decisions about Hystrix and Kubernetes
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.2M 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Hystrix
Pros of Kubernetes
  • 2
    Cirkit breaker
  • 164
    Leading docker container management solution
  • 128
    Simple and powerful
  • 106
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 25
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
  • 8
  • 6
  • 5
    No cloud platform lock-in
  • 5
    Promotes modern/good infrascture practice
  • 5
    Open, powerful, stable
  • 5
  • 4
  • 4
    Quick cloud setup
  • 3
    Cloud Agnostic
  • 3
    Captain of Container Ship
  • 3
    A self healing environment with rich metadata
  • 3
    Runs on azure
  • 3
    Backed by Red Hat
  • 3
    Custom and extensibility
  • 2
  • 2
  • 2
    Everything of CaaS
  • 2
  • 2
    Easy setup
  • 2

Sign up to add or upvote prosMake informed product decisions

Cons of Hystrix
Cons of Kubernetes
    Be the first to leave a con
    • 16
      Steep learning curve
    • 15
      Poor workflow for development
    • 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

    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 StackShare EnterpriseLearn 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

    Dec 8 2020 at 5:50PM


    May 21 2020 at 12:02AM

    Rancher Labs

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

    Rancher Labs

    What are some alternatives to Hystrix and Kubernetes?
    Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM.
    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 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.
    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.
    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
    See all alternatives