Alternatives to Ratchet PHP logo

Alternatives to Ratchet PHP

ReactPHP, nginx, Apache HTTP Server, Microsoft IIS, and Apache Tomcat are the most popular alternatives and competitors to Ratchet PHP.
2
3
+ 1
0

What is Ratchet PHP and what are its top alternatives?

It is a loosely coupled PHP library providing developers with tools to create real time, bi-directional applications between clients and servers over WebSockets.
Ratchet PHP is a tool in the Web Servers category of a tech stack.
Ratchet PHP is an open source tool with 4.9K GitHub stars and 556 GitHub forks. Here’s a link to Ratchet PHP's open source repository on GitHub

Ratchet PHP alternatives & related posts

ReactPHP logo

ReactPHP

5
4
0
5
4
+ 1
0
Event-driven, non-blocking I/O with PHP
    Be the first to leave a pro
    ReactPHP logo
    ReactPHP
    VS
    Ratchet PHP logo
    Ratchet PHP
    nginx logo

    nginx

    54.7K
    13.1K
    5.4K
    54.7K
    13.1K
    + 1
    5.4K
    A high performance free open source web server powering busiest sites on the Internet.
    nginx logo
    nginx
    VS
    Ratchet PHP logo
    Ratchet PHP

    related nginx posts

    GitHub
    GitHub
    nginx
    nginx
    ESLint
    ESLint
    AVA
    AVA
    Semantic UI React
    Semantic UI React
    Redux
    Redux
    React
    React
    PostgreSQL
    PostgreSQL
    ExpressJS
    ExpressJS
    Node.js
    Node.js
    FeathersJS
    FeathersJS
    Heroku
    Heroku
    Amazon EC2
    Amazon EC2
    Kubernetes
    Kubernetes
    Jenkins
    Jenkins
    Docker Compose
    Docker Compose
    Docker
    Docker
    #Frontend
    #Stack
    #Backend
    #Containers
    #Containerized

    Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

    We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

    See more
    Chris McFadden
    Chris McFadden
    VP, Engineering at SparkPost · | 7 upvotes · 43.2K views
    atSparkPostSparkPost
    Lua
    Lua
    OpenResty
    OpenResty
    nginx
    nginx

    We use nginx and OpenResty as our API proxy running on EC2 for auth, caching, and some rate limiting for our dozens of microservices. Since OpenResty support embedded Lua we were able to write a custom access module that calls out to our authentication service with the resource, method, and access token. If that succeeds then critical account info is passed down to the underlying microservice. This proxy approach keeps all authentication and authorization in one place and provides a unified CX for our API users. Nginx is fast and cheap to run though we are always exploring alternatives that are also economical. What do you use?

    See more

    related Apache HTTP Server posts

    Marcel Kornegoor
    Marcel Kornegoor
    CTO at AT Computing · | 6 upvotes · 7.7K views
    Apache HTTP Server
    Apache HTTP Server
    nginx
    nginx

    nginx or Apache HTTP Server that's the question. The best choice depends on what it needs to serve. In general, Nginx performs better with static content, where Apache and Nginx score roughly the same when it comes to dynamic content. Since most webpages and web-applications use both static and dynamic content, a combination of both platforms may be the best solution.

    Since both webservers are easy to deploy and free to use, setting up a performance or feature comparison test is no big deal. This way you can see what solutions suits your application or content best. Don't forget to look at other aspects, like security, back-end compatibility (easy of integration) and manageability, as well.

    A reasonably good comparison between the two can be found in the link below.

    See more
    Tim Abbott
    Tim Abbott
    Founder at Zulip · | 4 upvotes · 32.3K views
    atZulipZulip
    Apache HTTP Server
    Apache HTTP Server
    nginx
    nginx

    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
    Apache Tomcat logo

    Apache Tomcat

    4.8K
    2.8K
    195
    4.8K
    2.8K
    + 1
    195
    An open source software implementation of the Java Servlet and JavaServer Pages technologies
    Apache Tomcat logo
    Apache Tomcat
    VS
    Ratchet PHP logo
    Ratchet PHP

    related Apache Tomcat posts

    MySQL
    MySQL
    Apache Tomcat
    Apache Tomcat
    Apache HTTP Server
    Apache HTTP Server
    JUnit
    JUnit
    Spring
    Spring
    Java
    Java

    Java Spring JUnit

    Apache HTTP Server Apache Tomcat

    MySQL

    See more
    OpenResty logo

    OpenResty

    2.1K
    73
    0
    2.1K
    73
    + 1
    0
    Turning Nginx into a Full-fledged Web App Server
      Be the first to leave a pro
      OpenResty logo
      OpenResty
      VS
      Ratchet PHP logo
      Ratchet PHP

      related OpenResty posts

      Chris McFadden
      Chris McFadden
      VP, Engineering at SparkPost · | 7 upvotes · 43.2K views
      atSparkPostSparkPost
      Lua
      Lua
      OpenResty
      OpenResty
      nginx
      nginx

      We use nginx and OpenResty as our API proxy running on EC2 for auth, caching, and some rate limiting for our dozens of microservices. Since OpenResty support embedded Lua we were able to write a custom access module that calls out to our authentication service with the resource, method, and access token. If that succeeds then critical account info is passed down to the underlying microservice. This proxy approach keeps all authentication and authorization in one place and provides a unified CX for our API users. Nginx is fast and cheap to run though we are always exploring alternatives that are also economical. What do you use?

      See more
      Go
      Go
      Lua
      Lua
      OpenResty
      OpenResty
      nginx
      nginx
      Logstash
      Logstash
      Prometheus
      Prometheus

      At Kong while building an internal tool, we struggled to route metrics to Prometheus and logs to Logstash without incurring too much latency in our metrics collection.

      We replaced nginx with OpenResty on the edge of our tool which allowed us to use the lua-nginx-module to run Lua code that captures metrics and records telemetry data during every request’s log phase. Our code then pushes the metrics to a local aggregator process (written in Go) which in turn exposes them in Prometheus Exposition Format for consumption by Prometheus. This solution reduced the number of components we needed to maintain and is fast thanks to NGINX and LuaJIT.

      See more
      LiteSpeed logo

      LiteSpeed

      1.7K
      3
      0
      1.7K
      3
      + 1
      0
      A drop-in Apache replacement and the leading high-performance, high-scalability server
        Be the first to leave a pro
        LiteSpeed logo
        LiteSpeed
        VS
        Ratchet PHP logo
        Ratchet PHP
        Gunicorn logo

        Gunicorn

        614
        274
        58
        614
        274
        + 1
        58
        A Python WSGI HTTP Server for UNIX
        Gunicorn logo
        Gunicorn
        VS
        Ratchet PHP logo
        Ratchet PHP

        related Gunicorn posts

        AWS Elastic Beanstalk
        AWS Elastic Beanstalk
        Heroku
        Heroku
        uWSGI
        uWSGI
        Gunicorn
        Gunicorn

        I use Gunicorn because does one thing - it’s a WSGI HTTP server - and it does it well. Deploy it quickly and easily, and let the rest of your stack do what the rest of your stack does well, wherever that may be.

        uWSGI “aims at developing a full stack for building hosting services” - if that’s a thing you need then ok, but I like the principle of doing one thing well, and I deploy to platforms like Heroku and AWS Elastic Beanstalk where the rest of the “hosting service” is provided and managed for me.

        See more
        Cowboy logo

        Cowboy

        582
        24
        15
        582
        24
        + 1
        15
        Small, fast, modular HTTP server written in Erlang.
        Cowboy logo
        Cowboy
        VS
        Ratchet PHP logo
        Ratchet PHP
        Unicorn logo

        Unicorn

        477
        292
        292
        477
        292
        + 1
        292
        Rack HTTP server for fast clients and Unix
        Unicorn logo
        Unicorn
        VS
        Ratchet PHP logo
        Ratchet PHP

        related Unicorn posts

        Simon Bettison
        Simon Bettison
        Managing Director at Bettison.org Limited · | 6 upvotes · 73.1K views
        atBettison.org LimitedBettison.org Limited
        Amazon EC2 Container Service
        Amazon EC2 Container Service
        Docker
        Docker
        Amazon VPC
        Amazon VPC
        Amazon Route 53
        Amazon Route 53
        Amazon SQS
        Amazon SQS
        Amazon SES
        Amazon SES
        Amazon CloudFront
        Amazon CloudFront
        nginx
        nginx
        Unicorn
        Unicorn
        Ruby
        Ruby
        Travis CI
        Travis CI
        Selenium
        Selenium
        RSpec
        RSpec
        Rails
        Rails
        Amazon ElastiCache
        Amazon ElastiCache
        Redis
        Redis
        Sidekiq
        Sidekiq
        Elasticsearch
        Elasticsearch
        PostgreSQL
        PostgreSQL

        In 2010 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

        Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

        PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

        Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

        Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

        We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

        Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

        See more
        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare · | 6 upvotes · 14.6K views
        atStackShareStackShare
        Rails
        Rails
        Puma
        Puma
        Unicorn
        Unicorn

        We switched from Unicorn (process model) to Puma (threaded model) to decrease the memory footprint of our Rails production web server. Memory indeed dropped from 6GB to only 1GB!

        We just had to decrease our worker count and increase our thread count instead. Performance (response time and throughput) remained the same, if not slightly better. We had no thread-safety errors, which was good.

        Free bonus points are:

        • Requests are blazing fast on our dev and staging environments!
        • Puma has first-class support for WebSockets, so we know for sure that Rails ActionCable or GraphQL subscriptions will work great.
        • Being on Puma makes us even more "default Rails"-compliant since it is the default Rails web server these days.
        See more
        Jetty logo

        Jetty

        304
        139
        41
        304
        139
        + 1
        41
        An open-source project providing an HTTP server, HTTP client, and javax.servlet container
        Jetty logo
        Jetty
        VS
        Ratchet PHP logo
        Ratchet PHP

        related Puma posts

        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare · | 6 upvotes · 14.6K views
        atStackShareStackShare
        Rails
        Rails
        Puma
        Puma
        Unicorn
        Unicorn

        We switched from Unicorn (process model) to Puma (threaded model) to decrease the memory footprint of our Rails production web server. Memory indeed dropped from 6GB to only 1GB!

        We just had to decrease our worker count and increase our thread count instead. Performance (response time and throughput) remained the same, if not slightly better. We had no thread-safety errors, which was good.

        Free bonus points are:

        • Requests are blazing fast on our dev and staging environments!
        • Puma has first-class support for WebSockets, so we know for sure that Rails ActionCable or GraphQL subscriptions will work great.
        • Being on Puma makes us even more "default Rails"-compliant since it is the default Rails web server these days.
        See more
        Caddy logo

        Caddy

        120
        37
        7
        120
        37
        + 1
        7
        The HTTP/2 Web Server with Automatic HTTPS
        Caddy logo
        Caddy
        VS
        Ratchet PHP logo
        Ratchet PHP

        related Caddy posts

        Scott Mebberson
        Scott Mebberson
        CTO / Chief Architect at Idearium · | 5 upvotes · 16.2K views
        Caddy
        Caddy
        nginx
        nginx

        We used to primarily use nginx for our static web server and proxy in-front of Node.js. Now, we use Caddy. And we couldn't be happier.

        Caddy is simpler on all fronts. Configuration is easier. Free HTTPS out of the box. Some fantastic plugins. And for the most part, it's fast.

        Don't get me wrong, it's not lost on me that Nginx is actually a superior product.

        But for the times when you don't need that extra performance, and complexity - take a look at Caddy.

        See more
        lighttpd logo

        lighttpd

        101
        27
        23
        101
        27
        + 1
        23
        A secure, fast, compliant, and very flexible web-server that has been optimized for high-performance environments
        lighttpd logo
        lighttpd
        VS
        Ratchet PHP logo
        Ratchet PHP
        Wildfly logo

        Wildfly

        58
        19
        2
        58
        19
        + 1
        2
        A Java EE8 Application Server
        Wildfly logo
        Wildfly
        VS
        Ratchet PHP logo
        Ratchet PHP
        JBoss logo

        JBoss

        57
        22
        0
        57
        22
        + 1
        0
        An open source Java EE-based application server
          Be the first to leave a pro
          JBoss logo
          JBoss
          VS
          Ratchet PHP logo
          Ratchet PHP
          NGINX Unit logo

          NGINX Unit

          49
          49
          0
          49
          49
          + 1
          0
          A dynamic web and application server with Go, PHP, Python, Perl, and Ruby support.
            Be the first to leave a pro
            NGINX Unit logo
            NGINX Unit
            VS
            Ratchet PHP logo
            Ratchet PHP
            Oracle Weblogic Server logo

            Oracle Weblogic Server

            34
            8
            0
            34
            8
            + 1
            0
            JEE Application Server
              Be the first to leave a pro
              Oracle Weblogic Server logo
              Oracle Weblogic Server
              VS
              Ratchet PHP logo
              Ratchet PHP
              Sanic logo

              Sanic

              34
              37
              7
              34
              37
              + 1
              7
              Python 3.5+ web server that's written to go fast
              Sanic logo
              Sanic
              VS
              Ratchet PHP logo
              Ratchet PHP