Sounds good, thanks! Such an in-memory database seems quite important for productivity, so I will definitely consider this. Read access could be implemented i

Sounds good, thanks! Such an in-memory database seems quite important for productivity, so I will definitely consider this. Read access could be implemented in a first step, while the semantics would still have to be discussed. I think write access would actually be quite important as well so that you can completely abstract away the sending, receiving and processing of events. Latency compensation or optimistic UI would be nice to have (for making applications more snappy), but I think this is only the third most important piece. Maybe one can use "SQLiteOpenHelper" with "name" set to "null" for in-memory storage. Or perhaps some things can be adopted from or based on Minimongo, Realm or MapDB: http://www.quora.com/How-is-Meteors-client-side-database-implemented http://www.quora.com/How-is-Meteors-client-side-database-imp... https://realm.io/ https://realm.io/ https://github.com/jankotek/mapdb https://github.com/jankotek/mapdb