Two of your images have broken links. Is that intentional?

Probably Adrian would like to fix the images links ?

thanks, I added back the missing images.

Yes, please can we see the diagrams for Figure 3 and Figure 4. Thanks :-)

I fixed it

What Rails is not suitable for: "Very large-scale web applications (millions of concurrent users) that need to deliver high-performance."

That's not true. Rails is very scalable. We have a large Rails application that relies on multiple servers because of the high traffic and it's very easy to scale it. Nowadays, scaling horizontally costs almost nothing, relatively.

Very good article for understanding rails core components and its architecture.

Actually Action View is not a part of ActionPack.
https://github.com/rails/ra...

It's separate gem
https://github.com/rails/ra...

Yes, it just happened recently that it go into its own gem

That was indeed super worthy.

> The Model centralizes the business logic

This is very bad idea and common mistake. Model should only represent data. I would say it's much better to move business logic apart from both models and controllers. For example check rails_workflow gem ( http://github.com/madzhuga/... ) - it allows to configure processes containing operations and split business logic in separate layer. Also please notice that it allows not just build processes (which is only part of it) but also to trace and manage processes, checking those which fails, restart them etc. Business logic should be not just set of 'service' classes or callback.

This article is really worth to read.. Thanks

Nice explanation about the ROR architectural design.. thanks

Good article but somehow not correct. Rails pretends to be MVC but is only MVP. I would correct that in the article because the difference is significant. Google for it.

You are the best!!!! Regards from Uruguay!!!!

Awesome and concise overview, thank you!

Thanks for this wonderful explanation,Please keep up the good work.