easy-swoole/easyswoole

swoole,easyswoole,swoole framework

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 14th, 2026
Created on March 15th, 2017
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 502
Total Stargazers: 4,757 (+0)
Total Subscribers: 145 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 37.2 days
Mean response time: 347.4 days
90th percentile: 947.4 days
Tracked items: 14

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 325 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

EasySwoole is a high-performance PHP framework built on the Swoole extension that enables asynchronous, multi-process applications.

EasySwoole addresses the performance overhead of traditional PHP by leveraging Swoole's event-driven architecture to keep the application in memory and eliminate repeated process initialization and file loading. The framework wraps Swoole's server capabilities while preserving their original functionality, allowing developers to build applications that handle HTTP, TCP, WebSocket, and UDP protocols simultaneously within a single process model. It provides built-in coroutine support across database clients (MySQL, Redis), HTTP clients, and RPC, along with middleware support for all protocol types, a dependency injection container, connection pooling, and task queuing for asynchronous work.

EasySwoole suits teams building high-throughput APIs and real-time services where traditional PHP-FPM architecture becomes a bottleneck. It works well for microservices, WebSocket-based applications, and systems requiring persistent connections or background job processing. The framework is particularly valuable when you need to serve many concurrent connections without spawning new processes for each request. Developers should expect to learn Swoole's async model and coroutine patterns, though the framework aims to minimize this learning curve through encapsulation. The project includes a router, parameter validator, ORM, logging, cron scheduling, and remote console tooling, reducing the need for external dependencies.

The project maintains active community engagement through multiple discussion channels and commercial support options. Development activity shows consistent attention to the codebase with regular updates and documentation maintenance across the main repository and associated documentation and demo repositories.