search

tengen-io / server

:white_circle: Server implementation of the board game Go
MIT License
13 stars 4 forks source link

Figure out how we want to store live state #48

Open eaceaser opened 5 years ago

eaceaser commented 5 years ago

we need management of online/offline state, and a broker for things like chat.

Not 100% sure yet what the architecture for this should look like. If we want to roll our own thing, most likely this will be some form of internal message bus. I'd suggest we use something like Redis to decouple apiserver from the brokerage of the messages so we can scale both independently?

I don't REALLY feel like rolling our own chat system however. We could look at using google's cloud firestore for the backend for chat, but maybe it can suffice as the real-time message bus as well?

eaceaser commented 5 years ago

Had a discussion at go club last night. Seems like Redis w/ a bit of persistence will get us pretty far.