Our great sponsors
-
RoadRunner
🤯 High-performance PHP application server, process manager written in Go and powered with plugins
-
souin
An HTTP cache system, RFC compliant, compatible with @tyktechnologies, @traefik, @caddyserver, @go-chi, @bnkamalesh, @beego, @devfeel, @labstack, @gofiber, @go-goyave, @go-kratos, @gin-gonic, @roadrunner-server, @zalando, @zeromicro, @nginx and @apache
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
sdk
🤖 RoadRunner Go SDK. Contains worker, pool, queues and other utilities and core RR features. (by roadrunner-server)
Built a Grafana RoadRunner dashboard to read all the server metrics (https://github.com/roadrunner-server/roadrunner/tree/master/dashboards)
HTTP plugin now support RFC 7234 caching options
RR doesn't know anything about PHP :) The primary purpose of the RR is to effectively pass the request from the user/web-server/queue/temporal/etc. to the underlying OS process using our protocol (similar to the IPv4 protocol) called Goridge. You may use our SDK to integrate it into your package. Or copy-paste some code from it that fits your needs (it's all MIT). Feel free to explore our org: https://github.com/roadrunner-server/
Yes, you are responsible for cleaning the memory after yourself. Most of modern frameworks can do it for you since they can control the state using DI. If you are looking for a more friendly way to manage memory take a look at https://github.com/spiral/framework It is Symfony like framework developed specifically for resident memory applications.