3. Components of a Traditional Internet of Things Architecture
Sensor Data History
Sensors
Operational data in the Cloud
In-memory Analytics
Dashboards /
Predictive
Analytics
Publish /
Subscribe
Cloud
Infrastructure
Bid data /
Context
Computing
Real-Time Analytics
Real-time Analytics Operational Analytics Big Data Analytics
3
4. IoT Components including Gateways
Sensor Data History
Sensors
Informix / Cloudant /
IoT Foundation Service /
TimeSeries Service
REST, NoSQL,
Relational, Timeseries,
Spatial storage &
Operational Analytics
Informix Warehouse
Accelerator
SPSS / Cognos /
PMQ
Message
Sight /
MQTT
SoftLayer /
BlueMix
BigInsights /
DashDB /
Identity Insights /
Watson
Infosphere Streams
= IBM products = IBM Database
Predictive analytics
and dashboard
Cloud infrastructure
Hadoop / Big Data
analytics / Context
Computing
Publish /
Subscribe
Real-time
analytics
Real-time Analytics Operational Analytics Big Data Analytics
In-memory Analytics
(no gateway)
Gateways for
local analytics
4
5. 1. Gateways can reduce the cost of the backend cloud
• Reduces cloud storage by filtering/aggregating/analyzing data
locally
• Reduces cloud CPU requirements by precomputing values
2. Reduces latency since actions can be taken immediately
• Intelligent gateways can detect and respond to local events as
they happen rather than waiting for transfer to the cloud
3. Some users are not comfortable putting all their data in the
cloud
• Gateways allow customers to capture and get value from their
sensors without sending data to the cloud
4. Protocol Consolidation
• Cloud does not need to implement the 100’s of IoT protocols
Over time more and more of the processing will move from the cloud
to gateway devices
How Do Gateways Help IoT Solutions?
5
6. What are the Requirements for a Gateway Database?
• The database management system must:
Have a small install footprint, less than 100 MB
Run with low memory requirements – less than 256 MB
Use lossless compression or other techniques to minimize
storage space
Have built-in support for common types of IoT data like time
series and spatial/GIS data
Simple application development supporting both NoSQL and SQL
Require absolutely no administration
Ideally should be able to network multiple gateways together to
create a single distributed database
6
The database must be powerful enough to ingest, process
and analyze data in real-time
7. IBM Informix: The Ideal Database for Gateways
Simple to use
Hands-Free operation – No administration
Supports popular interfaces such as REST and Mongo as
well as ODBC/JDBC
Handles SQL and JSON data in the same database
Performance
One of a kind support for Time Series and Spatial data
Stream data continuously into the database
Run analytics as data arrives
Dynamically add and update analytics when needed
Storage is typically 1/3 the size compared to other vendors
Invisible
Agile
7
Informix is the only database management system
perfectly suited to run in Gateways
8. Sensor Data is Time Series Data
8
• What is a Time Series?
A logically connected set of records order by time
• What are the Key Strengths of Informix TimeSeries?
Much less space required
• Typically about 1/3 the space required by other vendors
Queries run orders of magnitude faster
• Unique optimized storage means codes paths are shorter and more
data fits in memory
Purpose built streaming data loader for sensor data
• Automatically run analytic and/or aggregate functions on new data
Can store structured (SQL) or unstructured (JSON) data for quick
application development
• REST/ODBC/JDBC/JSON interfaces available
100’s of functions predefined
• Programming APIs available to create your own analytics
9. Traditional Table Approach
Informix TimeSeries Approach
Meter_ID Time KWH Voltage ColN
1 1-1-11 12:00 Value 1 Value 2 Value N
2 1-1-11 12:00 Value 1 Value 2 Value N
3 1-1-11 12:00 Value 1 Value 2 Value N
1 1-1-11 12:15 Value 1 Value 2 Value N
2 1-1-11 12:15 Value 1 Value 2 Value N
3 1-1-11 12:15 Value 1 Value 2 Value N
Meter_ID Series
1 [(1-1-11 12:00, value 1, value 2, , value N), (1-1-11 12:15, value 1, value 2, , value N), ]
2 [(1-1-11 12:00, value 1, value 2, , value N), (1-1-11 12:15, value 1, value 2, , value N), ]
3 [(1-1-11 12:00, value 1, value 2, , value N), (1-1-11 12:15, value 1, value 2, , value N), ]
4 [(1-1-11 12:00, value 1, value 2, , value N), (1-1-11 12:15, value 1, value 2, , value N), ]
Traditional Time Series Storage VS Informix TimeSeries
Storage
9
10. IoT Requirements for Temporal Spatial Data
• Many IoT applications have a
spatial component to them
Vehicles, cell phones, even
pets tracking is common
• In these cases both location and
time is important
Show me the vehicles that have
passed by location X in the last
hour
Where has my cat been over the
last few hours?
• Informix allows you to combine
Time series and Spatial data in
the same query
10
11. Informix Handles Structured and Unstructured Data
• There is no common format for sensor data
Vendor 1 sends just temperature, Vendor 2 sends temperature plus
pressure
• Informix is the only product to handle structured and unstructured data
simultaneously in the same database
Allows your gateway to store structured information about the sensor itself
as well as the unstructured sensor readings in one database
• Informix translates between structured and unstructured on the fly
Allows SQL apps to access the unstructured data and Mongo apps to
access the structured data
Structured and unstructured data can be combined in a single query
• “Give me all the temperature data for sensors made by manufacturer X
between Jan 1 and Feb 1”
11
13. Benchmark: Informix vs SQLite
• Hardware tested:
Intel Quark based gateway:
• DK50 and DK100 gateways
• Intel Quark SoC X1020D single core, 400MHz, 32 bit processor
• 256MB DDR3 memory (DK50), 1 GB DDR3 memory (DK100)
• MicroSD for disk
• Software
Wind River Linux platform
Informix Database server version 12.10
SQLite Version 3.7.10
13
14. Benchmark: Informix vs SQLite
14
Tests on Intel Quark Informix SQLite
Data loading – high-speed performance
(records per second)
950 / 1050
secs
(DK100 / DK50)1
700 secs
(Average)2
Storage space that is required for 1 day of data 275 MB 1200 MB
Aggregation query (seconds) 2 secs 4-25 secs
Moving average (seconds) 25 secs 2592003 secs
Missing interval search (seconds) 2 secs 14-30 secs
1. The two figures for data loading with Informix reflect a slight difference in performance between the
DK100 and DK50. DK100 had more running components causing a drop in performance vs DK50
2. Data loading with SQLite had significant variations in load performance as the database size
increased.
3. The moving average result for SQLite is a projected figure that is based on a partial result after 10
minutes.
15. Metric Competitor Informix
Daily processing time
Maximum number of cores used
11 hours
62
5 hour 50 min
32
Maximum amount of memory used 192GB 192GB
Size of database per month of data 15TB 5TB
# Records processed each day 2.88 Billion 2.88 Billion
Billing determinants creation (1/21 of
the total meter population)
51,322 ~2 million reads
per second
TimeSeries Meter Data Management Benchmark
- 30 million smart meters sending data every 15 minutes
- 2.88 billion records inserted each day
- Workload: data Ingestion, data cleanup, and a daily billing cycle
15
16. IBM Informix and Intel Deliver Leading Edge Solutions for IoT
Informix support for Intel’s
new Quark processor, now
supporting Intel family,
from Quark to Xeon.
Quark port in the free
Informix Developer Edition
Informix Developer Edition
available as part of
standard Intel Gateway
developer SDK
Combining IBM and Intel’s strength at the Edge, Gateway and in the Cloud provides
an intelligent, e2e IoT solution for rapid time to market.
Intel® Quark™ SoC / Intel®
Atom™ / Intel® Xeon™
Windriver
McAfee Security
Supports OSGI/TR69
Informix Database
16
17. • Solution from business partners Shaspa, Tatung, and ST-Micro
Runs on ARM and Intel Quark/Atom chip sets
512MB to 1GB of memory
1GB to 4GB of storage
Wireless/Bluetooth receiver
3 inch by 2 inch form factor
• Software components in SmartGate
Informix enterprise edition
Webserver
Debian Linux
Connectivity to the TimeSeries cloud service
Support for common device communication protocols, including:
• Enocean, KNX, Modbus, CANOpen, Zigbee, ZWave, DALI, MBus, SNMP, MPBus
17
Solution Provider Shaspa’s SmartGate Gateway Built
with Informix
Informix Database
Inside
17
18. IBM Informix Supports Flexible Development on HP Moonshot
Announcing
• IBM Informix is available
on HP's new micro server
and is the only
commercially available
database to run on HP
ProLiant Moonshot.
• Informix offers a unique
and efficient data
architecture that provides
flexible grid technology
and enables commercial
grade workloads to take
advantage of these new
server economies.
18