Alternatives to Jelastic logo

Alternatives to Jelastic

Google App Engine, Amazon EBS, DigitalOcean, Kubernetes, and Heroku are the most popular alternatives and competitors to Jelastic.
38
60
+ 1
74

What is Jelastic and what are its top alternatives?

Jelastic is a multifunctional Platform as a Service (PaaS) that offers cloud hosting solutions for Java, PHP, Ruby, Node.js, Python, and Docker. It provides scalability, high availability, and automation in managing applications on the cloud. Key features include automatic vertical scaling, automatic clustering, multi-cloud support, and Docker containers support. However, some limitations of Jelastic may include limited support for certain programming languages and frameworks, complex pricing structure, and potential performance issues.

  1. Heroku: Heroku is a cloud platform that lets developers build, deliver, monitor, and scale applications. Key features include support for multiple programming languages, easy integration with various tools and services, and seamless deployment process. Pros of Heroku include ease of use, scalability, and robust ecosystem of add-ons. Cons may include limited configuration options for certain applications and pricing based on resource usage.

  2. AWS Elastic Beanstalk: AWS Elastic Beanstalk is a platform that allows for easy deployment and management of applications on AWS. Key features include support for various programming languages, automatic scaling, and monitoring tools. Pros of Elastic Beanstalk include seamless integration with other AWS services, high scalability, and reliable infrastructure. Cons may include complex pricing structure and potential resource management challenges.

  3. Google App Engine: Google App Engine is a fully managed serverless platform that supports multiple programming languages. Key features include auto-scaling, built-in security features, and seamless integration with other Google Cloud services. Pros of Google App Engine include high availability, robust infrastructure, and strong compliance standards. Cons may include limited flexibility in configuration and potential vendor lock-in.

  4. Microsoft Azure App Service: Azure App Service is a platform that allows for building, deploying, and scaling web applications. Key features include support for multiple programming languages, auto-scaling, and integration with other Azure services. Pros of Azure App Service include high availability, seamless deployment process, and strong security features. Cons may include potential performance issues and complex pricing.

  5. DigitalOcean App Platform: DigitalOcean App Platform is a platform that simplifies the deployment and scaling of web applications. Key features include automatic scaling, HTTPS encryption, and continuous deployment. Pros of DigitalOcean App Platform include ease of use, affordable pricing, and integration with other DigitalOcean services. Cons may include limited support for databases and potential resource limitations.

  6. OpenShift: OpenShift is a Kubernetes-based platform that offers containerized application development and deployment. Key features include support for various programming languages, auto-scaling, and built-in monitoring tools. Pros of OpenShift include flexibility in deployment options, strong community support, and robust security features. Cons may include potential complexity in configuration and management.

  7. IBM Cloud Foundry: IBM Cloud Foundry is a platform that enables developers to build, deploy, and scale applications with ease. Key features include support for multiple programming languages, auto-scaling, and integration with various IBM services. Pros of IBM Cloud Foundry include high availability, seamless deployment process, and strong security features. Cons may include potential vendor lock-in and complex pricing.

  8. Oracle Cloud Platform: Oracle Cloud Platform offers a comprehensive set of cloud services for building, deploying, and managing applications. Key features include support for various programming languages, auto-scaling, and robust security features. Pros of Oracle Cloud Platform include reliability, integration with Oracle databases, and strong compliance standards. Cons may include limited documentation and potential complexity in setting up.

  9. Pivotal Cloud Foundry: Pivotal Cloud Foundry is a platform that simplifies the deployment and management of cloud-native applications. Key features include support for multiple programming languages, auto-scaling, and containerization. Pros of Pivotal Cloud Foundry include flexibility in deployment options, seamless integration with CI/CD tools, and strong security features. Cons may include potential learning curve and pricing based on resource usage.

  10. Red Hat OpenShift: Red Hat OpenShift is a Kubernetes-based platform that enables automated container provisioning, scaling, and management. Key features include support for various programming languages, auto-scaling, and built-in monitoring tools. Pros of Red Hat OpenShift include strong community support, robust security features, and flexibility in deployment options. Cons may include potential complexity in configuration and potential performance issues.

Top Alternatives to Jelastic

  • Google App Engine
    Google App Engine

    Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. ...

  • Amazon EBS
    Amazon EBS

    Amazon EBS volumes are network-attached, and persist independently from the life of an instance. Amazon EBS provides highly available, highly reliable, predictable storage volumes that can be attached to a running Amazon EC2 instance and exposed as a device within the instance. Amazon EBS is particularly suited for applications that require a database, file system, or access to raw block level storage. ...

  • DigitalOcean
    DigitalOcean

    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel. ...

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

  • Heroku
    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • Cloud Foundry
    Cloud Foundry

    Cloud Foundry is an open platform as a service (PaaS) that provides a choice of clouds, developer frameworks, and application services. Cloud Foundry makes it faster and easier to build, test, deploy, and scale applications. ...

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

  • Apache HTTP Server
    Apache HTTP Server

    The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet. ...

Jelastic alternatives & related posts

Google App Engine logo

Google App Engine

10.3K
611
Build web applications on the same scalable systems that power Google applications
10.3K
611
PROS OF GOOGLE APP ENGINE
  • 145
    Easy to deploy
  • 106
    Auto scaling
  • 80
    Good free plan
  • 62
    Easy management
  • 56
    Scalability
  • 35
    Low cost
  • 32
    Comprehensive set of features
  • 28
    All services in one place
  • 22
    Simple scaling
  • 19
    Quick and reliable cloud servers
  • 6
    Granular Billing
  • 5
    Easy to develop and unit test
  • 5
    Monitoring gives comprehensive set of key indicators
  • 3
    Really easy to quickly bring up a full stack
  • 3
    Create APIs quickly with cloud endpoints
  • 2
    No Ops
  • 2
    Mostly up
CONS OF GOOGLE APP ENGINE
    Be the first to leave a con

    related Google App Engine posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 12 upvotes · 453.2K views

    So, the shift from Amazon EC2 to Google App Engine and generally #AWS to #GCP was a long decision and in the end, it's one that we've taken with eyes open and that we reserve the right to modify at any time. And to be clear, we continue to do a lot of stuff with AWS. But, by default, the content of the decision was, for our consumer-facing products, we're going to use GCP first. And if there's some reason why we don't think that's going to work out great, then we'll happily use AWS. In practice, that hasn't really happened. We've been able to meet almost 100% of our needs in GCP.

    So it's basically mostly Google Kubernetes Engine , we're mostly running stuff on Kubernetes right now.

    #AWStoGCPmigration #cloudmigration #migration

    See more
    Aliadoc Team

    In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

    For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

    For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

    We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

    Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

    See more
    Amazon EBS logo

    Amazon EBS

    667
    82
    Block level storage volumes for use with Amazon EC2 instances.
    667
    82
    PROS OF AMAZON EBS
    • 36
      Point-in-time snapshots
    • 27
      Data reliability
    • 19
      Configurable i/o performance
    CONS OF AMAZON EBS
      Be the first to leave a con

      related Amazon EBS posts

      I could spin up an Amazon EC2 instance and install PostgreSQL myself, review latest configuration best practices, sort Amazon EBS storage for data, set up a snapshot process etc.

      Alternatively I could use Amazon RDS, Amazon RDS for PostgreSQL or Heroku Postgres and have most of that work handled for me, by a team of world experts...

      See more

      We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.

      We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.

      We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.

      You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?

      See more
      DigitalOcean logo

      DigitalOcean

      18.1K
      2.6K
      Deploy an SSD cloud server in less than 55 seconds with a dedicated IP and root access.
      18.1K
      2.6K
      PROS OF DIGITALOCEAN
      • 560
        Great value for money
      • 364
        Simple dashboard
      • 362
        Good pricing
      • 300
        Ssds
      • 250
        Nice ui
      • 191
        Easy configuration
      • 156
        Great documentation
      • 138
        Ssh access
      • 135
        Great community
      • 24
        Ubuntu
      • 13
        Docker
      • 12
        IPv6 support
      • 10
        Private networking
      • 8
        99.99% uptime SLA
      • 7
        Simple API
      • 7
        Great tutorials
      • 6
        55 Second Provisioning
      • 5
        One Click Applications
      • 4
        Dokku
      • 4
        LAMP
      • 4
        Debian
      • 4
        CoreOS
      • 4
        Node.js
      • 3
        1Gb/sec Servers
      • 3
        Word Press
      • 3
        Mean
      • 3
        LEMP
      • 3
        Simple Control Panel
      • 3
        Ghost
      • 2
        Runs CoreOS
      • 2
        Quick and no nonsense service
      • 2
        Django
      • 2
        Good Tutorials
      • 2
        Speed
      • 2
        Ruby on Rails
      • 2
        GitLab
      • 2
        Hex Core machines with dedicated ECC Ram and RAID SSD s
      • 1
        CentOS
      • 1
        Spaces
      • 1
        KVM Virtualization
      • 1
        Amazing Hardware
      • 1
        Transfer Globally
      • 1
        Fedora
      • 1
        FreeBSD
      • 1
        Drupal
      • 1
        FreeBSD Amp
      • 1
        Magento
      • 1
        ownCloud
      • 1
        RedMine
      • 1
        My go to server provider
      • 1
        Ease and simplicity
      • 1
        Nice
      • 1
        Find it superfitting with my requirements (SSD, ssh.
      • 1
        Easy Setup
      • 1
        Cheap
      • 1
        Static IP
      • 1
        It's the easiest to get started for small projects
      • 1
        Automatic Backup
      • 1
        Great support
      • 1
        Quick and easy to set up
      • 1
        Servers on demand - literally
      • 1
        Reliability
      • 0
        Variety of services
      • 0
        Managed Kubernetes
      CONS OF DIGITALOCEAN
      • 3
        No live support chat
      • 3
        Pricing

      related DigitalOcean posts

      Christopher Wray
      Web Developer at Soltech LLC · | 15 upvotes · 185.9K views

      This week, we finally released NurseryPeople.com. In the end, I chose to provision our server on DigitalOcean. So far, I am SO happy with that decision. Although setting everything up was a challenge, and I learned a lot, DigitalOceans blogs helped in so many ways. I was able to set up nginx and the Laravel web app pretty smoothly. I am also using Buddy for deploying changes made in git, which is super awesome. All I have to do in order to deploy is push my code to my private repo, and buddy transfers everything over to DigitalOcean. So far, we haven't had any downtime and DigitalOceans prices are quite fair for the power under the hood.

      See more

      Hello, I'm currently writing an e-commerce website with Laravel and Laravel Nova (as an admin panel). I want to start deploying the app and created a DigitalOcean account. After some searches about the deployment process, I saw that the setup via DigitalOcean (using Droplets) isn't very easy for beginners. Now I'm not sure how to deploy my app. I am in between Laravel Forge and DigitalOcean (?Apps Platform or Droplets?). I've read that Heroku and Laravel Vapor are a bit expensive. That's why I didn't consider them yet. I'd be happy to read your opinions on that topic!

      See more
      Kubernetes logo

      Kubernetes

      60.3K
      681
      Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
      60.3K
      681
      PROS OF KUBERNETES
      • 166
        Leading docker container management solution
      • 129
        Simple and powerful
      • 107
        Open source
      • 76
        Backed by google
      • 58
        The right abstractions
      • 25
        Scale services
      • 20
        Replication controller
      • 11
        Permission managment
      • 9
        Supports autoscaling
      • 8
        Simple
      • 8
        Cheap
      • 6
        Self-healing
      • 5
        Open, powerful, stable
      • 5
        Reliable
      • 5
        No cloud platform lock-in
      • 5
        Promotes modern/good infrascture practice
      • 4
        Scalable
      • 4
        Quick cloud setup
      • 3
        Custom and extensibility
      • 3
        Captain of Container Ship
      • 3
        Cloud Agnostic
      • 3
        Backed by Red Hat
      • 3
        Runs on azure
      • 3
        A self healing environment with rich metadata
      • 2
        Everything of CaaS
      • 2
        Gke
      • 2
        Golang
      • 2
        Easy setup
      • 2
        Expandable
      • 2
        Sfg
      CONS OF KUBERNETES
      • 16
        Steep learning curve
      • 15
        Poor workflow for development
      • 8
        Orchestrates only infrastructure
      • 4
        High resource requirements for on-prem clusters
      • 2
        Too heavy for simple systems
      • 1
        Additional vendor lock-in (Docker)
      • 1
        More moving parts to secure
      • 1
        Additional Technology Overhead

      related Kubernetes posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 13.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
      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
      Heroku logo

      Heroku

      25.6K
      3.2K
      Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
      25.6K
      3.2K
      PROS OF HEROKU
      • 703
        Easy deployment
      • 459
        Free for side projects
      • 374
        Huge time-saver
      • 348
        Simple scaling
      • 261
        Low devops skills required
      • 190
        Easy setup
      • 174
        Add-ons for almost everything
      • 153
        Beginner friendly
      • 150
        Better for startups
      • 133
        Low learning curve
      • 48
        Postgres hosting
      • 41
        Easy to add collaborators
      • 30
        Faster development
      • 24
        Awesome documentation
      • 19
        Simple rollback
      • 19
        Focus on product, not deployment
      • 15
        Natural companion for rails development
      • 15
        Easy integration
      • 12
        Great customer support
      • 8
        GitHub integration
      • 6
        Painless & well documented
      • 6
        No-ops
      • 4
        I love that they make it free to launch a side project
      • 4
        Free
      • 3
        Great UI
      • 3
        Just works
      • 2
        PostgreSQL forking and following
      • 2
        MySQL extension
      • 1
        Security
      • 1
        Able to host stuff good like Discord Bot
      • 0
        Sec
      CONS OF HEROKU
      • 27
        Super expensive
      • 9
        Not a whole lot of flexibility
      • 7
        No usable MySQL option
      • 7
        Storage
      • 5
        Low performance on free tier
      • 2
        24/7 support is $1,000 per month

      related Heroku posts

      Russel Werner
      Lead Engineer at StackShare · | 32 upvotes · 2.9M 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
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 12M 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
      Cloud Foundry logo

      Cloud Foundry

      189
      5
      Deploy and scale applications in seconds on your choice of private or public cloud
      189
      5
      PROS OF CLOUD FOUNDRY
      • 2
        Perfectly aligned with springboot
      • 1
        Free distributed tracing (zipkin)
      • 1
        Application health management
      • 1
        Free service discovery (Eureka)
      CONS OF CLOUD FOUNDRY
        Be the first to leave a con

        related Cloud Foundry posts

        NGINX logo

        NGINX

        113.8K
        5.5K
        A high performance free open source web server powering busiest sites on the Internet.
        113.8K
        5.5K
        PROS OF NGINX
        • 1.4K
          High-performance http server
        • 894
          Performance
        • 730
          Easy to configure
        • 607
          Open source
        • 530
          Load balancer
        • 289
          Free
        • 288
          Scalability
        • 226
          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
          Supports http/2
        • 7
          The best of them
        • 5
          Great Community
        • 5
          Lots of Modules
        • 5
          Enterprise version
        • 4
          High perfomance proxy server
        • 3
          Embedded Lua scripting
        • 3
          Streaming media delivery
        • 3
          Streaming media
        • 3
          Reversy Proxy
        • 2
          Blash
        • 2
          GRPC-Web
        • 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 · 12M 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 · 499.7K 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
        Apache HTTP Server logo

        Apache HTTP Server

        64.6K
        1.4K
        Open-source HTTP server for modern operating systems including UNIX and Windows
        64.6K
        1.4K
        PROS OF APACHE HTTP SERVER
        • 479
          Web server
        • 305
          Most widely-used web server
        • 217
          Virtual hosting
        • 148
          Fast
        • 138
          Ssl support
        • 44
          Since 1996
        • 28
          Asynchronous
        • 5
          Robust
        • 4
          Proven over many years
        • 2
          Mature
        • 2
          Perfomance
        • 1
          Perfect Support
        • 0
          Many available modules
        • 0
          Many available modules
        CONS OF APACHE HTTP SERVER
        • 4
          Hard to set up

        related Apache HTTP Server posts

        Nick Rockwell
        SVP, Engineering at Fastly · | 46 upvotes · 4.3M views

        When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

        So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

        React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

        Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

        See more
        Tim Abbott
        Shared insights
        on
        NGINXNGINXApache HTTP ServerApache HTTP Server
        at

        We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.

        Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.

        See more