Developer Blog hand with wrench

Welcome to the relayr Developer Blog

Recent posts

  • Google Cloud Platform and Sensor Data: a first look
    Aug 11, 2017
    Introduction IoT data usage by 2018 is expected to reach 400 Zettabytes — 10^21– by 2018. Companies looking to leverage IoT data analytics will need to rethink their data center infrastructures and strategies. We explore the implications of this fact and how leveraging Google Cloud Platform we can create data pipelines that allow for data compression in each stage. Define the data source. Extract & Transform the streaming data.
  • DevNet coding camp Calgary: the drive for modernization in Alberta
    Feb 6, 2017


    relayr was invited by Cisco DevNet to participate in the Automation Coding Bootcamp in Calgary, Alberta (Canada) that took place between Friday the 27th and Saturday the 28th of January 2017. The venue was the Southern Alberta Institute of Technology.

    Roland Plett from Cisco was kind enough to host our team for a weekend of hacking around the themes of:

    • people flow, and
    • alert systems in the context of safety for Oil and Gas sites.

    The event took place at the beautiful SAIT’s Heritage Hall.

    The goal was to bootstrap the usage of Cisco APIs and IoT — that’s where relayr comes in — to local students and professionals through a hacking competition. Participants had 22 hours to come up with (ideally) working prototypes of hardware and software solutions addressing the above themes.

  • Good documentation: More than just a common courtesy
    Jan 16, 2017

    This week we launched version 2.0 of the relayr Documentation Center. The site was in desperate need of an overhaul: the design didn’t match our branding guidelines, the content was purely referential and not interactive, and worst of all, the information was outdated and poorly organized. It got to that point because we treated documentation as an afterthought, as something we could fix once we’d pushed the code out the door. This kind of thinking will set you up for failure.

    Over the past several months, we came together as an organization to make documentation a priority and treat it as a product of its own. Good documentation is everyone’s responsibility, and once everyone adopted this attitude, we were able to deliver a comprehensive documentation repository. This post explains how we accomplished this and why your product won’t succeed without good documentation.