On Thu, Apr 17, 2014 at 1:46 AM, Fran��ois Stephany <tulipe.moutarde@gmail.com> wrote:
Phil, can you describe your use case ?!


Network of objects persistence.

��

On Wed, Apr 16, 2014 at 11:20 PM, phil@highoctane.be <phil@highoctane.be> wrote:

I worked with Sebastian on using Mapless for my application.

Just one word: Wow. This has potential!!!!

Phil

On Wed, Apr 16, 2014 at 9:17 PM, Sebastian Sastre <sebastian@flowingconcept.com> wrote:

Mapless

Mapless is a small framework for storing objects in a key->data fashion (i.e.: noSQL databases) without requiring any kind of object-data map. So far only MongoDB is supported. It can use Redis for reactivity (pub/sub) and cache.

Motivation

I wanted to persist objects with extremely��low friction��and extremely��low maintenanceand great��scaling��and��availability��capabilities so Mapless is totally biased towards that. This framework is what I came up with after incorporating my experience withAggregate.

There is no spoon���

There is no object-relational impedance���

There is no instVars���

only persistence :D

Code and instructions here:


All MIT, enjoy