(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.

Thanks for the reply. Also, when I run in an microservice architecture, how does hasura handles say for example websocket across the services? Do we need to depend on any other library?

Can you share some samples for these things if available. I will be glad to look at it.

That works automatically!

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?)