Infrastructure: Difference between revisions

From Resonite Wiki
make page translatable
Marked this version for translation
 
Line 1: Line 1:
<languages/>
<languages/>


<translate>Resonite has networking infrastructure around the world.</translate>
<translate><!--T:1--> Resonite has networking infrastructure around the world.</translate>


== <translate>Network Nodes</translate> ==
== <translate><!--T:2--> Network Nodes</translate> ==
<translate>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.</translate>
<translate><!--T:3--> 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.</translate>


<translate>We have these in:</translate>
<translate><!--T:4--> We have these in:</translate>
* <translate>Australia</translate>
* <translate><!--T:5--> Australia</translate>
* <translate>Japan</translate>
* <translate><!--T:6--> Japan</translate>
* <translate>Finland</translate>
* <translate><!--T:7--> Finland</translate>
* <translate>US West Coast</translate>
* <translate><!--T:8--> US West Coast</translate>


== <translate>Azure Managed Infrastructure</translate> ==
== <translate><!--T:9--> Azure Managed Infrastructure</translate> ==
<translate>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:</translate>
<translate><!--T:10--> 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:</translate>
* <translate>Azure Cosmos DB</translate>
* <translate><!--T:11--> Azure Cosmos DB</translate>
* <translate>Azure VMs</translate>
* <translate><!--T:12--> Azure VMs</translate>
* <translate>Azure Table Storage</translate>
* <translate><!--T:13--> Azure Table Storage</translate>
* <translate>Azure API Service</translate>
* <translate><!--T:14--> Azure API Service</translate>
* <translate>Azure Redis</translate>
* <translate><!--T:15--> Azure Redis</translate>
* <translate>Azure Signal R</translate>
* <translate><!--T:16--> Azure Signal R</translate>


== <translate>Miscellaneous Systems</translate> ==
== <translate><!--T:17--> Miscellaneous Systems</translate> ==
<translate>Some systems run on more traditional infrastructure for things like:</translate>
<translate><!--T:18--> Some systems run on more traditional infrastructure for things like:</translate>
* <translate>Email</translate>
* <translate><!--T:19--> Email</translate>
* <translate>Support & Moderation Desk</translate>
* <translate><!--T:20--> Support & Moderation Desk</translate>
* [[Asset Variant System|<translate>Asset Variant System workers</translate>]]
* [[Asset Variant System|<translate><!--T:21--> Asset Variant System workers</translate>]]


== <translate>Infrastructure Help</translate> ==
== <translate><!--T:22--> Infrastructure Help</translate> ==
<translate>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:</translate>
<translate><!--T:23--> 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:</translate>
* <translate>Additional Servers</translate>
* <translate><!--T:24--> Additional Servers</translate>
* <translate>Additional Asset Variant Workers</translate>
* <translate><!--T:25--> Additional Asset Variant Workers</translate>
* <translate>Additional Networking Nodes</translate>
* <translate><!--T:26--> Additional Networking Nodes</translate>
* <translate>Infrastructure/Site Reliability Staff</translate>
* <translate><!--T:27--> Infrastructure/Site Reliability Staff</translate>


<translate>If you're experiencing issues that you think may be due to Infrastructure related matters, please follow our regular [https://github.com/Yellow-Dog-Man/Resonite-Issues bug reporting] process.</translate>
<translate><!--T:28--> If you're experiencing issues that you think may be due to Infrastructure related matters, please follow our regular [https://github.com/Yellow-Dog-Man/Resonite-Issues bug reporting] process.</translate>

Latest revision as of 12:20, 3 March 2024

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.