grpc-web VS diesel

A proxy is required to communicate from web clients to a server running gRPC, and there are only two choices for this proxy: a. The Improbable gRPC-Web client or b. The Google gRPC-Web client

I'll have to try the Improbable method (https://github.com/improbable-eng/grpc-web) - as it definitely includes a websocket transport, hopefully this multiplexes requests on that transport and would hence solve the problem. I'll post again once I know...

I think you should check out https://github.com/improbable-eng/grpc-web/tree/master/go/grpcwebproxy

What I like with gRPC is that it allows both client and server side streaming. Twirp seems to not have this feature at all. In contrast the https://github.com/improbable-eng/grpc-web even supports server and client streaming while wrapping gRPC in a HTTP1.1 Web connection.

I highly recommend also to look into https://github.com/improbable-eng/grpc-web in contrast to the 'official' gRPC-web from google the improbable-eng Implementation can do both server side and client side gRPC streaming (when used with their JavaScript client library) and all this on an http1.1/websocket basis...

We use https://github.com/improbable-eng/grpc-web for the server part with https://github.com/protobufjs/protobuf.js on the frontend.

I'm debating whether or not to rely on grpc for all client to API transport using improbable-eng's grpc-web project. The hesitation I'm running into is concern over unforeseen pitfalls. The fact that it isn't widely used is the main cause for my apprehension.

If you use https://github.com/improbable-eng/grpc-web you do not need envoy, you can wrap your golang grpc connection. I then mux the grpc and grpc-web so that I can use the same endpoint to serve http1 and http2 clients. This makes it easy to host on the cloud, eg. google cloud run.

I'm setting up a server portion of a website which uses (g)RPC. My dev setup is a docker-compose.yml that starts up my server on 50051 & another service that runs grpcwebproxy (exposes 8080 and proxies to my server @ 50051).

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/