You may be better off using the new engines or merb slices Blog: http://random8.zenunit.com/ Learn rails: http://sensei.zenunit.com/
On 05/02/2009, at 8:06 PM, sbrocher <sbroc...@gmail.com> wrote: > > Hi Julian, > > No worries. I'm just after the basic high-level design concept where > you first break the (large) problem into several subsystems (i.e.: > divide and conquer). Then define APIs for each subsystem. Then > implement each subsystem. Test each system separately. Integrate. Test > whole system. Also known as the "V" model at another level of > abstraction. > > This has many benefits and is a proven technique to design large > systems. It reduces coupling and makes it easier to integrate with > other systems in the future, work with large teams, write more > maintainable code, etc. It also enables you to break down the app onto > different servers in the future as needed, by adding something like > SOAP, REST or XML-RPC in between those APIs. > > For example, if a part of the app deals with inventory management, it > will have it's own API. Then if one day I decide to buy an inventory > management system from a vendor that has its own API and similar > features, all I have to do is write a connector (proxy) and place it > inside my app, replacing the inventory management subsystem > implementation by the proxy that communicates back and forth with the > newly acquired system, but without needing to change any of my > interface code, other business logic code, etc. > > Seb > > On Feb 4, 6:34 pm, Julian Leviston <jul...@coretech.net.au> wrote: >> The reasons you explained you wanted the layer made me think you only >> needed datamapper. Be simpler rather than complex. Explain again why >> you need the layer, please? Remember YAGNI. >> >> Blog:http://random8.zenunit.com/ >> Learn rails:http://sensei.zenunit.com/ >> >> On 05/02/2009, at 5:28 AM, sbrocher <sbroc...@gmail.com> wrote: >> >> >> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
