components

How coroutines help

Hypervel runs applications in long lived workers and uses coroutines to serve many requests, jobs, and connections at once. When one coroutine is waiting on a database query, a cache lookup, a queue operation, file access, or an HTTP request, the worker keeps serving other work instead of sitting idle. The developer writes ordinary sequential code, and the runtime yields to other work while yours waits. The framework is built for traditional web applications, APIs, microservices, real time services, and background workers, which all spend meaningful time waiting on external systems.

Framework features

Hypervel includes the pieces expected from a modern full stack framework. It offers fast expressive routing and middleware, a dependency injection container with a service provider system, the Eloquent ORM with schema building and migrations, and multiple session and cache stores. It also covers background jobs with batching and scheduling, real time event broadcasting and WebSocket support, authentication, authorization, validation, notifications, mail, and filesystem storage. Blade templates and Vite integrate for full stack apps, and first class coroutines enable concurrent HTTP requests with persistent database and Redis connection pools.

Requirements and license

The 0.4 branch requires PHP 8.4 or later and Swoole 6.2.2 or later. Redis integrations use the PhpRedis extension 6.1 or later, and Predis is not supported. The README warns that this branch holds the ongoing, unreleased 0.4 rewrite, so APIs, behavior, configuration, and package internals may change without notice and the branch should not be used for real projects until a beta is tagged. Published documentation currently covers the 0.3 release, with in progress 0.4 docs available in the repository.

Editorial conclusion

Hypervel is open source software under the MIT license and its 0.4 development branch targets PHP 8.4 with Swoole 6.2.2 or later.