Skip to content
This repository has been archived by the owner on Oct 26, 2019. It is now read-only.

Figure out core/api-v1 separation #3

Closed
goto-bus-stop opened this issue Jan 13, 2016 · 1 comment
Closed

Figure out core/api-v1 separation #3

goto-bus-stop opened this issue Jan 13, 2016 · 1 comment

Comments

@goto-bus-stop
Copy link
Member

Currently api-v1 contains all of the things, and it's very tightly coupled with core. There should be a meaningful separation between the two so other plugins/interfaces/ can be added by server hosts easily, while keeping everything in sync.

Ideally we'd want some multiprocess support so we can have like millions of people online and do 0-downtime server upgrades (I mean, I assume that's how it works! not an expert. But we need to be able to do that, anyway.) in the long term.

Idea:
https://docs.google.com/drawings/d/1xq_F4mUoF0gsE_q5LW26fA2pElgTBf2zOKKkQaKq6AU/view

@fawaf
Copy link
Member

fawaf commented Sep 7, 2017

why did you close this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants