Catalytic VS diesel

After years of working, I finally completed Beezle Social, discover local events!

Beezle Social is an app that is ready to be downloaded on the App Store and possibly soon on the Play store as well! With Beezle, you can explore events happening nearby. Check out the website at https://beezleapp.com/. The app can be downloaded at: https://apps.apple.com/us/app/beezle-social/id1661982809. I completed this on my own.

Rust is used at the backend. I did choose Rust because of its safety and speed. I took me awhile to get used to the type-system, but after that, I was amazed by the functionality and ecosystem. It is a joy working with macro's, cargo and code quality of other libraries.

Swift is used at the frontend. Obviously I preferred Swift over Obj-c. I used SwiftUI + UIKit to make the UI. The whole chatting part is done with UIKit because SwiftUI does not support advanced text editing options. I used some hacks in the chatting part to make sure SwiftUI doesn't reload everything all the time when a new message comes in.

AWS is used at the deploying side. I used ECS and Docker to deploy the server and a lot of other services for media, CDN and mailing system.

Beezle used libraries I created: https://github.com/Jasperav/Catalytic and https://github.com/Jasperav/GRDB-ORM. Catalytic is an ORM for the scylla-rust-driver and GRDB-ORM an ORM for GRDB.

I am happy to answer any question! Please download the app, leave a review and ping me if you missing features.

The Cargo.lock file: https://github.com/Jasperav/Catalytic/blob/versions/Cargo.lock

7. Diesel

Both seem nice. However, both of them rely very heavily on prepared statements. Unfortunately, using prepared statements is a no-go when you use connection poolers like pgbouncer, or in my case AWS RDS proxy. A discussion in Diesel indicates that disel is not going to provide any support for disabling prepared stements (https://github.com/diesel-rs/diesel/discussions/3575), and a discussion on sqlx hints that disabling prepared statements is possible, but I haven't found any documentation or examples for it.

In addition we are experimenting with prebuild versions of diesel-cli that can be installed directly. We have a set of prebuilt binaries here. We are interested in feedback about how the provided binaries work on your platform.

First of all thanks for making this great tool. As it happens I currently toy around with using it for diesel-cli releases. See the WIP PR here. I think diesel-cli is a good example of a tool that depends on system libraries as it needs to link native database drivers, so this new release is welcome. Defining the dependencies seems to allow easily building things on x86_64-unknown-linux-gnu and x86_64-apple-darwin. It seems to pick up everything in the right way there.

I did look at mysql initially. Then I started checking other crates. Diesel is an Object Relation Model (ORM), I'm not yet keen on taking on the complication of learning ORM, I give this crate a pass in the meantime.

I would recommend people look at diesel from Rust for how nice it could be. https://diesel.rs/ Look at the complex queries example. So much more readable and easier to understand.

Most wanted missing features in diesel

There are two problems with using Rust for web servers:

1. The only production-ready Rust web servers require writing async request handlers. Async Rust is not fun.

2. The only good Postgres client library is async: https://crates.io/crates/sqlx

I'm trying to remedy the first problem with https://crates.io/crates/servlin .

Solving the second problem will be another project. I hope someone else does it. There is https://crates.io/crates/diesel but it has the same problem as async Rust: incomprehensible compiler errors.

Lemmy is written in Rust using Actix Web and Diesel.rs.

https://actix.rs/

https://diesel.rs/