Refactor so that eth-json-rpc endpoints use GraphQL to interface with Postgres #52

New Issue

i-norden · 2021-04-15T17:46:16Z

i-norden commented

2021-04-15 17:46:16 +00:00

Rather than interfacing directly through a pg connection

srw commented

2021-04-15 20:00:22 +00:00

To add some context from previous discussions, and this is kind of a rough overview from a sysop perspective so there could be per service requirements that weren't taken into account, further refinement etc.

My thinking here is that arch0-1 vulcanize geth talks directly to db0-1 postgresql, then db0-1 postgraphile end points sit in front of each database and become the central place all other database driven services talk to. Likewise arch0-1 ipld-eth-server talks directly to vulcanize geth and all other geth dependent services talk only to the end points that ipld presents.

If ipld-eth-server is itself creating postgraphile endpoints maybe that first graphql layer sitting on the db0-1 becomes redundant but I think this at least begins to paint a picture of centralizing the access paths different services take rather than having everything reaching directly to the database and geth.

To add some context from previous discussions, and this is kind of a rough overview from a sysop perspective so there could be per service requirements that weren't taken into account, further refinement etc. My thinking here is that `arch0-1 vulcanize geth` talks directly to `db0-1 postgresql`, then `db0-1 postgraphile end points` sit in front of each database and become the central place all other database driven services talk to. Likewise `arch0-1 ipld-eth-server` talks directly to vulcanize geth and all other geth dependent services talk only to the end points that ipld presents. If ipld-eth-server is itself creating postgraphile endpoints maybe that first graphql layer sitting on the db0-1 becomes redundant but I think this at least begins to paint a picture of centralizing the access paths different services take rather than having everything reaching directly to the database and geth.

AFDudley commented

2023-06-10 16:24:27 +00:00

Seems as though this was resolved elsewhere.

Sign in to join this conversation.

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/ipld-eth-server#52