Regardless that the technology is Rails and Postgres -centric, the text is solid about proper enterprise architecture. Specifically, presenting services as layers of small, loosely coupled plugins.

High Pockets "HP": Amazon Reviewer

My edition was written in 2008, and lots of things in Rails have moved on since then. However, this book is still a great read for the many other aspects that are rarely addressed in rails tutorials. Dan has a good writing style and clear experience in a real business.

I smiled, learned and even laughed as I read his comments on the data layer and the need to use protection wherever possible. His way of testing data exceptions and validations seemed neater than anything else I have ever seen.

David Verrier: Amazon Reviewer

I just finished Enterprise Rails and want to tell you what a capital, outstanding, helpful book it is. I was sad when I finished it!

I've been building a startup site of moderate size, not even something you'd call enterprise yet, for the last 3 years. When I started I was just the sort of naive and overconfident Rails guy this book is aimed at. The author has been through all the scaling issues involved with running a popular website and the book is chock full of useful advice and examples. I wish I had read it way back when I started as I have made many of the mistakes he warns about and had to learn the hard way. Dan shows you how to avoid painting yourself in a corner with overly optimistic/naive design choices up front. He shows you how to design things properly from the start, with a special emphasis on using the native features of a relational database instead of doing things at the application level, and how to keep things organized. I love love LOVED this book.

M. Subelsky: Amazon Reviewer

Required reading for any rails developer. The author provides an important perspective that can easily be forgotten in the rails community. You may not put into practice everything you find in the book but it is an invaluable, intelligent description of design strategies that need to be re-aquired in the rails community if it wants to survive beyond "this is a really cool language!" ;)

Tom: Amazon Reviewer