PUBLIC MARKS with tags rails & architecture

Trailblazer gives you a high-level architecture for web applications. Logic that used to get violently pressed into MVC is restructured and decoupled from the Rails framework. New abstraction layers like operations, form objects, authorization policies, data twins and view models guide you towards a better architecture. By applying encapsulation and good OOP, Trailblazer maximizes reusability of components, gives you a more intuitive structure for growing applications and adds conventions and best practices on top of Rails' primitive MVC stack. A polymorphic architecture sitting between controller and persistence is designed to handle many different contexts and helps to minimize code to handle various user roles and edge cases.

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.

Good application design is hard and there’s no one “right” way to do it. I often get asked the how I design decoupled applications and while there’s no easy answer I’m going to lay down the rules that have worked for me.

Voici quelques pistes qui seront particulièrement utiles à ceux qui développent une application dans un environnement LAMP (Linux, Apache, Php et MySql) ou RoR (Ruby On Rails). Il s’agit en fait des retours d’expérience de sites comme Flickr, Digg