My reading of this article: Your application may be more than just DB-backed models and REST-based HTTP controllers. Don't be afraid to introduce additional objects to better model your domain.
A services layer sits between your external interfaces (e.g. controllers, and others) and your models. It can reduce duplication of logic among interaces, and support complex interactions involving transactions across multiple models and the coordination of multiple responses. A services layer doesn't belong in /app/models or /app/controllers. You can put in under /lib or even extract it to an external gem (which you configure to access specific models in your application). My response: If your application's only interface is REST controllers and the operations your application provides are simple enough to be encapsulated in individual models, then Rails is your application. Otherwise, do introduce additional structures. I'm interested to hear other's thoughts. Cheers, Chris On Sun, Oct 23, 2011 at 5:33 AM, jamesl <ladd.ja...@gmail.com> wrote: > I found this article insightful and thought others might as well. > http://blog.firsthand.ca/2011/10/rails-is-not-your-application.html > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to rails-oceania@googlegroups.com. > To unsubscribe from this group, send email to > rails-oceania+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-oceania@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
