Alternatives to Monit logo

Alternatives to Monit

Nagios, Zabbix, Prometheus, Supervisord, and Munin are the most popular alternatives and competitors to Monit.
130
54
+ 1
0

What is Monit and what are its top alternatives?

Monit is a popular open-source tool used for proactive monitoring and automatic management of Unix systems. It can monitor various aspects of a system such as CPU usage, memory usage, file systems, and processes. Monit can also perform automatic actions like restarting a service or sending alerts based on predefined conditions. However, one of its limitations is the lack of complex monitoring capabilities compared to enterprise-grade monitoring tools.

  1. Prometheus: Prometheus is a powerful open-source monitoring and alerting toolkit designed for reliability, scalability, and extensibility. It scrapes metrics from monitored targets, stores them in a time series database, and allows querying of these metrics to trigger alerts based on predefined conditions. One key feature of Prometheus is its robust querying language, PromQL, which enables complex monitoring scenarios. However, setting up Prometheus can be complex compared to Monit.
  2. Nagios: Nagios is a widely-used open-source monitoring tool that provides comprehensive monitoring and alerting solutions. It can monitor network services, host resources, and environmental factors. Nagios supports both agent-based and agentless monitoring, making it versatile for various monitoring requirements. However, Nagios can be challenging to configure and maintain compared to Monit.
  3. Zabbix: Zabbix is an enterprise-class open-source monitoring solution known for its scalability and flexibility. It can monitor networks, servers, virtual machines, and cloud services. Zabbix offers advanced features like distributed monitoring, auto-discovery, and real-time monitoring of tens of thousands of devices. One drawback of Zabbix is its steep learning curve compared to Monit.
  4. Icinga: Icinga is an open-source monitoring tool that forked from Nagios and enhanced its features. It offers a user-friendly web interface, advanced reporting capabilities, and support for monitoring across multiple locations. Icinga supports plugins for extending functionality and integration with various third-party tools. However, Icinga can be resource-intensive compared to Monit.
  5. Grafana: Grafana is a popular open-source visualization tool commonly used with monitoring systems like Prometheus. It provides a rich set of visualizations, dashboards, and plugins to create custom monitoring solutions. Grafana supports data from various sources and offers features like alerting, annotations, and sharing dashboards. One limitation of Grafana is its focus on visualization rather than system monitoring compared to Monit.
  6. Datadog: Datadog is a SaaS-based monitoring and analytics platform that provides comprehensive monitoring solutions for cloud-scale applications. It offers integrations with various technologies, real-time monitoring, and advanced analytics for performance optimization. Datadog's pricing model based on the number of monitored hosts can be a drawback compared to Monit.
  7. Sysdig: Sysdig is a container monitoring solution that provides real-time visibility into containerized environments. It offers features like container security, performance monitoring, and troubleshooting capabilities. Sysdig's deep integration with container orchestration platforms like Kubernetes sets it apart from traditional monitoring tools like Monit.
  8. Netdata: Netdata is an open-source real-time monitoring and troubleshooting tool for systems and applications. It offers a highly interactive web interface, custom dashboards, and detailed metrics for various system components. Netdata's lightweight footprint and ease of installation make it a popular choice for real-time monitoring compared to Monit.
  9. Opsgenie: Opsgenie is an incident management platform that provides alerting, on-call scheduling, and incident response automation. It integrates with various monitoring tools to streamline alerting and resolution processes. Opsgenie's robust notification capabilities and automation features make it a valuable addition to monitoring setups alongside tools like Monit.
  10. Checkmk: Checkmk is an open-source monitoring tool that offers comprehensive monitoring solutions for networks, servers, applications, and cloud infrastructure. It provides a centralized monitoring platform with features like auto-discovery, performance graphs, and customizable alerts. Checkmk's user-friendly interface and scalability make it a strong alternative to Monit for monitoring complex environments.

Top Alternatives to Monit

  • Nagios
    Nagios

    Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License. ...

  • Zabbix
    Zabbix

    Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics. ...

  • Prometheus
    Prometheus

    Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true. ...

  • Supervisord
    Supervisord

    It allows its users to monitor and control a number of processes on UNIX-like operating systems. It shares some of the same goals of programs like launchd, daemontools, and runit. it is meant to be used to control processes related to a project or a customer, and is meant to start like any other program at boot time. ...

  • Munin
    Munin

    Munin is a networked resource monitoring tool that can help analyze resource trends and "what just happened to kill our performance?" problems. It is designed to be very plug and play. A default installation provides a lot of graphs with almost no work. ...

  • JavaScript
    JavaScript

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

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

Monit alternatives & related posts

Nagios logo

Nagios

826
1.1K
102
Complete monitoring and alerting for servers, switches, applications, and services
826
1.1K
+ 1
102
PROS OF NAGIOS
  • 53
    It just works
  • 28
    The standard
  • 12
    Customizable
  • 8
    The Most flexible monitoring system
  • 1
    Huge stack of free checks/plugins to choose from
CONS OF NAGIOS
    Be the first to leave a con

    related Nagios posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 15 upvotes · 4.5M views

    Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

    By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node’s disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

    To ensure the scalability of Uber’s metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

    https://eng.uber.com/m3/

    (GitHub : https://github.com/m3db/m3)

    See more
    Shared insights
    on
    PrometheusPrometheusNagiosNagios

    I am new to DevOps and looking for training in DevOps. Some institutes are offering Nagios while some Prometheus in their syllabus. Please suggest which one is being used in the industry and which one should I learn.

    See more
    Zabbix logo

    Zabbix

    670
    970
    66
    Track, record, alert and visualize performance and availability of IT resources
    670
    970
    + 1
    66
    PROS OF ZABBIX
    • 21
      Free
    • 9
      Alerts
    • 5
      Service/node/network discovery
    • 5
      Templates
    • 4
      Base metrics from the box
    • 3
      Multi-dashboards
    • 3
      SMS/Email/Messenger alerts
    • 2
      Grafana plugin available
    • 2
      Supports Graphs ans screens
    • 2
      Support proxies (for monitoring remote branches)
    • 1
      Perform website checking (response time, loading, ...)
    • 1
      API available for creating own apps
    • 1
      Templates free available (Zabbix Share)
    • 1
      Works with multiple databases
    • 1
      Advanced integrations
    • 1
      Supports multiple protocols/agents
    • 1
      Complete Logs Report
    • 1
      Open source
    • 1
      Supports large variety of Operating Systems
    • 1
      Supports JMX (Java, Tomcat, Jboss, ...)
    CONS OF ZABBIX
    • 5
      The UI is in PHP
    • 2
      Puppet module is sluggish

    related Zabbix posts

    Shared insights
    on
    DatadogDatadogZabbixZabbixCentreonCentreon

    My team is divided on using Centreon or Zabbix for enterprise monitoring and alert automation. Can someone let us know which one is better? There is one more tool called Datadog that we are using for cloud assets. Of course, Datadog presents us with huge bills. So we want to have a comparative study. Suggestions and advice are welcome. Thanks!

    See more
    Shared insights
    on
    ZabbixZabbixCheckmkCheckmk

    I am looking for an easy to set up and use monitoring solution for my servers and network infrastructure. What are the main differences between Checkmk and Zabbix? What would you recommend and why?

    See more
    Prometheus logo

    Prometheus

    4.2K
    3.8K
    239
    An open-source service monitoring system and time series database, developed by SoundCloud
    4.2K
    3.8K
    + 1
    239
    PROS OF PROMETHEUS
    • 47
      Powerful easy to use monitoring
    • 38
      Flexible query language
    • 32
      Dimensional data model
    • 27
      Alerts
    • 23
      Active and responsive community
    • 22
      Extensive integrations
    • 19
      Easy to setup
    • 12
      Beautiful Model and Query language
    • 7
      Easy to extend
    • 6
      Nice
    • 3
      Written in Go
    • 2
      Good for experimentation
    • 1
      Easy for monitoring
    CONS OF PROMETHEUS
    • 12
      Just for metrics
    • 6
      Bad UI
    • 6
      Needs monitoring to access metrics endpoints
    • 4
      Not easy to configure and use
    • 3
      Supports only active agents
    • 2
      Written in Go
    • 2
      TLS is quite difficult to understand
    • 2
      Requires multiple applications and tools
    • 1
      Single point of failure

    related Prometheus posts

    Matt Menzenski
    Senior Software Engineering Manager at PayIt · | 16 upvotes · 995.6K views

    Grafana and Prometheus together, running on Kubernetes , is a powerful combination. These tools are cloud-native and offer a large community and easy integrations. At PayIt we're using exporting Java application metrics using a Dropwizard metrics exporter, and our Node.js services now use the prom-client npm library to serve metrics.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 15 upvotes · 4.5M views

    Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

    By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node’s disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

    To ensure the scalability of Uber’s metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

    https://eng.uber.com/m3/

    (GitHub : https://github.com/m3db/m3)

    See more
    Supervisord logo

    Supervisord

    116
    110
    0
    A client/server system that allows its users to monitor and control a number of processes
    116
    110
    + 1
    0
    PROS OF SUPERVISORD
      Be the first to leave a pro
      CONS OF SUPERVISORD
        Be the first to leave a con

        related Supervisord posts

        Hello, I'm using Supervisord for separate process manager/consumer with RabbitMQ and Symfony but it's not working properly, it disconnects after a couple of hours.. and for a workaround, I'm using a restart job on Jenkins (as in the linked issue in GitHub) but tbh I would like to have a clean stack.. if anyone knows a better alternative than supervisord it will be awesome..

        Many thanks!

        See more
        Munin logo

        Munin

        72
        95
        10
        PnP networked resource monitoring tool that can help to answer the what just happened to kill our performance
        72
        95
        + 1
        10
        PROS OF MUNIN
        • 3
          Good defaults
        • 2
          Extremely fast to install
        • 2
          Alerts can trigger any command line program
        • 2
          Adheres to traditional Linux standards
        • 1
          Easy to write custom plugins
        CONS OF MUNIN
          Be the first to leave a con

          related Munin posts

          JavaScript logo

          JavaScript

          350.9K
          267.1K
          8.1K
          Lightweight, interpreted, object-oriented language with first-class functions
          350.9K
          267.1K
          + 1
          8.1K
          PROS OF JAVASCRIPT
          • 1.7K
            Can be used on frontend/backend
          • 1.5K
            It's everywhere
          • 1.2K
            Lots of great frameworks
          • 896
            Fast
          • 745
            Light weight
          • 425
            Flexible
          • 392
            You can't get a device today that doesn't run js
          • 286
            Non-blocking i/o
          • 236
            Ubiquitousness
          • 191
            Expressive
          • 55
            Extended functionality to web pages
          • 49
            Relatively easy language
          • 46
            Executed on the client side
          • 30
            Relatively fast to the end user
          • 25
            Pure Javascript
          • 21
            Functional programming
          • 15
            Async
          • 13
            Full-stack
          • 12
            Setup is easy
          • 12
            Its everywhere
          • 12
            Future Language of The Web
          • 11
            JavaScript is the New PHP
          • 11
            Because I love functions
          • 10
            Like it or not, JS is part of the web standard
          • 9
            Expansive community
          • 9
            Everyone use it
          • 9
            Can be used in backend, frontend and DB
          • 9
            Easy
          • 8
            Easy to hire developers
          • 8
            No need to use PHP
          • 8
            For the good parts
          • 8
            Can be used both as frontend and backend as well
          • 8
            Powerful
          • 8
            Most Popular Language in the World
          • 7
            Popularized Class-Less Architecture & Lambdas
          • 7
            It's fun
          • 7
            Nice
          • 7
            Versitile
          • 7
            Hard not to use
          • 7
            Its fun and fast
          • 7
            Agile, packages simple to use
          • 7
            Supports lambdas and closures
          • 7
            Love-hate relationship
          • 7
            Photoshop has 3 JS runtimes built in
          • 7
            Evolution of C
          • 6
            1.6K Can be used on frontend/backend
          • 6
            Client side JS uses the visitors CPU to save Server Res
          • 6
            It let's me use Babel & Typescript
          • 6
            Easy to make something
          • 6
            Can be used on frontend/backend/Mobile/create PRO Ui
          • 5
            Promise relationship
          • 5
            Stockholm Syndrome
          • 5
            Function expressions are useful for callbacks
          • 5
            Scope manipulation
          • 5
            Everywhere
          • 5
            Client processing
          • 5
            Clojurescript
          • 5
            What to add
          • 4
            Because it is so simple and lightweight
          • 4
            Only Programming language on browser
          • 1
            Test2
          • 1
            Easy to learn
          • 1
            Easy to understand
          • 1
            Not the best
          • 1
            Hard to learn
          • 1
            Subskill #4
          • 1
            Test
          • 0
            Hard 彤
          CONS OF JAVASCRIPT
          • 22
            A constant moving target, too much churn
          • 20
            Horribly inconsistent
          • 15
            Javascript is the New PHP
          • 9
            No ability to monitor memory utilitization
          • 8
            Shows Zero output in case of ANY error
          • 7
            Thinks strange results are better than errors
          • 6
            Can be ugly
          • 3
            No GitHub
          • 2
            Slow

          related JavaScript posts

          Zach Holman

          Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

          But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

          But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

          Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

          See more
          Conor Myhrvold
          Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.1M 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
          Git logo

          Git

          289.8K
          174.2K
          6.6K
          Fast, scalable, distributed revision control system
          289.8K
          174.2K
          + 1
          6.6K
          PROS OF GIT
          • 1.4K
            Distributed version control system
          • 1.1K
            Efficient branching and merging
          • 959
            Fast
          • 845
            Open source
          • 726
            Better than svn
          • 368
            Great command-line application
          • 306
            Simple
          • 291
            Free
          • 232
            Easy to use
          • 222
            Does not require server
          • 27
            Distributed
          • 22
            Small & Fast
          • 18
            Feature based workflow
          • 15
            Staging Area
          • 13
            Most wide-spread VSC
          • 11
            Role-based codelines
          • 11
            Disposable Experimentation
          • 7
            Frictionless Context Switching
          • 6
            Data Assurance
          • 5
            Efficient
          • 4
            Just awesome
          • 3
            Github integration
          • 3
            Easy branching and merging
          • 2
            Compatible
          • 2
            Flexible
          • 2
            Possible to lose history and commits
          • 1
            Rebase supported natively; reflog; access to plumbing
          • 1
            Light
          • 1
            Team Integration
          • 1
            Fast, scalable, distributed revision control system
          • 1
            Easy
          • 1
            Flexible, easy, Safe, and fast
          • 1
            CLI is great, but the GUI tools are awesome
          • 1
            It's what you do
          • 0
            Phinx
          CONS OF GIT
          • 16
            Hard to learn
          • 11
            Inconsistent command line interface
          • 9
            Easy to lose uncommitted work
          • 7
            Worst documentation ever possibly made
          • 5
            Awful merge handling
          • 3
            Unexistent preventive security flows
          • 3
            Rebase hell
          • 2
            When --force is disabled, cannot rebase
          • 2
            Ironically even die-hard supporters screw up badly
          • 1
            Doesn't scale for big data

          related Git posts

          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
          Tymoteusz Paul
          Devops guy at X20X Development LTD · | 23 upvotes · 8.3M 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
          GitHub logo

          GitHub

          279.5K
          243.8K
          10.3K
          Powerful collaboration, review, and code management for open source and private development projects
          279.5K
          243.8K
          + 1
          10.3K
          PROS OF GITHUB
          • 1.8K
            Open source friendly
          • 1.5K
            Easy source control
          • 1.3K
            Nice UI
          • 1.1K
            Great for team collaboration
          • 867
            Easy setup
          • 504
            Issue tracker
          • 486
            Great community
          • 482
            Remote team collaboration
          • 451
            Great way to share
          • 442
            Pull request and features planning
          • 147
            Just works
          • 132
            Integrated in many tools
          • 121
            Free Public Repos
          • 116
            Github Gists
          • 112
            Github pages
          • 83
            Easy to find repos
          • 62
            Open source
          • 60
            It's free
          • 60
            Easy to find projects
          • 56
            Network effect
          • 49
            Extensive API
          • 43
            Organizations
          • 42
            Branching
          • 34
            Developer Profiles
          • 32
            Git Powered Wikis
          • 30
            Great for collaboration
          • 24
            It's fun
          • 23
            Clean interface and good integrations
          • 22
            Community SDK involvement
          • 20
            Learn from others source code
          • 16
            Because: Git
          • 14
            It integrates directly with Azure
          • 10
            Newsfeed
          • 10
            Standard in Open Source collab
          • 8
            Fast
          • 8
            It integrates directly with Hipchat
          • 8
            Beautiful user experience
          • 7
            Easy to discover new code libraries
          • 6
            Smooth integration
          • 6
            Cloud SCM
          • 6
            Nice API
          • 6
            Graphs
          • 6
            Integrations
          • 6
            It's awesome
          • 5
            Quick Onboarding
          • 5
            Remarkable uptime
          • 5
            CI Integration
          • 5
            Hands down best online Git service available
          • 5
            Reliable
          • 4
            Free HTML hosting
          • 4
            Version Control
          • 4
            Simple but powerful
          • 4
            Unlimited Public Repos at no cost
          • 4
            Security options
          • 4
            Loved by developers
          • 4
            Uses GIT
          • 4
            Easy to use and collaborate with others
          • 3
            IAM
          • 3
            Nice to use
          • 3
            Ci
          • 3
            Easy deployment via SSH
          • 2
            Good tools support
          • 2
            Leads the copycats
          • 2
            Free private repos
          • 2
            Free HTML hostings
          • 2
            Easy and efficient maintainance of the projects
          • 2
            Beautiful
          • 2
            Never dethroned
          • 2
            IAM integration
          • 2
            Very Easy to Use
          • 2
            Easy to use
          • 2
            All in one development service
          • 2
            Self Hosted
          • 2
            Issues tracker
          • 2
            Easy source control and everything is backed up
          • 1
            Profound
          CONS OF GITHUB
          • 53
            Owned by micrcosoft
          • 37
            Expensive for lone developers that want private repos
          • 15
            Relatively slow product/feature release cadence
          • 10
            API scoping could be better
          • 8
            Only 3 collaborators for private repos
          • 3
            Limited featureset for issue management
          • 2
            GitHub Packages does not support SNAPSHOT versions
          • 2
            Does not have a graph for showing history like git lens
          • 1
            No multilingual interface
          • 1
            Takes a long time to commit
          • 1
            Expensive

          related GitHub posts

          Johnny Bell

          I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

          I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

          I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

          Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

          Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

          With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

          If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

          See more
          Russel Werner
          Lead Engineer at StackShare · | 32 upvotes · 2.2M views

          StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

          Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

          #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

          See more