3 ms·
Can you expand on this? Do you mean you'd use Postgres as your main store and periodically "flush" data from CouchDB to Postgres (probably as JSON)? I don't se
by tabeth 9y ago
Can you expand on this? Do you mean you'd use Postgres as your main store and periodically "flush" data from CouchDB to Postgres (probably as JSON)?
I don't see how that would work reliably. On the client would you source CouchDB or Postgres? Presumably you'd access CouchDB directly, but then why even use Postgres (for that subset of data, anyway).
- StavrosK 9y agoIt really depends on what your data looks like. If it's just game settings and state, put them in Couch and that's it, and keep user data like payments and activity there. If it's data you're going to want to run analytics on and sync to the client, you're probably going to have to store it in both places, I think.