[ANN] Mapless a small framework for storing objects in a key->data fashion with no friction
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/
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 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/
Phil, can you describe your use case ?! 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 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/
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 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/
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/
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. 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/
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/
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:phil@highoctane.be | 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 < 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 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/
Here: http://sebastianconcept.github.io/Mapless sebastian o/
On 03/05/2014, at 14:05, "phil@highoctane.be" <phil@highoctane.be> 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:phil@highoctane.be | 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 <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/
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 <sebastian@flowingconcept.com> wrote:
Here:
http://sebastianconcept.github.io/Mapless
sebastian
o/
On 03/05/2014, at 14:05, "phil@highoctane.be" <phil@highoctane.be> 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:phil@highoctane.be | 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 <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/
On May 3, 2014, at 4:42 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
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.
Thanks Sven! Iâve updated it today adding a FAQ section: Frequently Asked Questions What saving 'Models' means? why not any object? By Models Mapless means that you are not pretending to save transient stuff like contexts or sockets or filehandlers, etc. Any instance of a MongoMapless subclass will save in a breeze. Those instances are going to be serialized and stored as documents of its correspondant MongoDB collection. Is only for tree-like structures or does actually support an object graph? Given that you follow its rules,like saving children first and thinking your models as noSQL friendly documents, yes, it does support an arbitrary object graph. Why would I want to use Mapless? Because you might want to profit from some of these benefits: JSON friendly models Having 1:1 interoperability of your models with Ruby and NodeJS and any JSON friendly object oriented app Dealing with Gigas or Teras order of magnitude databases High availability Easy replication of the whole database across the cloud Databases many people is familiar to use and maintain Powerful queries and custom indices Freedom from a prioristic instVars declarations Freedom from mappings maintenance when the design changes Trans-image model caching (requires Redis) Trans-image model observation/reaction, horizontally scalling the Observer Pattern (requires Redis) Friendly to mobile noSQL database use and sync (requires CouchDB) All that with very low-friction and low-maintenance using one simple API
participants (5)
-
François Stephany -
Norbert Hartl -
phil＠highoctane.be -
Sebastian Sastre -
Sven Van Caekenberghe