On 11 Sep 2008, at 16:52, Diego Bernardes wrote:
> > Hi guys :) > > I have a question, i have a big program to code, its a issue > tracking + > time tracking + alot of others tracking that my client needs, the > question: > > - make a big rails application > - split the application into smaller applications with the same > database > - split the application and the database > > The client want to offer the full app (issue, time,...) and want to > offer separated parts of the program too like the issue tracking, time > tracking,... > The data from modules are very integrated, ex, in a issue, i need know > the time spent on it and know the files attached to it, 3 diff apps > here. Personally I prefer small applications with separate databases. Easier to maintain, easier to scale one part of the app without doing the same to others etc... Exactly how practical that is can depend on the degree of interapplication communication you need. Things like ActiveMessaging or just an internal API which the apps use to request data off each other can be useful Fred --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
