You know how frustrating it is to try to make your Node program do what you want. The code you’ve written has no syntax errors, but running it has strange behavior like:
- Node doesn’t wait for your database call to finish before rendering a page
- you get Cannot read property of undefined when accessing your variable after a call
- your HTTP calls fire at the same time, not after each other like you intended
"...Just think asynchronously!" - But, how exactly?
You’re supposed to “think asynchronously” when programming in Node but it’s not exactly clear how to accomplish this. Examples in tutorials seem reasonable when reading them but translating them into your situation is difficult. You don't know which statement to write next.
Reading n-th Stack Overflow post, but your page still renders with zero results
Trying to find the official word on this leaves you dumbfounded. How come the official docs at nodejs.org have no word on how you’re supposed to program Node? It looks like the real information is scattered across blogs, Github issues and Stack Overflow answers. Going that route takes forever - and you don’t which pieces would be the best use of your time.
What if you could write the app that's in your head
What if you were able to take the vision in your head and turn it into a working and running program. Imagine knowing exactly which statement to write next. You’d be the one in control of your app. You’d write programs that
- finish database calls and only then continue further processing
- have variables filled with values when you need them
- have HTTP calls that run one at a time
You’d be able to express program logic in Node.js. Every statement in your program would have a reason to exist. Time spent working on your app would go to implementing new features.
It’s true asynchronous calls are a little hard to grasp, but it’s possible to make your text editor the place where working programs are written.
You'd know exactly which line to write next
The key to writing working programs is to understand how Node executes your calls. The internals of Node are predictable when you zoom out from the level of individual statements and for-loops. When you look at the system that takes over when you return from a top-level function you’ll start to understand how Node works.
Time spent on your app would go to implementing new features
When you understand what takes place behind the scenes, you're able to get the right mental model how to write Node programs. You'll be able to write programs that work as intended. And that is exactly what you’ll learn in this book.
Book that teaches right mental model for Node apps
When you grab this book, you’ll learn
- the role of a node programmer that is to start operations, register functions and let control back
- the two-fold nature of starting operation in the background and receiving results later
- execution order of calls, when callbacks are run
- how to make things run at the same time or after each other
- making use of waiting time
- care about other computations taking place in your program
The book is written in a concise form that is perfect for busy people who don’t have too much spare time on their hands.
Exercises where you'll learn to make calls run at same time or after each other
Theory alone is not enough if you don’t get to practice your newly learned skills. You’ll write five programs as exercise assignments. You get to build a news aggregator and a Twitter bot, call weather APIs and calculate cryptographic hash functions.