Network Services Working Group
Every company building Rust network services hits the same walls: fragmented ecosystem choices, undocumented best practices locked inside individual organizations, and library gaps that no single team can justify fixing alone. This working group brings those teams together to publish shared guidance, prioritize ecosystem gaps, and coordinate fixes.
Scope: HTTP servers, proxies, gRPC services, async service frameworks, event processors, and the infrastructure around them. If your team runs Rust in production for anything involving network I/O and async runtimes, this is for you.
Status
The working group held its kickoff meeting in early 2025 and is now scheduling regular meetings. Async discussion is ongoing in the Zulip thread. We're looking for members to help shape the agenda and first deliverables.
Goals
- Publish reference network stacks for common use cases (HTTP services, gRPC, high-throughput proxies, event processors), so new teams don't have to rediscover what large organizations already know.
- Surface and prioritize ecosystem gaps across member organizations, turning individual frustrations into a shared backlog with real resources behind it.
- Coordinate funding and engineering contributions to close those gaps in upstream crates, working with existing maintainers.
Get Involved
Participation is open to everyone, including non-RCN members.
- Join the conversation: follow the Network Services WG topic on Zulip
- Shape the next meeting: fill out the scheduling poll and share it with anyone who'd want to join
- See what we discussed last time: check the past meeting notes below
Meetings are roughly monthly, about an hour. Between meetings, coordination happens on Zulip.
Calendar
See the RCN meeting calendar for upcoming meetings.
Next Meeting
Currently scheduling. Fill out the scheduling poll if you want to join, and please share it around.
Discussion: Network Services WG meeting schedule on Zulip