[Pharo-dev] [ANN] Mapless a small framework for storing objects in a key->data fashion with no friction

phil at highoctane.be phil at highoctane.be
Thu Apr 17 02:57:04 EDT 2014


On Thu, Apr 17, 2014 at 1:46 AM, François Stephany <
tulipe.moutarde at gmail.com> wrote:

> Phil, can you describe your use case ?!
>
>
Network of objects persistence.



>
> On Wed, Apr 16, 2014 at 11:20 PM, phil at highoctane.be <phil at 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 at 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
>>> 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/
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20140417/5d00e5c2/attachment-0002.html>


More information about the Pharo-dev mailing list