Context Propagation in LoopBack

LoopBack developers often need to propagate information (aka “context”) from the HTTP layer all the way down to data source connectors. We hear this regularly in the LoopBack discussion forums and GitHub issues.

Consider the following examples:

  • When querying a database for a list of “todo” items, return only the items owned by the currently logged-in user.
  • When making a REST or SOAP request to a backend service, include a transaction/correlation ID from the incoming HTTP request headers in the outgoing HTTP request headers, so that these two requests can be linked together by logging and tracing tools.
  • When formatting an error message, translate it to the language understood by the user, as indicated by the HTTP request header “Accept-Language”.

These examples share a common pattern: the app needs to access information in the layer handling incoming HTTP requests, but it is not included in the arguments (parameters) of remote method APIs.
Read more

Webinar: Customizing Loopback – Integrating More Modules

We have a new webinar coming up on Tuesday, February 21st – how to customize LoopBack by integrating more modules!

LoopBack is a fantastic tool for generating a RESTful web API, and to have it up and running in no time. We’ll spend some time showing you how to take what’s generated, and step through a couple of real-life scenarios that allow you to expand your server with other Node.js modules.
Read more

Strong-soap LoopBack module

After years of work in with Java and Java EE7 technologies, I recently transitioned to IBM’s Strongloop team to work with the latest new technologies – Node.js. Making the transition from Java to Node.js has been an interesting journey, more about that in a blog someday. In the meanwhile, here is my first bit of work with Node.js, a new open-source module called strong-soap, which is part of the LoopBack 3.0 release. This module provides a comprehensive SOAP client for invoking web services. It also provides a mock-up SOAP server capability to create and test your web service. However, you can use strong-soap with Loopback 2.x as well.

Read more

Announcing the LoopBack CLI!

Three years ago we released slc, a veritable swiss-army knife for building and managing Node applications. The slc command-line interface (CLI) also included commands for scaffolding  and modifying LoopBack apps.

Over the last year, as part of the Strongloop-IBM journey, we’ve integrated the API creation aspects of LoopBack with the API management aspects of IBM’s existing solutions. With that, we’ve made progress on extending the Loopback roadmap.  As part of this path, we’ve now given LoopBack its very own CLI.
Read more

Announcing LoopBack 3.0 GA

Today we are excited to announce availability of LoopBack 3.0 for general availability.

It has been a long ride since the last major release of LoopBack (version 2.0), announced more than two years ago. In that time, we have added over 90 new features, StrongLoop was acquired by IBM, the LoopBack team grew by 10 more developers, and we opened the documentation to your contributions.

Before we move to the list of new features, let me clarify a last-minute change in supported Node.js versions and our plans for the LoopBack version line 2.x. Read more