Node.js API Field Guide: The Dos and Don’ts in Using Node.js to Build APIs
During Node.js Interactive last year, Node.js Foundation members recommended that we build field guides around popular use cases of Node.js. One of the most popular use cases for Node.js is building APIs. We started here.
Why Node.js for APIs?
Node.js is perfect for building APIs. It has a short learning curve, especially for developers with JavaScript experience. You can extend your talent base without adding extra hires since developers can work on both the front and back ends. Node.js works in small tasks, which is fast in any case but also ideal for microservices. It also rests quietly while waiting on data returns, which frees resources so they can be used elsewhere in the interim.
Where’s the Field Guide?
Heard enough and ready to get started? Check out our field guide on building APIs here. This guide explains how to use Node.js to build APIs, and why and where it is appropriate to do so. Several short case studies are also included to further illustrate real-world uses.
Thank you!
Before we close this post, we want to thank the Node.js experts who helped us build this guide: Brian Clark (a cloud developer advocate at Microsoft), James Snell (Open Source Architect at nearForm), and Al Tsang, founder and CEO of LunchBadger. Thank you! We appreciate all the time and work you put into this.
As for you, do you have other suggestions on field guides that would be helpful to you? Please leave a comment and we’ll try our best to accommodate.
