[FEATURE]: ServerSide vs ClientSide run mode

skrdgraph commented 1 year ago

Use case

Ratel is a great tool to use on top of Dgraph. The way it works today is mostly in ClientSide & not in ServerSide mode. The particular use-case where this can be very handy is:

Imagine a setup in a secure environment, where we have Dgraph Alpha & Zero running.
If I want to connect Ratel to this setup, I would be forced to setup an ingress to my Alpha - and connect Ratel (from my local computer) to the Ingress. This is equivalent to exposing alpha publicly.
Now if you deploy a Ratel pod in the secure environment, it cannot help us connect to the Dgraph Alpha. Even if we have an ingress for Ratel. Because it operates as a client. And still cannot to the Alpha as they are not available over internet.

As we move towards IaaC (infra as code), users will find it easy to have a ratel deployed alongside dgraph. And forcing a server side connection on ratel will help solve this problem. This would help make Dgraph-ops easier.

More context around this: https://dgraph-community.slack.com/archives/C051UPZUGKE/p1682524807448859

Link to examples and research

NA

Solution proposal

NextJS (has some server side rendering opportunities). We should consider having ratel run in this mode vs client mode.

Additional information.

NA

rjsadow commented 4 months ago

Hi, is there any chance this issue will be supported by the team? It would be hugely beneficial!

github-actions[bot] commented 1 month ago

This issue has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open.

rjsadow commented 1 month ago

Bump

dgraph-io / ratel