async-http-client VS swift-nio

import PackageDescription let package = Package( name: "WelcomeEmail", dependencies: [ .package(url: "https://github.com/swift-server/async-http-client.git", from: "1.0.0"), ], targets: [ .target( name: "WelcomeEmail", dependencies: [ .product(name: "AsyncHTTPClient", package: "async-http-client"), ]) ] )

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.