Infrastructure

From Resonite Wiki
Revision as of 08:39, 3 March 2024 by ProbablePrime (talk | contribs) (Created page with "Resonite has networking infrastructure around the world. == Network Nodes == We run Network Nodes, which are servers around the world that run LNL Bridge and Relay services. These are used to help you connect to Resonite Sessions. We have these in: * Australia * Japan * Finland * US West Coast == Azure Managed Infrastructure == The majority of the Resonite Cloud runs on Azure's Managed Infrastructure as a part of Azure's service offerings. A combination of the followi...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Resonite has networking infrastructure around the world.

Network Nodes

We run Network Nodes, which are servers around the world that run LNL Bridge and Relay services. These are used to help you connect to Resonite Sessions.

We have these in:

  • Australia
  • Japan
  • Finland
  • US West Coast

Azure Managed Infrastructure

The majority of the Resonite Cloud runs on Azure's Managed Infrastructure as a part of Azure's service offerings. A combination of the following is used:

  • Azure Cosmos DB
  • Azure VMs
  • Azure Table Storage
  • Azure API Service
  • Azure Redis
  • Azure Signal R

Miscellaneous Systems

Some systems run on more traditional infrastructure for things like:

Infrastructure Help

Resonite's community cares a lot and due to this we have had offers of help with Infrastructure. Resonite currently do not need any form of infrastructure help including:

  • Additional Servers
  • Additional Asset Variant Workers
  • Additional Networking Nodes
  • Infrastructure/Site Reliability Staff

If you're experiencing issues that you think may be due to Infrastructure related matters, please follow our regular bug reporting process.