Node is one part of a larger puzzle. Whether you’re using the full Mongo / Express / Angular / Node (MEAN) stack or not, understanding how those pieces fit together will make it easier to see how Node fits in applications.
To get started with Node development, you need to define an initial Node application supporting basic functionality.
Your Node applications won’t be one giant block of code: you’ll construct your programs out of modules, both the ones you create and the ones you link from elsewhere. Get started with this basic component of program logic.
Node shuns synchronous connections, driving developers to work in a model where they make requests and then wait for an answer. Callbacks are the core Node construct enabling this.
You can write Node applications where you control every detail of the routing in your own code, but it’s much easier to get started by letting the Express framework handle that.
Sometimes you’re writing apps for the ages. Other times you need to create something quick. Node lets you do both, and is especially useful when you need to prototype something new.
WebSockets give you longer-lasting and lighter-weight connections than HTTP. Learn how to set them up quickly in Node.
All these callbacks, all these modules – it’s a lot to track before you put an application in production. Debugging tools can help you through the maze.
Your Node application works great locally, but you want it to reach a crowd. Fortunately, deploying Node applications to Amazon Web Services isn’t too big a challenge.
Deploying ever-changing applications can be a recipe for madness. Fortunately Docker’s containerization model can simplify your deployment challenges and reduce the number of things you need to change repeatedly.