Destiny

Destiny is a standalone lightweight web server that makes use of the latest Swift features to push performance to the absolute limits of the Swift Language, and designed to require the minimum amount of dependencies.

It provides a router (which is used via a Swift Macro) that accepts router groups, redirects, middleware and routes for processing requests.

Features like TLS/SSL, Web Sockets and embedded support are coming soon.

Roadmap

• Custom hostname and port (Nov 8, 2024)
• Middleware and Routes (Nov 8, 2024)
• Register middleware/routes after starting server (Nov 8, 2024)
• Support multiple data representations (Nov 8, 2024)
• Routes with custom parameters (Nov 8, 2024)
• Configure settings via Command Line Arguments (Dec 11, 2024)
• Compression (Dec 24, 2024 | see Swift Compression)
• Hybrid Routes (Dec 24, 2024 | see ConditionalRouteResponderProtocol)
• CORS (Dynamic CORS implemented Dec 9, 2024)
• Redirects (Static Redirects implemented Dec 11, 2024)
• Router Groups
• Metric Middleware
• Queries
• Commands
• Data Validation (form, POST, etc)
• Authentication
• TLS/SSL
• Web Sockets
• SIMD processing for headers
• Response/data streaming
• Support custom middleware & routes in default #router
• Support third-party macro expansions in #router
• Unit testing middleware/routes/requests
• Better handling of clients to unlock more throughput
• CSS & JavaScript minification (separate repo?)
• Swift-APNS (separate repo?)
• Embedded support

Getting started

coming soon...

Command Line Arguments

Command Line Arguments are prefixed using double hyphens. Command Line Argument aliases are prefixed using a single hyphen.

hostname

Assign the hostname of the server.

• Aliases: h
• Usage: --hostname <hostname>

port

Assigns the port of the server.

• Aliases: p
• Usage: --port <port>

maxpendingconnections

Assigns the maximum pending connections the server can queue.

• Aliases: mpc
• Usage: --maxpendingconnections <max pending connections>

Benchmarks

• Libraries tested
  • RandomHashTags/destiny v0.1.0 (this library)
  • hummingbird-project/hummingbird v2.1.0
  • vapor/vapor v4.106.0

Static

Initial testing of a basic HTML response shows that this library has the lowest server latency and most consistent timings when serving the same content.

Dynamic

Depends on how much dynamic content you add, but initial testing compared to a Static response cost only a few microseconds more (~10-50). I am actively researching and testing improvements.

Conclusion

This library is the clear leader in reliability, performance and efficiency. Static content offer the best performance, while dynamic content still tops the charts.

Contributing

Create a PR.