alchemy VS swift-nio

I'm curious if anyone has played with Alchemy.

Hey r/swift, after years of lurking here I’ve got something to contribute! Over the recent year I’ve been working on a web framework for everyone’s favorite language. Its focus is on clean,‏‏‎‏‏‎‏‏‎‏‏‎­elegant, full featured APIs and sharing code between Swift clients and server. There are a couple quickstart projects in there (including one that’s Fullstack; iOS, Backend, Shared all in a single Xcode Project!) to peruse. There’s also a ton of docs that are geared towards fellow Swifters who are just getting started in backend dev. Would love for you guys to check it out and give feedback! https://github.com/alchemy-swift/alchemy

```

There’s also a bunch more examples of APIs around QueryBuilder, Caching, Jobs, Queues, Redis, Commands, Authentication, Middleware etc[1]. And everything will be converted to async/await in the coming days.

1: https://github.com/alchemy-swift/alchemy/tree/main/Docs#docs

It's aimed to be an alternative, vapor is great and super customizable but I wanted to create something that was a little more "convention over configuration" so that out of the box things were a little more simple to follow and get going, if you are willing to do it the Alchemy "way of doing things". For example the ORM models can be super light weight,if you name the database table columns after the CodingKeys of the model.

Alchemy is a recently released Swift web framework.

In addition to what others have said, SwiftNIO is a possible low-level web server framework.

Also look at: Hummingbird https://github.com/hummingbird-project/hummingbird Smoke https://github.com/amzn/smoke-framework Swift NIO https://github.com/apple/swift-nio

You could take a look a swift-nio (https://github.com/apple/swift-nio) which is a pretty high-throughput system. swift-nio does this using some reference-counted GC where it simplifies the code and doesn't affect performance. Otherwise, value-types are used which incur no GC overhead (unless they are copy-on-write, and backed by something that requires reference counting).

The UI and the Core are mainly written by Swift. The proxy server is powered by Apple Swift-NIO. Some critical parts (deal with low-level system APIs, high performant JSON Parser, de/compression, protobuf, BoringSSL,...) are written by Objective-C and C. For some parts that deal with Pointer, or C library, I continue using Objective-C since it's easier than using a bunch of Unsafe Swift classes (UnsafePointer, UnsafeMutablePointer, UnsafeRawPointer, etc)

> Why should they? That isn't their target audience.

Because they need it?

Apple discontinued macOS server, i bet they use Linux in some of their servers

All their networking related libs are available and tested for Linux [1, 2]

Let's not forget that they package Swift for Linux, and now also for Windows [3]

Swift is crossplatform language (you not wanting to understand it doesn't change this fact), it's not a macOS framework

[1] - https://github.com/apple/swift-nio

[2] - https://github.com/apple/swift-protobuf/blob/main/.github/wo...

[3] - https://forums.swift.org/t/announcing-swift-5-6-2-for-linux-...

I would look at NIO or something that uses it, like https://diamantidis.github.io/2019/10/27/swift-nio-server-in-an-ios-app

i use swiftnio to spin up http servers. lots of documentation online. your app logic will be the same as ios but without swiftui and uikit.

Depending on what you need, SwiftNIO might do the trick.

If you want something a little more robust for a low-level TCP connection, you can also use SwiftNIO.