Using Mobx as server-side state management.

[skid]

Hi, I have a question.

It's hard to find anything online about using mobx on the server, apart from server side rendering. I'm thinking of using a mobx model on a Node.JS backend as a long-lived object that manages a state shared between several users. If anyone can think of reasons why this is a good/bad idea, I'd appreciate hearing it. Also, pointers to online resources, which are not about SSR are welcome.

[mweststrate]

MobX is a generic library, unrelated to the runtime environment. So like with libraries like lodash, RxJS etc, you won't find real pointers on the frontend versus backend, because it doesn't matter to MobX. Only mobx-react is frontend, or rather, React, specific. So if you want to use MobX on the backend, that is perfectly fine, assuming that meaningful side effects are possible. (Such as pushing messages through a websocket to the relevant users). But probably that is the case, given that you need some shared state.

…

On Tue, Mar 5, 2019 at 4:58 PM Dusko Jordanovski ***@***.***> wrote: Hi, I have a question. It's hard to find anything online about using mobx on the server, apart from server side rendering. I'm thinking of using a mobx model on a Node.JS backend as a long-lived object that manages a state shared between several users. If anyone can think of reasons why this is a good/bad idea, I'd appreciate hearing it. Also, pointers to online resources, which are note about SSR are welcome. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1922>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABvGhAzplu4CDJDsKq21OqBNxcqqCpLnks5vTpQMgaJpZM4be7Js> .

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or questions.