The approach I take is to have the memory data structures (arrays, hashmaps, etc) in a service all of their own called "Data". This gives me something I can easily dump in the console to see what's going on, is easily fillable with test data, and can be saved/restored to local storage with a single call.
Then I hide that behind another service called DataMethods (or some business equivalent) such that any access to Data must be done via a DataMethod. That allows me to change the implementation detail at will, and also track where any updates are coming from. imho the future is Angular with Meteor,so having an architecture that is easily migratable to Meteor Collections is a win. On Wednesday, 2 December 2015 18:17:51 UTC, Sean Levy wrote: > > I am wondering what model system do you recommend for Angular 2* (i.e.: > like Backbone.Model equivalent)* > Coming from Backbone, I love the simplicity of collections and models and > all the tools around them (underscore tools). > > I am evaluating ng2 and looking for an equivalent in Angular 2? > > thanks for reading, > > Regards, > > Sean - http://DigitalSignage.com > > ____________________________________________ > MediaSignage.com, FREE Digital Signage for everyone! > 5776-D Lindero Cyn Rd #182 > Westlake Village, CA 91362 > Phone: 1.877.DIG.SIGN (1-877-344-7446) > Fax: 1.818.337.0442 > Live support: http://chat.digitalsignage.com > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
