Wow, excellent site, very well done ! It is like we are having a competition in quality of presentation, marketing and documentation, cool. Things like this are really pushing the status quo forward.
On 03 May 2014, at 21:05, Sebastian Sastre <[email protected]> wrote: > Here: > > http://sebastianconcept.github.io/Mapless > > sebastian > > o/ > > On 03/05/2014, at 14:05, "[email protected]" <[email protected]> wrote: > >> What is the URL of the cool mapless site? >> >> --- >> Philippe Back >> Visible Performance Improvements >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 >> Mail:[email protected] | Web: http://philippeback.eu >> Blog: http://philippeback.be | Twitter: @philippeback >> Youtube: http://www.youtube.com/user/philippeback/videos >> >> High Octane SPRL >> rue cour Boisacq 101 | 1301 Bierges | Belgium >> >> Pharo Consortium Member - http://consortium.pharo.org/ >> Featured on the Software Process and Measurement Cast - >> http://spamcast.libsyn.com >> Sparx Systems Enterprise Architect and Ability Engineering EADocX Value >> Added Reseller >> >> >> >> >> 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 >> 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: >> >> https://github.com/sebastianconcept/Mapless >> >> All MIT, enjoy >> >> sebastian >> >> o/ >> >> >> >> >> >>
