Hacker News Reader

This article suggest that MVC implies a fat server, and that using newer patterns with thin servers breaks away from MVC.

Using a thin server with a Javascript heavy app basically means keeping the Model/Controller on the server, then having Views/Controllers on the client.

So in the end, you're still with a MVC pattern, you just spread your Controller over two machines with RPC in between.

View on HN

To me a controller is just another thin client and models provide an (internal) API. What breaks this and leads to fat clunking controllers is ActiveRecord and 'model as table row' mindset (particularly when a model doesn't handle collections).

The missing part here is turning that API into an external one, which requires a layer in any case to cover things like authorisation, caching, queuing, reporting, QoS, orchestration.

Reply on news.ycombinator.com