Today my newest book: "Scaling your Node.js apps" is officially out and ready to be obtained, both in digital and print versions, so I wanted to leave a few words about what this book will do for you in case your interest has been picked:
One thing to note first, is that this book is intended for both, novice and experienced audiences. The ones that have not had the actual experience of having to go through the growing pains of a scaling application will be the ones that make the most out of the book, of course. But if you've been there, and you've done that, you might still get a few tidbits of information and details on how the big companies are handling scaling to the absurd levels they need to go (I'm referring to Netflix and PayPal for example).
Other than that, this book is not heavy on the code, since scaling is more about working with the right architecture rather than writing the right line of code, so I'll be taking you through a journey that starts at the most basic concept: scaling. I'll define it for you, and I'll show you in how many ways you can actually scale.
Then, I'll move on to explaining when you should start considering scaling and when not to worry about it. This is important, because just like I hate premature optimization of code, I hate over-engineering architectures just so they can scale from day one, when no one is using the app. I'll show you what to look for in a architecture in order to ensure growth in the future, and save some time in the present.
Finally, once you've scaled up, I'll even cover a few problems that arise when scaling, since such practices need to be done carefully, otherwise you're doing more harm than good. But that's what I'm here for and the book will help you work around those pitfalls. Here I'll be covering some generic problems and some Node.js specific ones, so expect to see some code!
In the end, I'll cover some good practices when it comes to testing your Node.js applications, which might sound a bit weird, since we've been discussing Scaling architecture, but I consider that quality of code is required for a proper scaling platform. So I've dedicated a whole chapter to talk about the best ways to test your platform, what it means to do so and how to approach it.
The last thing I'll cover, is a list of success cases form some of the industry giants, such as Netflix, PayPal, Uber and others. They had to jump through some really nasty hoops when they saw the need to scale, and solve them in very interesting ways. So the final chapter of the book will cover their success stories, showing you that you're not alone in this journey.
So, if you're interested in this subject, even if you're not big on Node.js, the book will be a great read to help you get up to date and increase your architectural game, give it a shot!