IoT Zone is brought to you in partnership with:

Ross founded the open source Mule® project in 2003. Frustrated by integration "donkey work," he set out to create a new platform that emphasized ease of development and re-use of components. He started the Mule project to bring a modern approach, one of assembly, rather than repetitive coding, to developers worldwide. He is now the Founder and CTO of Mulesoft. Ross is a DZone MVB and is not an employee of DZone and has posted 98 posts at DZone. You can read more from them at their website. View Full User Profile

Putting an API on a Raspberry Pi

  • submit to reddit

In the Internet of things no device is an island. And while Raspberry Pi are pretty cool on their own adding an API makes them a lot more interesting. We have been playing around with Raspberry for a while now and have a small distribution of Mule, called ‘Anypoint ’ that happily runs on small embeddable devices like the Raspberry Pi.  These ARM-based devices are taking the world by storm since they are lower powered, low cost and can be embedded into small hubs to control other things like lightbulbs, or be used inside anything from PoS kiosks to gas pumps to cars to medical devices.

I demoed putting an API on a Raspberry Pi during our Mule Summit tour earlier this year, see the video below.

With this we are starting to extend connectivity out to the edge of the network and allow developers to connect to anything whether deep in the data centre, in the cloud and now devices too.

This demo uses the forthcoming APIkit to expose an API to the niftly little Blink(1) device. The bit I like about this demo is that I can manage the API and the runtime using the same API Management and Governance platform we provide to manage on-premises or cloud , I also get the CloudHub Insight BAM capabilities making it possible to track events all the way to the edge of the network.

Published at DZone with permission of Ross Mason, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)