IBM and StrongLoop Are Going to APIStrat 2016

IBM and StrongLoop will be going to Boston, Massachusetts to attend APIStrat 2016 from November 2-4.

APIStrat, the API Strategy & Practice Conference, shines a spotlight on the API economy. The event site states:

“APIStrat brings together experts, leaders, and members of the community to discuss what we each see on the ground every day. This event is not just for developers and IT teams, it is also for business users, executives, and anyone who seeks to better understand how APIs are impacting the world around.”

Read more

Webinar – Strategies for API development: Creation, Management, Security

Looking to move forward with API development? Creative Intellect Consulting has a webinar coming up on November 10th  that will show you how easy it is to create, manage and secure your API.

Here’s a description of the webinar:

Application Programming Interfaces (APIs) enable easier and faster development of many different types of applications. Crucially, they allow the important abstraction of complex back-end systems. While historically this may have meant enterprise legacy systems, today’s modern APIs are focused on providing quick and easy access to application services and functionality, whether developed internally or externally, in a lightweight fashion, so as to minimize the impact to the network.

API Connect Webast Tweet 2 9-7-16(1)

Read more

The Node.js Debug Module: Advanced Usage

In a previous post, I explained the debug module and how to use it for basic debugging.  I recently used it to help me understand complex interactions between events in Leaflet and Leaflet.Editable. Before going over that, however, I’m going to lay the groundwork with a couple organizational tips that makes debug easier to use. This post assumes you have either used debug or read the previous post…. Read more

Using LoopBack to Build APIs For APIs

“Building APIs for APIs” sounds a bit like infinite recursion, but actually I’m talking about one of the cooler aspects of LoopBack: the ability to define a server API that maps to another server. Essentially your API acts as a proxy for another API. There are a lot of reasons you may want to do this, including:

  • Supplementing the set of APIs you already provide. Perhaps you’re a sports company that can provide APIs for every sport but golf. If you can find a third-party provider for golf data, you can then add it to your own library and offer a more complete solution to your users.
  • Modifying API results to fit your needs.  Maybe you want to use an API that is a bit inflexible in the data it returns. By creating your own proxy, you can modify the result sets to return only what you need.
  • To improve performance you can add your own caching layer.
  • Perhaps you want to use an API in your mobile app but don’t want to embed sensitive information, like an API key, in your source code. You can use your own server, and this LoopBack feature, to keep the key hidden in your Node.js code.

Read more