Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Developing an API With Node.js Using Couchbase NoSQL and N1QL [Video]

DZone's Guide to

Developing an API With Node.js Using Couchbase NoSQL and N1QL [Video]

Have you ever wanted to create a RESTful API with Node.js, but weren't sure where to start? Check out this video to learn more.

· Integration Zone
Free Resource

Today’s data climate is fast-paced and it’s not slowing down. Here’s why your current integration solution is not enough. Brought to you in partnership with Liaison Technologies.

Have you ever wanted to create a RESTful API with Node.js, but wasn't sure where to start? How do you design your endpoints or interact with the data layer? How do you store your data?

In this start-to-finish video tutorial, you'll see how to start a new Node.js application, develop four RESTful API endpoints for performing CRUD operations, and use SQL-like N1QL queries to interact with your NoSQL Couchbase data.

By the end of this video, you should be comfortable using Couchbase NoSQL with N1QL as your database for a RESTful Node.js API. While this video is a complete start-to-finish solution, it is part one of two in this series. The next video will accomplish the same, but using an ODM similar to MongoDB's Mongoose instead of N1QL.

Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.

Topics:
api ,integration ,nosql ,n1ql ,node.js ,couchbase

Published at DZone with permission of Nic Raboy, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}