Am 17.04.2014 um 10:08 schrieb phil@highoctane.be:
Not magically.
I have my own guide/visitor thing to do the save. But as I do have a "complicated" domain, the fact that I do not have to maintain all attributes in the image but directly through mapless helps me save a ton of time.
Can you elaborate on the point ânot to have to maintain all attributes in the imageâ? I donât get what it means. And if you know voyage can share with us what are the differences? thanks, Norbert
Phil
On Thu, Apr 17, 2014 at 10:03 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote: But how does a key/value store magically store a network of objects ? How is each object serialised ?
On 17 Apr 2014, at 08:57, phil@highoctane.be wrote:
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:
https://github.com/sebastianconcept/Mapless
All MIT, enjoy
sebastian
o/