azure/dotnetty

DotNetty project – a port of netty, event-driven asynchronous network application framework

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 16th, 2026
Created on May 8th, 2015
Open Issues & Pull Requests: 174 (+0)
GitHub issues: Enabled
Number of forks: 1,013
Total Stargazers: 4,255 (+0)
Total Subscribers: 392 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 202.3 days
Mean response time: 711.9 days
90th percentile: 2115.5 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,091 days
Stale 30+ days: 7
Stale 90+ days: 7

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

DotNetty is an event-driven asynchronous network application framework that ports the Java Netty library to the .NET ecosystem.

The project addresses the need for high-performance, non-blocking network I/O in .NET applications. It provides an abstraction layer over low-level socket operations, allowing developers to build network services using an event-driven model where handlers process data as it arrives. The framework uses channels, pipelines, and handlers to organize network logic, enabling clean separation of concerns and composable protocol implementations.

Developers should choose DotNetty when building network services that require efficient handling of many concurrent connections with minimal resource overhead. It suits projects implementing custom protocols, building real-time communication systems, or porting existing Netty-based Java applications to .NET. The framework is particularly valuable for scenarios where traditional synchronous socket programming would create scalability bottlenecks, as the asynchronous model allows a small thread pool to manage thousands of connections.

The project maintains steady activity with regular commits addressing bug fixes and feature enhancements. Pull requests receive consistent review and integration into the codebase. The maintainers respond to issues and incorporate community contributions, indicating ongoing stewardship of the codebase.