@yggie What I'm trying to aim here is to have a top level namespace that implies a use case or a related set of use cases; yes ```Events``` implies a direct relationship with the ```Event``` model but that was intentional, now we will know where to look for most use cases inside the service layer related to a particular model or a set of model. Probably it would be more appropiate to have a directory structure like this ```app/websiteone/<use_case_name_space>/<service_object>``` or even inside ```lib``` if we would like to extract the entire business logic from the Rails app we won't have a lot of files flying around. ```Creator``` won't become a generic creator service it will just create events in this context. 

Check out this blog post and comment thread to see what's my intention with all of this:  http://devblog.reverb.com/post/70344683203/5-architecture-anti-patterns-and-solutions-for-large
please keep throwing feedback. Thanks