Ted Neward recently posted about getting started with LoopBack and API Connect on IBM’s developerWorks blog.  It is the first part of a series in which he plans to “introduce LoopBack, a server-side JavaScript framework that emphasizes building HTTP APIs.” That’s a goal we fully support!

Getting started with LoopBack and API Connect

Ted’s blog covers a lot of ground:

The differences between StrongLoop, LoopBack and API Connect

As Ted explains, “As a newcomer to LoopBack, one of your first challenges will be figuring out what to call the technology you’re using. LoopBack was a standalone entity owned by a company called StrongLoop (which was also the name of its paid service offering), until the company was acquired by IBM® in 2015. Since that time, the LoopBack team released a 3.0 version, and starting with this version it’s consolidating the terms and names under the IBM banner with IBM API Connect™.”

How to install and set up LoopBack

Ted says, “Like most JavaScript-based frameworks, LoopBack is accessible via npm and makes use of a globally installed command-line tool. The first step to getting started with LoopBack, thus, is to open a command-line terminal with Node.js on the PATH, and use npm to install it: npm install -g apiconnect.”

Creating your first LoopBack API

“You can use apic to kick off the server process,” Ted explains, “or you can let npm launch it. Go to the hello directory (the parent to the client, common, and server subdirectories), where the package.json file resides. There, you’ll issue either the apic start or npm start command; either one will fire up the server to start listening for incoming requests.”

LoopBack and API Connect

Finally, Ted runs through how you can move from LoopBack to use API Connect and its dashboard.

While we have given highlights above, the full post gives a mucvh more in-depth look at each of these topics. Get the low-down on all of this here.