Architecting the Internet of Things

This session will give a brief overview of what IoT is from the perspective of an Architect within Consulting Services. We will look at what kinds of projects we are getting involved in, what those projects look like in reality, the kinds of challenges you will face, the network you need to succeed, and the risks involved. This session will move beyond hypotheticals and introduce real world examples that will help you prepare for life as a delivery architect working with IoT. Architecting the Internet of Things by Microsoft @ TechEd North America
Collecting information from lots of devices is cool - but it is just telematics. Merging perspectives between devices, systems, and humans to build a better understanding of the world around us. But tying together insight with action - there lies the promise of IoT.

Objectives

Understand what IoT means for IT Architects
Learn the tecnologies and how to begin applying them to deliver a modern IoT project
Be better able to talk to Customers about IoT

Session Overview

What is IoT and why it is important
IoT from an Architect's perspective
Technologies Architects need to know
Common pattern and practices
Quick real world examples

Expectations

Level 200 Architecture Session
There will be no code
There will be no "flashing light" demos

IoT: The Internet of Things

The network of physical objects that contain embedded technology to communicate and interact with their external states or the external environment. Gartner Definition
20 billion devices by 2020. Gartner

What is it?

Unique objects connected to the Internet
Devices, not people
Bi-directional communication
Large, complex data flows
New types of insight

Example 31% Cowwy ROI Beef Industry! The Internet of Cows: Azure-powered pedometers get dairies mooovin’

Why is it important?

Worlwide market for IoT solutions to reach $7.2 trillion in 2010 (IDC). Economic value-add is forecast to be $1.9 trillion across sectors in 2020 (Gartner)
Leading Industry Examples: Utilities, Insurance, Agriculture, Factory, Automobiles, Transport, Consumer

The Gartner Hype Cycle

An Architect's Perspective

POV: IoT is at an inflection point

Hardware is getting cheap
M2M solutions are mainstream
Connectivity is proliferating
Software is more advanced
Cloud cost, scale, flexibility

Example Talk Design Thinking Microsoft CityNext: Helping Guide Dogs support people with sight loss

General Technical Requirements for IoT

Many Devices
Large Scale
Vague Security Requirements
Volumes of Data
End to End Integration

Information Exchange Patterns

Basics of IoT Communication

Telemetry: Information flowing from a device to other systems for conveying status of device and environment
Inquiries: Requests from devices looking to gather required information or to initiate activities, I Am Ok!
Commands: Command from other systems to a device or a group of devices to perform specific activities
Notifications: Information flowing from other systems to a device (group) for conveying status changes

IoT Solutions

A service-oriented architecture (SOA) is an architectural pattern in computer software design in which application components provide services to other components via a communications protocol, typically over a network. The principles of service-orientation are independent of any vendor, product or technology. Wikipedia
SOA may introduce problems later on on IoT solutions