diesel_async VS mirrord

So I want to use diesel_async in my web backend.

The already linked discussion from last time already contains a lot of information about this. Diesel itself does not provide async operations and that will likely remain that way for a foreseeable future. At least my preferred solution is to keep async support in a separate crate. A prototype for this is currently available here. Keep in mind that this is not released yet, so there might be bugs everywhere. I plan to cut a first release of this crate after the final release of diesel 2.0, which means hopefully soon. As for ETA's: I generally do not give any ETA's for releases, as this is currently a free time project for me.

So, diesel is an ORM that tries to take full advantage of rust's typing expressivity to allow for statically checked, and fast, queries. I absolutely loved it when trying it out the first time.

i don't see why you or anyone else would consider it too big of an issue that Diesel doesn't have async. For those who really want async diesel right now, the author already released diesel_async as a stop-gap solution, but even without that there's nothing wrong with using spawn_blocking. It feels worse than it really is to use blocking thread pools; until io_uring is a thing, there's no real getting around the necessity of threads being blocked for I/O and so adding async to the mix doesn't magically make things faster.

As for now there is an prototype available here. It's technically feature complete, but depends on a unpublished diesel version + has some remaining bugs with certain mysql versions. If that is fixed I will likely publish a first alpha version officially. That can take same time because that's a second large project that needs maintenance time beside diesel itself and that's quite a lot to do in my free time. You can support this work by sponsoring me on github

Async support for diesel currently lives in a separate repository as there are language level blocking issues for publishing a version of this crate where we could commit to a stable release at all. See the corresponding diesel issue for details.

https://github.com/weiznich/diesel_async tho'.

Weiznich (the maintainer of Diesel) has created an experimental async version of the diesel Connection and RunQueryDsl traits, which should help with ease-of-use for Diesel within async contexts. It is not yet published on crates, but you can find it here: https://github.com/weiznich/diesel_async

So, you've been using mirrord to simplify your development process (if you haven’t, go here!). Naturally, you want the traffic from the app you're debugging to go through the cluster environment, so your app can communicate with its clustery pals. There is a problem though: your latest change adds some new columns to the database, and you don’t want to modify the database in the cluster and affect everyone else working on it. You do have a local instance of the database that you can modify, so your app can use that, but you still want it to talk to all the other components in the cluster. So what now? The new outgoing traffic filter feature is here to solve exactly this type of problem!

I had the pleasure of talking to Eyal @ CTO at Metalbear and the maintainer of Mirrord. I got some crazy insights.

If you want to take mirrord for a spin, check out the quick start guide. We’d love to hear about your experience or just general thoughts - chat us up on our Discord or open an issue or discussion on GitHub.

We're building an open-source tool called mirrord which lets you run a local process in the context of a pod in your cloud environment. We often get asked how mirrord is different from Telepresence and so we decided to write a short blog post about it, which we hope would be valuable to those interested in local Kubernetes development:

Hands-on tutorial of mirrord.dev with the creators and Rawkode!

if you are interested in k8s, iptables, hooking libc, asm etc https://github.com/metalbear-co/mirrord

I gave my first CNCF talk in Toronto yesterday, talking about https://github.com/metalbear-co/mirrord , how all the features work, and how it's engineered!