I think architecture is just a lot more important, especially when building larger systems. Lots of smaller, testable black boxes with well-defined interfaces. This lets you scale easier, experiment with different data stores/languages/frameworks for different problem domains, etc. However, in our recent experience building a Rails app for a new start-up, as much as we wanted to use a SoA style from the beginning, we just didnt know enough about the app. It was easier to prototype/sketch out the app as a standard monolithic Rails app, and then once the natural fault lines started to emerge, extract out functionality into a service. Rinse, and repeat.
Regards, John Lynch [email protected] On Wed, Nov 30, 2011 at 10:50 AM, Chris McCann <[email protected]>wrote: > An interesting post about where Rails fits in with the current web- > enabled application landscape. > > http://broadcastingadam.com/2011/11/moving_on_from_rails > > Thoughts? > > Chris > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
