roadrunner

why link to the old URL when linking to its redirected one is less confusing? https://github.com/roadrunner-server/roadrunner#readme (MIT)

Hey @kdunglas :) Nice project :) I just wanted to add a few notes: > Roadrunner executes php-cli and connects it to its web server through GRPC; RR communicates with the PHP process via pipes (stdin/out/err) via our protocol (similar to the IP protocol, we also have a tcp/unix-socket options and shared memory is coming soon). The RR server itself then has various options to connect to the world: - gRPC (w/o the need to install the `gRPC-php` extension), HTTP (with a lot of different middleware), HTTPS, fCGI. - Queues: kafka, rabbitmq, sqs, beanstalk, nats (with like priorities and so on) - KV/noSQL: memcached, redis, boltdb, memory. - Workflows: Temporal. I might forget smt, but the main idea is to have a very extensible server. With very little knowledge about Go, you may extend it with your plugins and build your RR binary. Or even em

What is the difference between this and Roadrunner? It seems to do the same stuff. https://github.com/roadrunner-server/roadrunner

I really love Django and Wagtail but I just can’t stop writing Go(lang) code, it’s just so addictive. It’s a pity there aren’t any WSGI servers written in Go that Would allow you to intermix Go and Python code seamlessly. Kind of like what Roadrunner does for php [0] [0] https://github.com/spiral/roadrunner

In typical PHP applications, the entire application is bootstraped, executed and teared down for every request. RoadRunner lets you run "workers" (php processes) that perform all the bootstrapping just once, and then receive-process-reply to requests. The use case is to avoid the (possibly expensive, especially with modern frameworks) bootstrapping for every request. Check the symfony integration example for instance [1]. Everything that's outside of the while ($req = $psr7->acceptRequest()) { ... } is usually run for every request in traditional PHP, whereas here it is only run once when initializing the worker and then that while block reads/executes/replies to each specific request. The problem with this approach is that you now need to be careful not to leave unwanted stuff behind (open files / db connections, static $propertie

Can anyone dumb this down for me? I don't really understand this use case - is this for PHP developers to eke out some more performance for their web apps? The goridge library (https://github.com/spiral/goridge) makes a little more sense to me; it's a bridge between golang and PHP via RPC. I went through the code (https://github.com/spiral/roadrunner) but it doesn't seem like something you can swap into an existing PHP project. Can anyone explain what use case this might be for?