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