async-http-client VS alchemy

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"), ]) ] )

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.