Table of Contents for
Scaling Your Node.js Apps: Progress Your Personal Projects to Production-Ready

Version ebook / Retour

Cover image for bash Cookbook, 2nd Edition Scaling Your Node.js Apps: Progress Your Personal Projects to Production-Ready by Fernando Doglio Published by Apress, 2018
  1. Navigation
  2. Cover
  3. Front Matter
  4. 1. The Need to Scale
  5. 2. Architectural Patterns
  6. 3. Ways to Scale
  7. 4. Challenges when Scaling
  8. 5. When to Scale?
  9. 6. Testing Your Application
  10. 7. Success Cases
  11. Back Matter
Fernando Doglio
Scaling Your Node.js AppsProgress Your Personal Projects to Production-Ready
Fernando Doglio
La Paz, Canelones, Uruguay
ISBN 978-1-4842-3990-2e-ISBN 978-1-4842-3991-9
https://doi.org/10.1007/978-1-4842-3991-9
Library of Congress Control Number: 2018964431
© Fernando Doglio 2018
This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed.
Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights.
While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein.
Distributed to the book trade worldwide by Springer Science+Business Media New York, 233 Spring Street, 6th Floor, New York, NY 10013. Phone 1-800-SPRINGER, fax (201) 348-4505, e-mail orders-ny@springer-sbm.com, or visit www.springeronline.com. Apress Media, LLC is a California LLC and the sole member (owner) is Springer Science + Business Media Finance Inc (SSBM Finance Inc). SSBM Finance Inc is a Delaware corporation.

To my wife, who’s been an amazing rock throughout this entire process: You make me a better person.

To my kids: you managed to fill a place in my heart I didn’t know I had empty. I love you.

Introduction

Any piece of software that either deals with an increasing amount of data or interacts with the public on a world-wide capacity will eventually (if the creators play their cards right) grow out of control.

This situation can get out of hand quickly if you’re not expecting it, after all, it’s plays a major role in crashing your favorite websites everyday. The key aspect here, is to understand why they happen and the kind of tools you have a your disposal to solve them once they do. By getting that part right, you’ll be ready to understand the signs and know how to react to them. And that is what this book attempts to answer.

Throughout this book, with the help of plenty of diagrams and, in some weird occasion, a few code samples, I’m going to provide you with the what, the where, the when, the who, and the “uh?” about scaling large platforms, while working with Node.js.

Acknowledgments

I’d like to thank the amazing technical reviewer involved in the project, Shane Hudson, whose great feedback was a crucial contribution to the making of this book.

I’d also like to thank the rest of the Apress editorial team, whose guidance helped me through the process of writing this book.

Table of Contents

Chapter 1:​ The Need to Scale 1
External Factors 1
Traffic Increase 1
Increased Processing Power Required 4
Internal Factors 6
High Availability 7
Fault Tolerance 11
Summary 18
Chapter 2:​ Architectural Patterns 19
The Patterns 19
Layered Architecture 20
MVC Is Not Layered 22
Client-Server 25
Master-Slave 27
Event-Bus or Event-Driven Architectures 29
Microservices Architecture 32
The Broker Pattern 34
Lambda Architectures 37
Summary 40
Chapter 3:​ Ways to Scale 41
Scaling Techniques 41
Vertical or Horizontal Scaling?​ 41
Taking Advantage of the Cloud 44
Clustering Your Application 47
Clustering with PM2 55
In Conclusion 57
Microservices to the Rescue 57
In Conclusion 60
Summary 61
Chapter 4:​ Challenges when Scaling 63
Dealing with Your Log Files 63
You’re Just Logging into stdout and stderr 65
You’re Logging into a Single File 69
Sharing Memory between Processes 73
Single Points of Failure?​ No Thank You! 76
Stateful Apps and Multi-Server Scenarios 82
Summary 86
Chapter 5:​ When to Scale?​ 87
Monitoring 87
Alerting 89
Monitoring Your Apps 91
Adding AWS Metrics into Your Dashboard 103
Reacting to Your Metrics 104
Summary 109
Chapter 6:​ Testing Your Application 111
Testing 101 111
The Definition 112
The Tools 115
Best Practices 123
Testing with Node.​js 125
Testing without External Modules 125
Mocha 128
Testing Asynchronous Code 130
Integration Testing 137
Testing Approaches 138
Summary 141
Chapter 7:​ Success Cases 143
PayPal 143
Uber 146
LinkedIn 148
Biggest Challenges 150
Netflix 151
Summary 155
Index 157

About the Author and About the Technical Reviewer

About the Author

Fernando Doglio
../images/464896_1_En_BookFrontmatter_Figb_HTML.jpg

has worked as a developer for the past 13 years. In that time, he has come to love the Web, and has had the opportunity to work with most leading technologies, such as PHP, Ruby on Rails, MySQL, Node.js, Angular.js, AJAX, REST APIs, and others. For the past four years Fernando has also been working as a Technical Manager and Technical Lead for Big Data projects.

In his spare time, Fernando likes to tinker, learn new things, and write technical articles and books such as this one. He’s also a big open source supporter, always trying to bring new people into it. When not programming, he can be seen spending time with his family.

Fernando can be contacted on Twitter @deleteman123 or online at www.fernandodoglio.com .

 

About the Technical Reviewer

Shane Hudson
../images/464896_1_En_BookFrontmatter_Figc_HTML.jpg

is a freelance web developer and author of JavaScript Creativity (Apress, 2014). From small proof of concept prototypes to large startups, charities and government organizations, Shane has worked on all kinds of projects and with all kinds of teams around the world. He can be found on his personal site at https://shanehudson.net or on Twitter at https://twitter.com/ShaneHudson .