PUBLIC MARKS from Spone with tags "design pattern" & rails

I've spent some time thinking about how a web application should be architected. How should it look from a high level? How does the development cycle look? How does the deployment process look? I read a lot about how applications should be modular, and I agree with this, but in practice I've come to realize I don't know how a large application should look.

While Rails may be the perfect tool for building an MVP, it isn’t optimised for medium and large codebases. We’re solving these problems with 3 concepts we believe should be part of any “Advanced” Rails deployment; Interactors, Policies and Presenters.