Skip to content
This repository was archived by the owner on Aug 21, 2021. It is now read-only.
This repository was archived by the owner on Aug 21, 2021. It is now read-only.

Exchange Support from Database #123

Description

@AusIV

Several of our microservices have a command line argument telling them an exchange address to support. The ingest service has a hard-coded list of supported exchanges.

These all predate the Exchanges table in the database, so that was the only way to find out about available exchanges. Now that we have that information in the database, microservices should be able to get it from there.

I think the easy way to handle it would be for the microservices to use their RPC connections to find out what network they're attached to, query the database for all exchanges pertaining to that network, then start goroutines for each supported exchange. That would enable us to support multiple exchanges on a single network without having to run multiple instances of each service.

I think the only service that cares about an exchange but doesn't have an RPC connection is the ingest service, which would want to accept all supported exchanges regardless of network anyway.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions