Alternatives to Fabric logo

Alternatives to Fabric

Ansible, Azure Service Fabric, Kubernetes, Liquid, and Forge are the most popular alternatives and competitors to Fabric.
413
299
+ 1
75

What is Fabric and what are its top alternatives?

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.
Fabric is a tool in the Server Configuration and Automation category of a tech stack.
Fabric is an open source tool with 13.9K GitHub stars and 1.9K GitHub forks. Here’s a link to Fabric's open source repository on GitHub

Top Alternatives to Fabric

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

  • Azure Service Fabric
    Azure Service Fabric

    Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices. Service Fabric addresses the significant challenges in developing and managing cloud apps. ...

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

  • Liquid
    Liquid

    It is an open-source template language written in Ruby. It is the backbone of Shopify themes and is used to load dynamic content on storefronts. It is safe, customer facing template language for flexible web apps. ...

  • Forge
    Forge

    Fastest possible way to host lighting-fast static websites for small businesses, web startups, and app developers. ...

  • Material
    Material

    Express your creativity with Material, an animation and graphics framework for Google's Material Design and Apple's Flat UI in Swift. ...

  • Fiber
    Fiber

    Fiber UI Kit is the perfect starting place for your next project. Each element has been designed to work independently or as one seamless flow. It’s a full-fledged prototype with customizable components. ...

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

Fabric alternatives & related posts

Ansible logo

Ansible

17.2K
14.1K
1.3K
Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine
17.2K
14.1K
+ 1
1.3K
PROS OF ANSIBLE
  • 283
    Agentless
  • 209
    Great configuration
  • 198
    Simple
  • 176
    Powerful
  • 154
    Easy to learn
  • 68
    Flexible
  • 55
    Doesn't get in the way of getting s--- done
  • 35
    Makes sense
  • 30
    Super efficient and flexible
  • 27
    Powerful
  • 11
    Dynamic Inventory
  • 9
    Backed by Red Hat
  • 7
    Works with AWS
  • 6
    Cloud Oriented
  • 6
    Easy to maintain
  • 4
    Multi language
  • 4
    Because SSH
  • 4
    Vagrant provisioner
  • 4
    Easy
  • 4
    Simple
  • 4
    Procedural or declarative, or both
  • 4
    Simple and powerful
  • 3
    Consistency
  • 2
    Merge hash to get final configuration similar to hiera
  • 2
    Debugging is simple
  • 2
    Fast as hell
  • 2
    Well-documented
  • 2
    Masterless
  • 1
    Manage any OS
  • 1
    Certified Content
  • 1
    Work on windows, but difficult to manage
CONS OF ANSIBLE
  • 8
    Dangerous
  • 5
    Hard to install
  • 3
    Doesn't Run on Windows
  • 3
    Bloated
  • 3
    Backward compatibility
  • 2
    No immutable infrastructure

related Ansible posts

Tymoteusz Paul
Devops guy at X20X Development LTD · | 23 upvotes · 5.7M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Sebastian Gębski

Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.

See more
Azure Service Fabric logo

Azure Service Fabric

90
272
25
Distributed systems platform that simplifies build, package, deploy, and management of scalable microservices apps
90
272
+ 1
25
PROS OF AZURE SERVICE FABRIC
  • 5
    Intelligent, fast, reliable
  • 3
    Open source
  • 3
    Superior programming models
  • 3
    More reliable than Kubernetes
  • 3
    Runs most of Azure core services
  • 3
    Reliability
  • 2
    Quickest recovery and healing in the world
  • 1
    Deploy anywhere
  • 1
    Is data storage technology
  • 1
    Battle hardened in Azure > 10 Years
CONS OF AZURE SERVICE FABRIC
    Be the first to leave a con

    related Azure Service Fabric posts

    Kubernetes logo

    Kubernetes

    52.2K
    45.7K
    641
    Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
    52.2K
    45.7K
    + 1
    641
    PROS OF KUBERNETES
    • 162
      Leading docker container management solution
    • 127
      Simple and powerful
    • 104
      Open source
    • 75
      Backed by google
    • 57
      The right abstractions
    • 24
      Scale services
    • 19
      Replication controller
    • 10
      Permission managment
    • 7
      Cheap
    • 7
      Simple
    • 7
      Supports autoscaling
    • 4
      No cloud platform lock-in
    • 4
      Self-healing
    • 4
      Reliable
    • 3
      Quick cloud setup
    • 3
      Open, powerful, stable
    • 3
      Scalable
    • 3
      Promotes modern/good infrascture practice
    • 2
      Custom and extensibility
    • 2
      Cloud Agnostic
    • 2
      Captain of Container Ship
    • 2
      A self healing environment with rich metadata
    • 2
      Runs on azure
    • 2
      Backed by Red Hat
    • 1
      Golang
    • 1
      Expandable
    • 1
      Sfg
    • 1
      Everything of CaaS
    • 1
      Easy setup
    • 1
      Gke
    CONS OF KUBERNETES
    • 15
      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

    related Kubernetes posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 42 upvotes · 6M 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
    Liquid logo

    Liquid

    119
    111
    0
    Open-source template language written in Ruby
    119
    111
    + 1
    0
    PROS OF LIQUID
      Be the first to leave a pro
      CONS OF LIQUID
        Be the first to leave a con

        related Liquid posts

        Forge logo

        Forge

        7
        19
        1
        Static web hosting made simple
        7
        19
        + 1
        1
        PROS OF FORGE
        • 1
          Fgfgf
        CONS OF FORGE
        • 1
          Its just bad

        related Forge posts

        Material logo

        Material

        85
        79
        3
        A Graphics Framework for Material Design in Swift
        85
        79
        + 1
        3
        PROS OF MATERIAL
        • 1
          Good Documentation
        • 1
          Samples included
        • 1
          IOS benefits
        CONS OF MATERIAL
          Be the first to leave a con

          related Material posts

          Fiber logo

          Fiber

          31
          42
          0
          An interactive UI Kit by Framer.
          31
          42
          + 1
          0
          PROS OF FIBER
            Be the first to leave a pro
            CONS OF FIBER
              Be the first to leave a con

              related Fiber posts

              Terraform logo

              Terraform

              15.3K
              12.4K
              341
              Describe your complete infrastructure as code and build resources across providers
              15.3K
              12.4K
              + 1
              341
              PROS OF TERRAFORM
              • 119
                Infrastructure as code
              • 73
                Declarative syntax
              • 44
                Planning
              • 28
                Simple
              • 24
                Parallelism
              • 8
                Cloud agnostic
              • 8
                Well-documented
              • 6
                Immutable infrastructure
              • 6
                It's like coding your infrastructure in simple English
              • 5
                Platform agnostic
              • 4
                Portability
              • 4
                Extendable
              • 4
                Automation
              • 4
                Automates infrastructure deployments
              • 2
                Scales to hundreds of hosts
              • 2
                Lightweight
              CONS OF TERRAFORM
              • 1
                1244124
              • 1
                Doesn't have full support to GKE

              related Terraform posts

              Emanuel Evans
              Senior Architect at Rainforest QA · | 20 upvotes · 1.2M views

              We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).

              We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .

              Read the blog post to go more in depth.

              See more
              Praveen Mooli
              Engineering Manager at Taylor and Francis · | 18 upvotes · 2.8M views

              We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

              To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

              To build #Webapps we decided to use Angular 2 with RxJS

              #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

              See more