Network Gateway Setup Overview

Network Gateway Architecture

Introduction

A Network Gateway deployment consists of:

  • One or more Radix Nodes, in their Full Node configuration, with the transaction endpoint of the Core API enabled.

  • A single[1] (Network Gateway) Data Aggregator.

  • A PostgreSQL Database

  • One or more (Network Gateway) Gateway APIs

If you are looking to run a local system for development of integrations with a Network Gateway, you can see the documentation on running a toy local environment which runs the full stack in docker compose. This isn’t suitable for production workloads.

For production systems, these four components will need to be set up in a resilient configuration, and monitored. Depending on your infrastructure provider, there are many ways to deploy these components - so in these docs, we’ll stick to the recommended requirements for a production setup, and explain how the services can be configured and monitored so that this can be adapted to your infrastructure requirements.

Comparison with Radix Nodes

Radix Nodes are built with Java, whereas the Network Gateway components are built with C#, using the .NET 6 runtime.

Deployment approaches

RDX Works provides the Data Aggregator and Gateway APIs as both:

You can choose to configure / run these as best fits your needs. The Docker containers are ready to be configured and run out of the box, and are recommended as the easiest deployment option. If you choose to run the binaries themselves (say, via systemd), you will need to be set up the server to run an ASP .NET Core app, running in the .NET 6 runtime, and configured with appropriate resiliency, to eg restart on failure.


1. For v1, only a single Data Aggregator is supported. In future versions, we hope to add support for allowing deployment of multiple Data Aggregators, which will configure themselves as a primary and 0 or more secondaries, ready for hot failover if required