realworld-axum-sqlx VS sycamore

This was one of the objectives when we created https://github.com/launchbadge/realworld-axum-sqlx

Clap can actually load values from the environment now: https://github.com/launchbadge/realworld-axum-sqlx/blob/main/src/config.rs

I'm working on a PoC to rewrite the realworld app from launchbadge to use entrait: https://github.com/audunhalland/rust-realworld-ioc/ (work in progress), maybe it can be used as inspiration.

While there already exists a fantastic implementation of the spec written by the sqlx authors, I wanted to use this as a Rust playground for myself and others to poke around the ecosystem. I'm sure there's quite a bit of room for improvement, and I'm looking forward to opening this up for those in a similar boat and learning Rust.

I'm following some examples for creating a server with Axum like realworld-axum-sqlx and customize-extractor-error. The second one shows how to get request errors related to json and I'd like to know if there's anyway to make the where clause more error-proof.

I've just migrated from actix-web to axum, so it's the backend that I'm interested in people's thoughs on. I've taken a fair amount of design inspiration from the realworld-axum-sqlx project.

Here is a realworld-spec in Axum: https://github.com/launchbadge/realworld-axum-sqlx

https://github.com/launchbadge/realworld-axum-sqlx is Axum based implementation of the Realworld specification

Here's an example codebase using these features: https://github.com/launchbadge/realworld-axum-sqlx/blob/main/src/http/articles/listing.rs

Realworld Spec with Axum

Perseus is a fast frontend web development framework for Rust with built-in support for reactivity using Sycamore, server-side rendering, and much more. Sycamore is a frontend library that allows you to build interactive user interfaces with Rust. I’d say that Perseus is to Sycamore as Next.js is to React, so it’ll be helpful for you to have a fair understanding of Sycamore before jumping into using Perseus — although it’s not necessary to follow along in this article.

Now, I considered whether to spend more time fixing everything that now failed in sycamore 0.9. But there are major changes ahead which would require yet another major refactoring, to the point where I am not sure whether it would not be more of a rewrite than a refactoring, given my previous experiences with sycamore.

Sycamore.

Sycamore, Yew, or Seed if you want a full-stack solution. (Or Leptos if you want something that's faster but less mature.)

There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.

I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.

If you want to do fullstack/SPA stuff, check out Sycamore, Seed, and Yew.

If you want to do front-end SPA development, take a look at Yew, Seed, or Sycamore.

I have written a front-end (website) application in Rust that is used internally in production. I wouldn't recommend to use something like sycamore, leptos, dioxus, yew for you next puplic web-app now but i can absolutely see how this is used in the future as those libs mature.

There are several performant rust web frameworks: Sycamore - Uses an architecture like solidjs Leptos - Uses an architecture like solidjs Dioxus - Uses an architecture like react