We are proud to announce the first high-scale production-grade server-side Swift based web server.
Thank you to the over 200 CTOs that provided valuable feedback and 800+ developers that have been using our system since launch. You have all been instrumental in getting us to where we are today, and we truly appreciate your support and encouragement.
For everyone we met at WWDC/AltConf- thank you for taking the time and seeing our demo. Also, we are excited and impressed by some of the cool projects you are working on. At WWDC we committed to making the platform open-source and in less than 3 months we have achieved this.
Why are we Production-Grade Server-Side Swift Server?
SwiftEngine is aimed at being a highly resilient and scalable server-side platform, and as such the goal of the platform is to overcome some of the inherent vulnerabilities of other modern platforms currently in the market.
Crashes don’t bring down the entire server
A key example of what this means for production deployments is that each request and endpoint is contained within its own process; a crash for one request does not bring down the entire server.
Memory leaks are ephemeral
Memory leaks or other bugs are ephemeral and only live for the duration of the request, instead of transcending the lifetime of the server.
In addition to being highly resilient and scalable…
No processing power is spent on maintaining a runtime environment
SwiftEngine is also highly performant due to the pre-compiled nature of all the endpoints because under the hood SwiftEngine uses Swift as its core language. All code that is executed on the server is a compiled (native object code) version of the source code. Thus, no processing power is spent on maintaining a runtime environment.
No manual compilation and configuration is required by the developer
Lastly, by not least(ly), SwiftEngine aims at being a highly productive environment, while abstracting away some of the mundane build and devops related tasks. As such, SwiftEngine is a complete autonomous solution. This means that no manual compilation and configuration is required by the developer.
Web-enabled debugging interface
Any compile time and runtime errors are also handled by SwiftEngine, and a full stack trace with diagnostics is displayed to the developer in a beautiful and easy to follow interface.
Long gone are the day of manual compilation and dealing with shell log dumps.
Simply save a file and request the URL, and SwiftEngine will automatically compile, cache, and serve the requested results.
Bugs are now contained in that specific endpoint only
In order to achieve these goals, there is a slight change of a paradigm in the methodology of how a typical Swift project functions. The primary shift is in the independently asynchronous processing of the various endpoints. This means that each one of the endpoints is compiled and maintained on its own, thus an introduction of a bug within one endpoint has no effect on the functionality of the other endpoints.
How can you help?
We are truly blessed to have some of the best developer community members. Without you guys, we are not sure how we would have gotten to where we are today.
Our ask is simple, if you get a chance, please check out our Github repo.
PS. If you get a chance, can you please make sure you star the repo as well?
PPS. To all the bloggers, media, influencers, thank you for sharing this post and helping us spread the word. You are awesome, and we couldn’t have done this without your help.