Framework: Strongloop’s Loopback


Recently I did a series for New Relic on three frameworks, both for APIs and web apps. I titled it “Evaluating Node.js Frameworks: hapi.js, Restify, and Geddy” and it is available via the New Relic Blog. To check out those frameworks give that blog entry a read, then below I’ve added one more framework to the list, Strongloop’s Loopback.

Strength: Very feature-rich generation of models, data structures and related enterprise-type needs. Solid enterprise-style API framework library.
Weakness: Complexity could be cumbersome unless it is needed. Not an immediate first choice for a startup going after lean and clean.
Great for: Enterprise API Services.

When I dove into StrongLoop, I immediately got the feel that I was using a fairly polished package of software. When installing with ‘sudo npm install -g strongloop’ I could easily see the other packages that are installed. But instead of the normal Node.js display of additional dependencies that are installed, the StrongLoop install displayed a number of additional options with a shiny ASCII logo.

StrongLoop's ASCII art begins.
StrongLoop’s ASCII art begins.

Once the library was installed, I took it for a test drive. The loopback library builds a basic API service with a simple command of ‘yo loopback’.

More ASCII Art!!!!
More ASCII Art!!!!

To build an initial model in the API service, simply run ‘yo loopback:model WidgetStuff’. From here I dove into what was being generated.

Taking a look at the JSON for WidgetStuff, the default generation looks like the code below.

[sourcecode language=”javascript”]
"name": "WidgetStuff",
"base": "PersistedModel",
"properties": {},
"validations": [],
"relations": {},
"acls": [],
"methods": []

In the JSON, the library has done a good job of leaving hooks for validations, relations, ACLs (Access Control Lists) that all point to an enterprise-grade product.

Moving along to other parts of the standard generated application, I took a look at the server.js file. In that file the code is simple, with comments to explain where to integrate other elements of the application. By default there are other parts of the application that are already in place with a basic minimal functionality. The code file starts off with the basic code as shown.

[sourcecode language=”javascript”]
var loopback = require(‘loopback’);
var boot = require(‘loopback-boot’);

var app = module.exports = loopback();

// Set up the /favicon.ico

// request pre-processing middleware

// — Add your pre-processing middleware here —

// boot scripts mount components like REST API
boot(app, __dirname);

// — Mount static files here–
// All static middleware should be registered at the end, as all requests
// passing the static middleware are hitting the file system
// Example:
// app.use(loopback.static(path.resolve(__dirname’, ‘../client’)));

// Requests that get this far won’t be handled
// by any middleware. Convert them into a 404 error
// that will be handled later down the chain.

// The ultimate error handler.

It’s good to see a starting code base that already has compression, basic error handler, not found handler and related functionality. Toward the end of the file there is the startup code.

[sourcecode language=”javascript”]
app.start = function() {
// start the web server
return app.listen(function() {
console.log(‘Web server listening at: %s’, app.get(‘url’));

// start the server if `$ node server.js`
if (require.main === module) {

This code from start to finish is pretty clean. And with basic functionality for API services already represented, I can start building a working application right from the start.

I found StrongLoop’s Loopback product to be a great starting point to build APIs off of with minimal ties to dependencies. Plus, the user interface provides an excellent way to interact with the generated API endpoints. In short, StrongLoop offers one of the best API-building experiences available on the Node.js platform. This will give you a better idea of what I’m talking about:

The first user interface screen that displays upon navigating to the explorer end point i shown here.

The LoopBack API web user interface. Very Enterprisey.
The LoopBack API web user interface. Very Enterprisey.

A number of endpoints for the WidgetStuffs model that I generated are now available. To interact with the actual endpoint itself, simply click on one to list or expand the operations.

UI Expanded.
UI Expanded.

The real time saver? Having the ability to check out the explorer interface and immediately send data to the APIs without typing in cryptic curl commands.

My Sample Loopback Project:

8 thoughts on “Framework: Strongloop’s Loopback

  1. I’ve looked into Loopback for an upcoming project, and although it does seem good for simple/standard response API’s, its a bit of a do it all easy solution which, upon inspection is not very flexible. I’d much rather spend a bit of time coding up my routes and responses so that I know whats going on and be able to change things easily.

    1. I feel the same way. All these frameworks look very sexy in demos until you start working on a real project. Then you are hit with their constrains that quickly become your constraints.

      1. I am going through the strongloop solution, it doesnt seems constrained. Its quite flexible as its based on express.js. Its now quite modular as well like API gateway, connector and strongops etc.

Comments are closed.