|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Frp||68,101||9||2 days ago||78||July 10, 2022||97||apache-2.0||Go|
|A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.|
|Caddy||47,606||118||334||a day ago||85||October 26, 2020||80||apache-2.0||Go|
|Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS|
|Vapor||22,858||6 days ago||November 16, 2021||113||mit||Swift|
|💧 A server-side Swift HTTP web framework.|
|Postgrest||20,624||4||19 hours ago||37||July 12, 2022||208||mit||Haskell|
|REST API for any Postgres database|
|Aiohttp||13,602||7,355||4,894||2 days ago||220||November 14, 2021||497||other||Python|
|Asynchronous HTTP client/server framework for asyncio and Python|
|A full-featured http proxy for node.js|
|a simple zero-configuration command-line http server|
|Chisel||9,160||2||21||4 days ago||27||February 03, 2022||184||mit||Go|
|A fast TCP/UDP tunnel over HTTP|
|Warp||8,145||73||355||19 hours ago||34||November 09, 2021||216||mit||Rust|
|A super-easy, composable, web server framework for warp speeds.|
|Proxygen||7,826||11 hours ago||40||other||C++|
|A collection of C++ HTTP libraries including an easy to use HTTP server.|
⚠️ This repository contains historical information about the Server APIs Work Group. This work is now being progressed in the Server category on the Swift Forums. All interested parties are invited to participate on the forums.
The Server APIs Work Group is responsible for steering the Swift Server APIs project, which is an evolving set of Swift libraries developed as part of the Swift open source project to provide fundamental capabilities for building server-oriented software.
The work group consisting of a core team, stakeholders from the server-side Swift community, and anyone who wants to get involved. The work group consists of three roles: core team member, stakeholder and contributor. Participants may have more than one role in the work group.
Everyone is welcome to contribute to the Server APIs Work Group through participating in a range of activities including joining as a stakeholder, participating in design discussions, asking or answering questions on the mailing lists, reporting or triaging bugs or by submitting pull requests to the project(s) for implementation or tests.
The work group is initially focussing on the creation of API proposals for base networking, security/encryption and HTTP parsing:
Base Networking: Provide a portable interface for low level socket based network based I/O, including TCP/IP and UDP protocols, IPv4 and IPv6 support and domain name resolution. Support should be provided to create and use both synchronous and asynchronous non-blocking connections.
Security and Encryption: Provide common cryptographic constants and cyphers along with keychain and certificate management, and SSL/TLS based secure transport. This must integrate with the base networking support to provide secure sockets, and with the HTTP parsing library to provide HTTPS support.
HTTP and WebSockets: Provide low level HTTP parsing, including HTTP, HTTP/2 and WebSocket support making it possible, in conjunction with the security and networking APIs, to create secure HTTP and WebSocket servers.
Analogous to the primary Core Team for Swift, the work group has a steering team that is responsible for providing overall technical direction, ensuring co-ordination both between the various API efforts (for example around Network, Security and HTTP integration for HTTPS) and with the wider Swift Core Libraries and language. Membership of the steering team is contribution based and is expected to evolve over time.
The initial steering team consists of:
The work group also has stakeholders who represent server-side frameworks or applications. They are responsible for providing early input on use cases and API design as part of the iterative design and implementation process, and to adopt the new APIs into their frameworks.
Joining and leaving the work group as a stakeholder is a straightforward process. The only requirement is to raise a Pull Request to add or remove your name from the stakeholder list in this project, which will act to add or remove you from invites to formal work group discussions.
The initial stakeholders consists of (alphabetically):
More information can be found in the Server APIs pages of swift.org, or by posting to the swift-server-dev mailing list.