Alternatives to Apache HTTP Server logo

Alternatives to Apache HTTP Server

Apache Tomcat, NGINX, JBoss, Jetty, and XAMPP are the most popular alternatives and competitors to Apache HTTP Server.
64.2K
22.4K
+ 1
1.4K

What is Apache HTTP Server and what are its top alternatives?

Apache HTTP Server is a widely-used open-source web server known for its flexibility, reliability, and extensive support for modules. It supports a variety of operating systems and programming languages, making it a popular choice for hosting websites and applications. However, Apache HTTP Server can be complex to configure and may require additional performance tuning for high traffic websites.

  1. Nginx: Nginx is a lightweight, high-performance web server known for its low resource usage and ability to handle a large number of concurrent connections. It also excels at serving static content quickly, making it a popular choice for websites with high traffic. However, it may not support as many modules and configurations out of the box compared to Apache HTTP Server.

  2. LiteSpeed Web Server: LiteSpeed Web Server is a high-performance commercial web server known for its speed and efficiency. It offers a range of features, including built-in caching and optimization tools, making it a suitable choice for websites that require fast loading times. However, the commercial license may be a limitation for some users compared to the free Apache HTTP Server.

  3. Caddy: Caddy is a modern, open-source web server that emphasizes ease of use and automatic HTTPS encryption. It comes with a simple configuration language and built-in features like Let's Encrypt integration, making it a user-friendly alternative to Apache HTTP Server. However, it may not offer the same level of customization and flexibility as Apache HTTP Server.

  4. Microsoft IIS: Internet Information Services (IIS) is a web server created by Microsoft for Windows servers. It offers a range of features and integration with other Microsoft products, making it a popular choice for organizations that use Windows environments. However, it may not be as widely supported across different operating systems compared to Apache HTTP Server.

  5. OpenLiteSpeed: OpenLiteSpeed is the open-source version of LiteSpeed Web Server, offering similar performance and features at no cost. It is designed to be lightweight and efficient while providing fast and secure web hosting capabilities. However, it may lack some advanced features present in the commercial version and may not have as extensive support compared to Apache HTTP Server.

  6. Caddy Web Server: Caddy is a powerful, enterprise-ready web server with automatic HTTPS by default. It has a simple configuration process and is suitable for showcasing static sites. However, it may require a commercial license for certain advanced features, unlike the free Apache HTTP Server.

  7. Cherokee: Cherokee is a high-performance, lightweight web server known for its ease of use and powerful features. It offers a web-based interface for configuration and management, making it user-friendly for beginners. However, it may not have as extensive support and community resources as Apache HTTP Server.

  8. HAProxy: HAProxy is a widely-used open-source software load balancer and proxy server known for its performance and reliability. It excels at handling a large number of concurrent connections and distributing traffic efficiently, making it a popular choice for high traffic websites. However, it may not offer the same level of web server functionality as Apache HTTP Server.

  9. Lighttpd: Lighttpd is a lightweight web server known for its speed and low resource consumption. It is designed to be efficient and easy to configure, making it suitable for hosting websites with high traffic or limited server resources. However, it may not have as many modules and features as Apache HTTP Server.

  10. Tengine: Tengine is a web server based on Nginx with added features and improvements for performance and stability. It offers enhanced load-balancing capabilities and support for dynamic content caching, making it a popular choice for high traffic websites. However, it may not have as extensive support and documentation as Apache HTTP Server.

Top Alternatives to Apache HTTP Server

  • Apache Tomcat
    Apache Tomcat

    Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. ...

  • NGINX
    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • JBoss
    JBoss

    An application platform for hosting your apps that provides an innovative modular, cloud-ready architecture, powerful management and automation, and world class developer productivity. ...

  • Jetty
    Jetty

    Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty. ...

  • XAMPP
    XAMPP

    It consists mainly of the Apache HTTP Server, MariaDB database, and interpreters for scripts written in the PHP and Perl programming languages. ...

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

Apache HTTP Server alternatives & related posts

Apache Tomcat logo

Apache Tomcat

16.3K
12.2K
201
An open source software implementation of the Java Servlet and JavaServer Pages technologies
16.3K
12.2K
+ 1
201
PROS OF APACHE TOMCAT
  • 79
    Easy
  • 72
    Java
  • 49
    Popular
  • 1
    Spring web
CONS OF APACHE TOMCAT
  • 2
    Blocking - each http request block a thread
  • 1
    Easy to set up

related Apache Tomcat posts

Остап Комплікевич

I need some advice to choose an engine for generation web pages from the Spring Boot app. Which technology is the best solution today? 1) JSP + JSTL 2) Apache FreeMarker 3) Thymeleaf Or you can suggest even other perspective tools. I am using Spring Boot, Spring Web, Spring Data, Spring Security, PostgreSQL, Apache Tomcat in my project. I have already tried to generate pages using jsp, jstl, and it went well. However, I had huge problems via carrying already created static pages, to jsp format, because of syntax. Thanks.

See more
Tomas Zeman
product manager at Broadcom · | 3 upvotes · 18.1K views
Shared insights
on
PlayPlayApache TomcatApache Tomcat
at

I use Play as the best Java framewrk for web development. It is easy to use and I was able to learn it quickly. Before I was using Apache Tomcat , but I would never go back. Play is preselecting for you popular and usefull libraries, you can use templating with Twirl, JPA, Injections and much more.

See more
NGINX logo

NGINX

112.3K
60.1K
5.5K
A high performance free open source web server powering busiest sites on the Internet.
112.3K
60.1K
+ 1
5.5K
PROS OF NGINX
  • 1.4K
    High-performance http server
  • 893
    Performance
  • 730
    Easy to configure
  • 607
    Open source
  • 530
    Load balancer
  • 288
    Free
  • 288
    Scalability
  • 225
    Web server
  • 175
    Simplicity
  • 136
    Easy setup
  • 30
    Content caching
  • 21
    Web Accelerator
  • 15
    Capability
  • 14
    Fast
  • 12
    High-latency
  • 12
    Predictability
  • 8
    Reverse Proxy
  • 7
    The best of them
  • 7
    Supports http/2
  • 5
    Great Community
  • 5
    Lots of Modules
  • 5
    Enterprise version
  • 4
    High perfomance proxy server
  • 3
    Reversy Proxy
  • 3
    Streaming media delivery
  • 3
    Streaming media
  • 3
    Embedded Lua scripting
  • 2
    GRPC-Web
  • 2
    Blash
  • 2
    Lightweight
  • 2
    Fast and easy to set up
  • 2
    Slim
  • 2
    saltstack
  • 1
    Virtual hosting
  • 1
    Narrow focus. Easy to configure. Fast
  • 1
    Along with Redis Cache its the Most superior
  • 1
    Ingress controller
CONS OF NGINX
  • 10
    Advanced features require subscription

related NGINX 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
John-Daniel Trask
Co-founder & CEO at Raygun · | 19 upvotes · 255.8K views

We chose AWS because, at the time, it was really the only cloud provider to choose from.

We tend to use their basic building blocks (EC2, ELB, Amazon S3, Amazon RDS) rather than vendor specific components like databases and queuing. We deliberately decided to do this to ensure we could provide multi-cloud support or potentially move to another cloud provider if the offering was better for our customers.

We’ve utilized c3.large nodes for both the Node.js deployment and then for the .NET Core deployment. Both sit as backends behind an nginx instance and are managed using scaling groups in Amazon EC2 sitting behind a standard AWS Elastic Load Balancing (ELB).

While we’re satisfied with AWS, we do review our decision each year and have looked at Azure and Google Cloud offerings.

#CloudHosting #WebServers #CloudStorage #LoadBalancerReverseProxy

See more
JBoss logo

JBoss

329
250
0
An open source Java EE-based application server
329
250
+ 1
0
PROS OF JBOSS
    Be the first to leave a pro
    CONS OF JBOSS
      Be the first to leave a con

      related JBoss posts

      Jetty logo

      Jetty

      465
      308
      43
      An open-source project providing an HTTP server, HTTP client, and javax.servlet container
      465
      308
      + 1
      43
      PROS OF JETTY
      • 14
        Lightweight
      • 10
        Very fast
      • 9
        Embeddable
      • 5
        Scalable
      • 5
        Very thin
      CONS OF JETTY
      • 0
        Student

      related Jetty posts

      XAMPP logo

      XAMPP

      132
      269
      6
      A free and open-source cross-platform web server solution stack package
      132
      269
      + 1
      6
      PROS OF XAMPP
      • 6
        Easy set up and installation of files
      CONS OF XAMPP
        Be the first to leave a con

        related XAMPP posts

        Shared insights
        on
        XAMPPXAMPPNGINXNGINX

        Hello everyone! I'm working on a web application, it will be deployed in a private local network so I need to choose which server I will use, so I need to know which one between NGINX and XAMPP, ps: I used to work with XAMPP since everything is integrated

        See more
        Helfried Plenk
        Senior Partner at IBS IT-DL GmbH · | 1 upvote · 673.5K views
        Shared insights
        on
        MAMPMAMPXAMPPXAMPPJoomla!Joomla!

        installing a local Joomla! 3.9 website for testing - I already downloaded an installed XAMPP - when now reading some other docs I found mentioned MAMP ... have I to change?

        See more
        JavaScript logo

        JavaScript

        350.9K
        267.2K
        8.1K
        Lightweight, interpreted, object-oriented language with first-class functions
        350.9K
        267.2K
        + 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.9K
        174.2K
        6.6K
        Fast, scalable, distributed revision control system
        289.9K
        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.6K
        243.8K
        10.3K
        Powerful collaboration, review, and code management for open source and private development projects
        279.6K
        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
          Standard in Open Source collab
        • 10
          Newsfeed
        • 8
          It integrates directly with Hipchat
        • 8
          Fast
        • 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
          Reliable
        • 5
          Remarkable uptime
        • 5
          CI Integration
        • 5
          Hands down best online Git service available
        • 4
          Uses GIT
        • 4
          Version Control
        • 4
          Simple but powerful
        • 4
          Unlimited Public Repos at no cost
        • 4
          Free HTML hosting
        • 4
          Security options
        • 4
          Loved by developers
        • 4
          Easy to use and collaborate with others
        • 3
          Ci
        • 3
          IAM
        • 3
          Nice to use
        • 3
          Easy deployment via SSH
        • 2
          Easy to use
        • 2
          Leads the copycats
        • 2
          All in one development service
        • 2
          Free private repos
        • 2
          Free HTML hostings
        • 2
          Easy and efficient maintainance of the projects
        • 2
          Beautiful
        • 2
          Easy source control and everything is backed up
        • 2
          IAM integration
        • 2
          Very Easy to Use
        • 2
          Good tools support
        • 2
          Issues tracker
        • 2
          Never dethroned
        • 2
          Self Hosted
        • 1
          Dasf
        • 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