Phil, can you describe your use case ?!
On Wed, Apr 16, 2014 at 11:20 PM, [email protected] <[email protected]>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 < > [email protected]> 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 >> maintenance*and 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<https://github.com/sebastianconcept/Aggregate> >> . >> >> *There is no spoon…* >> >> *There is no object-relational impedance…* >> >> *There is no instVars…* >> only persistence :D >> >> Code and instructions here: >> >> https://github.com/sebastianconcept/Mapless >> >> All MIT, enjoy >> >> sebastian <https://about.me/sebastianconcept> >> >> o/ >> >> >> >> >> >> >
