Storage

[nicolodavis]

Games are currently held in an in-memory object, but should be persisted in either a MongoDB or Firebase instance. Options for other backends should also be possible.

TODO:

• Mongo support
• Firebase support
• Postgres support

[w74]

Do we have a server for this already? Furthermore, we should consider creating a "library" of games people have made.

[nicolodavis]

All the server code lives in src/server. Games aren't persisted yet, but I plan to add support for various backends.

[nicolodavis]

I'll link to any games people make on the main README page once that happens. We haven't reached 1.0 yet so I would imagine that people will start using this more widely once the API is stable.

[saeidalidadi]

I think writing a connector class for the reducer would be a better idea, so people could add their own odm or orms.

[nicolodavis]

Yes, this is the idea I had too, to make it extensible so that we're not limited to just the backends that come supported out of the box.

[saeidalidadi]

If you have the usage signature or api of the connector I will be happy to write the tests of that requirements.

[nicolodavis]

I was just thinking of adding a DB section to the server constructor:

Server({
  game: ...
  db: {
    // optional initialization code
    init: function() { ... }

    // called whenever a Redux action is received by the server
    onAction: function(gamestate) { ... } 
  }
})

Provided connectors can be used like:

import { Mongo } from './db/mongo';

Server({
  game: ...
  db: Mongo(uri: "..."),
})

We could probably first just wrap the existing in-memory object into this signature and build up from there.

[saeidalidadi]

There is a use case which data could be on multiple stores like redis or mongo. does this solution works for that case?
I think for now this case could be ignored but I think using generators and calling them in a loop like that koa is doing would be a good idea to work with persist stores.

[nicolodavis]

Let's make db an array then:

db: [
  {onAction: }, {onAction: }, ...
]

where the onAction handlers are called in the order they are defined.

[saeidalidadi]

This is cool and has more benefits

[saeidalidadi]

Is it possible to use redux-saga middleware?

[nicolodavis]

We could definitely look into redux-saga, but I would prefer to start simple and only use it if necessary.

I've created a simple interface for storage with just get and set. We can add support for something like Mongo or Redis to start.