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

fabric8

37
113
+ 1
1
Kubernetes

60K
51.8K
+ 1
681
Add tool

Kubernetes vs fabric8: What are the differences?

Introduction

Kubernetes and fabric8 are both popular platforms used for container orchestration and management. However, they have some key differences that set them apart from each other.

  1. Cluster Management: One major difference between Kubernetes and fabric8 is their approach to cluster management. Kubernetes provides a highly scalable and robust cluster management solution, with features like automated deployment, scaling, and load balancing. On the other hand, fabric8 focuses more on providing a simplified and lightweight cluster management solution, suitable for smaller deployments or development environments.

  2. Support for multiple container runtimes: Kubernetes supports multiple container runtimes, including Docker and CRI-O. This allows users to choose the runtime that best suits their needs. In contrast, fabric8 primarily uses the Docker container runtime and has limited support for other runtimes. This can be a limitation for users who prefer non-Docker runtimes.

  3. Integration with other tools and services: Kubernetes has a rich ecosystem of tools and services built around it, making it easy to integrate with various monitoring, logging, and CI/CD tools. On the other hand, fabric8 offers a more opinionated stack with built-in tools for monitoring, logging, and continuous delivery, making it easier to get started quickly without the need for external integrations.

  4. Flexibility and Customization: Kubernetes provides a high degree of flexibility and customization options, allowing users to fine-tune their cluster configurations and define complex deployment scenarios. Fabric8, on the other hand, focuses on providing a curated experience with pre-configured deployments and opinionated defaults, which can make it easier for beginners but may limit customization options for advanced users.

  5. Community and Support: Kubernetes has a large and active community of contributors, with extensive documentation, tutorials, and support available. This makes it easier for users to find help and resources when facing issues or trying to implement specific features. Fabric8, while also having a community, may have a smaller user base and might have limited documentation and support resources available.

  6. Maturity and Adoption: Kubernetes has gained widespread adoption across various industries and has proven its stability and scalability in large-scale production deployments. Fabric8, while also being a mature platform, may not have the same level of adoption and proven track record in enterprise-scale deployments.

In summary, Kubernetes provides a robust and highly scalable cluster management solution with extensive community support and a wide range of integrations, while fabric8 offers a more lightweight and opinionated stack with built-in tools and simplified management for smaller deployments or development environments.

Decisions about fabric8 and Kubernetes
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.6M 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
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of fabric8
Pros of Kubernetes
  • 1
    Easy to build and automate integration testing
  • 166
    Leading docker container management solution
  • 129
    Simple and powerful
  • 107
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 25
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
    Simple
  • 8
    Cheap
  • 6
    Self-healing
  • 5
    Open, powerful, stable
  • 5
    Reliable
  • 5
    No cloud platform lock-in
  • 5
    Promotes modern/good infrascture practice
  • 4
    Scalable
  • 4
    Quick cloud setup
  • 3
    Custom and extensibility
  • 3
    Captain of Container Ship
  • 3
    Cloud Agnostic
  • 3
    Backed by Red Hat
  • 3
    Runs on azure
  • 3
    A self healing environment with rich metadata
  • 2
    Everything of CaaS
  • 2
    Gke
  • 2
    Golang
  • 2
    Easy setup
  • 2
    Expandable
  • 2
    Sfg

Sign up to add or upvote prosMake informed product decisions

Cons of fabric8
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 fabric8?

    fabric8 makes it easy to create microservices, build, test and deploy them via Continuous Delivery pipelines then run and manage them with Continuous Improvement and ChatOps.

    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 fabric8?
    What companies use Kubernetes?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

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

    What tools integrate with fabric8?
    What tools integrate with Kubernetes?

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

    Blog Posts

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

    DigitalOcean

    GitHubMySQLPostgreSQL+11
    2
    2449
    PythonDockerKubernetes+7
    3
    1160
    May 21 2020 at 12:02AM

    Rancher Labs

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

    Rancher Labs

    KubernetesRancher+2
    2
    976
    What are some alternatives to fabric8 and Kubernetes?
    Deis
    Deis can deploy any application or service that can run inside a Docker container. In order to be scaled horizontally, applications must follow Heroku's 12-factor methodology and store state in external backing services.
    Red Hat OpenShift
    OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
    Spinnaker
    Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
    Fuse
    It is a set of user experience development tools that unify design, prototyping and implementation of high quality, native apps for iOS and Android.
    Jib
    Jib builds Docker and OCI images for your Java applications and is available as plugins for Maven and Gradle.
    See all alternatives