(I'm from Hasura)
Hasura connects to a read replicas and manages connection pooling across the database cluster.
Hasura itself is stateless so it doesn't do the database replication.
Hasura connects to a read replicas and manages connection pooling across the database cluster.
Hasura itself is stateless so it doesn't do the database replication.
Can you share some samples for these things if available. I will be glad to look at it.
1. During the lifetime of a websocket connection, bytes should be routed to the same Hasura instance. This most service routers / load balancers should take care of automatically.
2. Subsequent connections from different clients to Hasura need not go to the same instance! This makes horizontal scaling painless.
(Is this what you meant?)