I'd like to introduce the Hypervel framework. It was initially created to incorporate coroutines into high I/O demand projects in my team, while helping colleagues quickly adapt using their familiar Laravel framework. After internal testing in company projects last year, I've gradually completed the missing features and documentation over the past few months, so I've decided to officially share it with everyone.
Hypervel is a framework built on Hyperf's underlying components (similar to the relationship between Laravel and Symfony), with all of Laravel's core components restructured and integrated. It resolves the States Bleeding issues that occur during coroutine context switching, something not considered in Laravel's original design, allowing these components to seamlessly integrate into the Hypervel framework. Essentially, all the basic components documented in Laravel's official documentation have been completely migrated.
Some might wonder why we need Hypervel when Laravel Octane exists. Isn't this just reinventing the wheel? The fundamental reason is that Laravel's core design doesn't account for coroutine switching issues. While Octane reduces request costs by keeping the framework resident in memory, it doesn't support any Non-Blocking I/O features. If your system isn't I/O intensive, Octane can still be helpful, but for requests with heavy I/O demands and slower response times, Octane becomes ineffective.
For example, with the recent boom in AI development, more products are integrating LLMs into their services. Each LLM request might take several seconds, and you'll find that under high request volumes, your workers are quickly exhausted. Then you can only increase your machine resource by either vertical or horizontal scaling.
If you're a Laravel developer, you'll find Hypervel easy to use (though developers should have a solid understanding of common operating systems, I/O, and coroutine concepts to avoid pitfalls).
Here are the main features of Hypervel:
1. Provides the same elegant development experience as Laravel, reducing the learning curve for the new framework.
2. Extremely high performance, with QPS 10 times higher than Octane in non-I/O scenarios, and hundreds of times higher in I/O-intensive scenarios.
3. Coroutine support out out the box, with even PHP's built-in I/O functions automatically being hooked to support coroutines.
4. Support for object pools and connection pools.
5. Seamless two-way communication with your existing Laravel projects through Cache, Lock, and Queue.
6. Coroutine support not limited to handling HTTP requests. Queue and Scheduling can also leverage coroutines, allowing a single process to achieve the concurrency that would require hundreds of workers in Laravel
If you're interested in this framework, just give it a try.
Hypervel is a framework built on Hyperf's underlying components (similar to the relationship between Laravel and Symfony), with all of Laravel's core components restructured and integrated. It resolves the States Bleeding issues that occur during coroutine context switching, something not considered in Laravel's original design, allowing these components to seamlessly integrate into the Hypervel framework. Essentially, all the basic components documented in Laravel's official documentation have been completely migrated.
Some might wonder why we need Hypervel when Laravel Octane exists. Isn't this just reinventing the wheel? The fundamental reason is that Laravel's core design doesn't account for coroutine switching issues. While Octane reduces request costs by keeping the framework resident in memory, it doesn't support any Non-Blocking I/O features. If your system isn't I/O intensive, Octane can still be helpful, but for requests with heavy I/O demands and slower response times, Octane becomes ineffective.
For example, with the recent boom in AI development, more products are integrating LLMs into their services. Each LLM request might take several seconds, and you'll find that under high request volumes, your workers are quickly exhausted. Then you can only increase your machine resource by either vertical or horizontal scaling.
If you're a Laravel developer, you'll find Hypervel easy to use (though developers should have a solid understanding of common operating systems, I/O, and coroutine concepts to avoid pitfalls).
Here are the main features of Hypervel:
1. Provides the same elegant development experience as Laravel, reducing the learning curve for the new framework. 2. Extremely high performance, with QPS 10 times higher than Octane in non-I/O scenarios, and hundreds of times higher in I/O-intensive scenarios. 3. Coroutine support out out the box, with even PHP's built-in I/O functions automatically being hooked to support coroutines. 4. Support for object pools and connection pools. 5. Seamless two-way communication with your existing Laravel projects through Cache, Lock, and Queue. 6. Coroutine support not limited to handling HTTP requests. Queue and Scheduling can also leverage coroutines, allowing a single process to achieve the concurrency that would require hundreds of workers in Laravel
If you're interested in this framework, just give it a try.
For more details, please visit the official website: https://hypervel.org