Fabric vs Kubernetes

Overview

Fabric

Stacks494

Followers307

Votes75

GitHub Stars15.3K

Forks2.0K

Kubernetes

Stacks61.2K

Followers52.8K

Votes685

Fabric vs Kubernetes: What are the differences?

Markdown is a lightweight markup language with plain-text formatting syntax. It is often used to format readme files, for writing messages in online discussion forums, and to create rich text using a plain text editor.

Scalability: One key difference between Fabric and Kubernetes is in their scalability approach. Fabric allows for fine-grained control over the network resources, making it more suitable for smaller, more specific requirements. On the other hand, Kubernetes is designed for massive scalability and can efficiently manage large clusters of nodes and containers, making it more suitable for large-scale applications.
Configuration Management: Fabric focuses more on the network implementation and doesn't have built-in features for managing configuration across nodes. Kubernetes, on the other hand, provides robust configuration management capabilities through ConfigMaps and Secrets, making it easier to manage and maintain the configuration of applications running in the cluster.
Resource Orchestration: Kubernetes excels in resource orchestration, ensuring that containers are allocated resources efficiently and effectively. It manages resource utilization, scaling, load balancing, and more, providing a comprehensive orchestration solution. Fabric, while capable of deploying and managing networks efficiently, lacks the advanced resource orchestration features that Kubernetes offers.
Support for Stateful Applications: Kubernetes provides robust support for stateful applications through features like StatefulSets and persistent volumes. These features enable developers to run stateful workloads such as databases reliably in Kubernetes clusters. Fabric, being more network-focused, doesn't offer these specific features for managing stateful applications in the same comprehensive way.
Community and Ecosystem: Kubernetes has a large and active community, with extensive documentation, tutorials, and plugins available to support users. The strong ecosystem around Kubernetes includes tools for monitoring, logging, networking, and more. Fabric, while actively developing, may not have the same breadth and depth of community support and ecosystem as Kubernetes.
Architecture: The architectural differences between Fabric and Kubernetes are significant. Fabric is a permissioned blockchain network, designed specifically for enterprise use cases, with an emphasis on privacy, scalability, and modular design. Kubernetes, on the other hand, is a container orchestration platform that focuses on automating the deployment, scaling, and management of containerized applications. The architectural paradigms of Fabric and Kubernetes are fundamentally different, reflecting their distinct purposes and target domains.

In Summary, Fabric and Kubernetes differ in scalability, configuration management, resource orchestration, support for stateful applications, community and ecosystem, and architectural paradigms, making each platform suitable for distinct use cases within the realm of network and container management.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Fabric, Kubernetes

Simon

Senior Fullstack Developer at QUANTUSflow Software GmbH

Apr 27, 2020

Decidedon

GitHub

GitHub Pages

Markdown

Our whole DevOps stack consists of the following tools:

@{GitHub}|tool:27| (incl. @{GitHub Pages}|tool:683|/@{Markdown}|tool:1147| for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
Respectively @{Git}|tool:1046| as revision control system
@{SourceTree}|tool:1599| as @{Git}|tool:1046| GUI
@{Visual Studio Code}|tool:4202| as IDE
@{CircleCI}|tool:190| for continuous integration (automatize development process)
@{Prettier}|tool:7035| / @{TSLint}|tool:5561| / @{ESLint}|tool:3337| as code linter
@{SonarQube}|tool:2638| as quality gate
@{Docker}|tool:586| as container management (incl. @{Docker Compose}|tool:3136| for multi-container application management)
@{VirtualBox}|tool:774| for operating system simulation tests
@{Kubernetes}|tool:1885| as cluster management for docker containers
@{Heroku}|tool:133| for deploying in test environments
@{nginx}|tool:1052| as web server (preferably used as facade server in production environment)
@{SSLMate}|tool:2752| (using @{OpenSSL}|tool:3091|) for certificate management
@{Amazon EC2}|tool:18| (incl. @{Amazon S3}|tool:25|) for deploying in stage (production-like) and production environments
@{PostgreSQL}|tool:1028| as preferred database system
@{Redis}|tool:1031| 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.

12.8M views12.8M

Comments

Anis

Founder at Odix

Nov 7, 2020

Review

I recommend this : -Spring reactive for back end : the fact it's reactive (async) it consumes half of the resources that a sync platform needs (so less CPU -> less money). -Angular : Web Front end ; it's gives you the possibility to use PWA which is a cheap replacement for a mobile app (but more less popular). -Docker images. -Kubernetes to orchestrate all the containers. -I Use Jenkins / blueocean, ansible for my CI/CD (with Github of course) -AWS of course : u can run a K8S cluster there, make it multi AZ (availability zones) to be highly available, use a load balancer and an auto scaler and ur good to go. -You can store data by taking any managed DB or u can deploy ur own (cheap but risky).

You pay less money, but u need some technical 2 - 3 guys to make that done.

Good luck

115k views115k

Comments

Detailed Comparison

Fabric	Kubernetes
Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution.	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.
Lets you execute arbitrary Python functions via the command line;Library of subroutines (built on top of a lower-level library) to make executing shell commands over SSH easy and Pythonic	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
Statistics
GitHub Stars 15.3K	GitHub Stars -
GitHub Forks 2.0K	GitHub Forks -
Stacks 494	Stacks 61.2K
Followers 307	Followers 52.8K
Votes 75	Votes 685
Pros & Cons
Pros 23 Python 21 Simple 5 Low learning curve, from bash script to Python power 5 Installation feedback for Twitter App Cards 3 Agentless	Pros 166 Leading docker container management solution 130 Simple and powerful 108 Open source 76 Backed by google 58 The right abstractions Cons 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
Integrations
No integrations available	Vagrant Docker Rackspace Cloud Servers Microsoft Azure Google Compute Engine Ansible Google Kubernetes Engine

What are some alternatives to Fabric, Kubernetes?

Ansible

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

Rancher

Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.

Docker Compose

With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.

Chef

Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.

Terraform

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Docker Swarm

Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.

Tutum

Tutum lets developers easily manage and run lightweight, portable, self-sufficient containers from any application. AWS-like control, Heroku-like ease. The same container that a developer builds and tests on a laptop can run at scale in Tutum.

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Puppet Labs

Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Salt

Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.

Related Comparisons

Fabric vs Kubernetes: What are the differences?

Scalability: One key difference between Fabric and Kubernetes is in their scalability approach. Fabric allows for fine-grained control over the network resources, making it more suitable for smaller, more specific requirements. On the other hand, Kubernetes is designed for massive scalability and can efficiently manage large clusters of nodes and containers, making it more suitable for large-scale applications.
Configuration Management: Fabric focuses more on the network implementation and doesn't have built-in features for managing configuration across nodes. Kubernetes, on the other hand, provides robust configuration management capabilities through ConfigMaps and Secrets, making it easier to manage and maintain the configuration of applications running in the cluster.
Resource Orchestration: Kubernetes excels in resource orchestration, ensuring that containers are allocated resources efficiently and effectively. It manages resource utilization, scaling, load balancing, and more, providing a comprehensive orchestration solution. Fabric, while capable of deploying and managing networks efficiently, lacks the advanced resource orchestration features that Kubernetes offers.
Support for Stateful Applications: Kubernetes provides robust support for stateful applications through features like StatefulSets and persistent volumes. These features enable developers to run stateful workloads such as databases reliably in Kubernetes clusters. Fabric, being more network-focused, doesn't offer these specific features for managing stateful applications in the same comprehensive way.
Community and Ecosystem: Kubernetes has a large and active community, with extensive documentation, tutorials, and plugins available to support users. The strong ecosystem around Kubernetes includes tools for monitoring, logging, networking, and more. Fabric, while actively developing, may not have the same breadth and depth of community support and ecosystem as Kubernetes.
Architecture: The architectural differences between Fabric and Kubernetes are significant. Fabric is a permissioned blockchain network, designed specifically for enterprise use cases, with an emphasis on privacy, scalability, and modular design. Kubernetes, on the other hand, is a container orchestration platform that focuses on automating the deployment, scaling, and management of containerized applications. The architectural paradigms of Fabric and Kubernetes are fundamentally different, reflecting their distinct purposes and target domains.

Fabric vs Kubernetes

Overview