Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Mesa server out of API in favour of Mega #94

Open
darnfish opened this issue May 21, 2020 · 0 comments
Open

Migrate Mesa server out of API in favour of Mega #94

darnfish opened this issue May 21, 2020 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@darnfish
Copy link
Contributor

Migrating the Mesa (WebSocket) server from API to a seperate Gateway server, such as Mega would improve performance and remove some off the load from API. With the Mesa Dispatcher API this should be a lot easier to perform and other services like Portals can hook into the pre-existing Mesa server instead of proxying messages to API and then to Mesa.

Also if API goes down briefly during a update then client connections won't be affected and there won't be a sudden surge in load due to authenticating reconnecting clients, which is expensive for the db.

Only issue is it's more to setup for newcomers :/

@darnfish darnfish added enhancement New feature or request good first issue Good for newcomers labels May 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant