Webinar: LoopBack, MongoDB, and Continuous Integration

Considering using LoopBack to create an API for your data in MongoDB? Then mark your calendars! We have a new webinar coming up on Tuesday March 28th – “LoopBack, MongoDB, and Continuous Integration”.

LoopBack is a great tool for quickly generating a CRUD API for your data stored in MongoDB. In this webinar, we will walk through setting up a continuous integration pipeline with tests, and show a few different deployment options.

loopback-logo-sm

Erin McKean (Lead Developer Evangelist, IBM Cloud) is the webinar speaker and will provide a comprehensive walkthrough of a full MongoDB-backed API, including unit tests, continuous integration, and deployment examples.

When: March 28, 2017
Virtual door opens at 12:45 pm EST
Webcast starts at 1:00 pm EST

Register Now!

Also, don’t forget about the webinar we announced last week – Combining OpenWhisk (serverless), OpenAPI (swagger) and API Connect to Build Powerful APIs.

Webinar: Combining OpenWhisk (serverless), OpenAPI (swagger) and API Connect to Build Powerful APIs

Our next webinar will be held on March 16th, focusing on “Combining OpenWhisk (serverless), OpenAPI (swagger) and API Connect to build powerful APIs”.

Using the power and simplicity of serverless functions and exposing them via API Connect provides a clean and organized way to build powerful APIs, applications and integrations for your developer and your customers. We will go over both technologies, as well as OpenAPI, to see how the magic comes together.

Read more

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