node.js - Best way to separate logic in sailsjs (nodejs) -

There are some parts in my application structure: I (Oeth 2, local, socialists), etc. They differentiate slightly but use the same model. Some routes are number of high requests per second and can not be cached.

I am interested in best practices to divide everything properly, I have also opened for any other frameworks or even Io.js.

Right now I've got 3 variants:

1. Create a separate app.
2. Find the way to the control of group folders, and group routes.
3. Make another example of the seal app and run it in another process (so I can have all the controllers, models, but how can I organize the subpicture structure by using it? I think most of the responses will be opinions, but putting sub controllers in subfolders. The easiest way to share models (easiest but not only)

   and You can easily run policies based on those subfolders.

   However, you really need to take out more aspects of your question and think about whether it will be shared differently. (Such as templates or assets) or if the differences will restrict a shared app, will they use all sessions or they will use the same session.

   Finally, depending on your limited question, you can do the sail you want.