[{"_1":2,"_52":-5,"_53":-5},"loaderData",{"_3":4,"_14":15,"_50":-5,"_51":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_49":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNjYyNw","title","Growing Rails Applications in Practice","state","published","contactAuthorMethod","email","aboutText","

\n\"Never has a tech book spoken so clearly and in a timely manner to acute pains I've been having at work\" — Ethan Garofolo\n
\n\"Nice to witness a new generation of Rails authors\" — Obie Fernandez\n
#1 bestselling book on Leanpub during launch week!

How we got here

When you started working with Rails some years ago, it all seemed so easy. You saw the blog-in-ten-minutes video. You reproduced the result. ActiveRecord felt great and everything had its place.

Fast forward two years. Your blog is now a full-blown CMS with a hundred models and controllers. Your team has grown to four developers. Every change to the application is a pain. Your code feels like a house of cards.

You turn to the internet for assistance, and find it filled with silver bullets. You should move away from fat controllers, it says. But do avoid fat models. And use DCI. Or CQRS. Or SOA. As you cycle through patterns, your application is becoming a patchwork of different coding techniques. New team members are having a hard time catching up. And you're beginning to question if all those new techniques actually help, or if you're just adding layers of indirection.

You start missing the early days, when everything had seemed so easy and every new piece of code had its place. You actually liked ActiveRecord before it drowned you in a sea of callbacks. If only there was a way to do things \"the Rails way\" without having it fall apart as your application grows.

The myth of the infinitely scalable architecture

We'd like to show you one path to write Rails apps that are a joy to understand and change, even as your team and codebase grows. This book describes a complete toolbox that has served us well for all requirements that we have encountered.

But before we do that, we need to let you in on an inconvenient secret: Large applications are large. The optimal implementation of a large application will always be more complex than the optimal representation of a smaller app. We cannot make this go away. What we can do is to organize a codebase in a way that \"scales logarithmically\". Twice as many models should not mean twice as many problems.

To accomplish this, you don't necessarily need to change the entire way your application is built. You don't necessarily need to introduce revolutionary architectures to your code. You can probably make it with the tools built into Rails, if you use them in a smarter way.

Compare this to sorting algorithms. When a sorting function is too slow, our first thought is not \"install a Hadoop cluster\". Instead we simply look for an algorithm that scales better. In a similar fashion this book is not about revolutionary design patterns or magic gems that make all your problems go away. Instead we will show how to use discipline, consistency and organization to make your application grow more gently.

How we structured this book

We divided the book into three parts:

\n Part I: New rules for Rails \n

In this part we unlearn bad Rails habits and introduce design conventions for controllers and user-facing models. By being consistent in our design decisions we can make it asier to navigate and understand our application even as its codebase grows.

The first part contains the following chapters:

Beautiful controllers
Relearning ActiveRecord
User interactions without a database

\n Part II: Creating a system for growth \n

As we implement more and more requirements, all that code has to go somewhere. If all we do is add more lines to existing classes and methods, we end up with an unmaintainable mess.

In this part we show how to organize code in a way that encourages the creation of new classes which in turn enhances comprehensibility and maintainability. We also lean to contain the side effects that code can have on unrelated parts of our application.

The second part discusses the following topics:

Dealing with fat models
A home for interaction-specific code
Extracting service objects
Organizing large codebases with namespaces
Taming stylesheets

Part III: Building applications to last \n

We show how to think about future maintenance when making decisions today. We make a case for adopting new technologies and patterns with care, and for taking full responsibility for those techniques and technologies that you do choose to adopt.

The last part contains the following chapters:

On following fashions
Surviving the upgrade pace of Rails
Owning your stack
The value of tests

","authors",[30,43],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci82OTA3","name","Henning Koch",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://d308did4coypzi.cloudfront.net/avatars/178206/medium/he.jpeg?1425584503","styleName","medium","exists",true,{"_18":44,"_32":45,"_5":46},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci82OTA4","Thomas Eisenbarth",{"_35":47},{"_37":48,"_39":40,"_41":42},"https://d308did4coypzi.cloudfront.net/avatars/293483/medium/thomas-eisenbarth_beschnitten_smaller.jpeg?1425585663","currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Authors