1. A 3-TIER ARCHITECTURE
FOR THE INTERNET OF THINGS
David Bericat,
Senior Solution Architect, IoT Specialist
david.bericat@redhat.com
2. THE INTERNET OF THINGS
INFORMATION LIFECYCLE
Information
triggers pre-defined
business rules
Summarized
information sent
to back office for
deep analysis
New rules created
and pushed to business
rules engine
New data analysis
optimizations
Controlled and
augmented by
domain experts
Field level
data analysis
INFORMATION
Data analyzed to
drive tactical action
KNOWLEDGE
Information stored in
DB and analyzed,
yielding optimized
tactical tools
INTELLIGENCE
Actions driven
from information
DATA
Data emitted from
sensors, control panels,
actuators, human
interfaces, etc.
3. Transmission costs
paid by consumer
Analysis and response
not critical
Simple network
communications
Smaller amounts
of data
Bandwidth and network
transports not a concern
No need for data
summarization
WHY ENTERPRISE IOT
NEEDS THREE TIERS
Two-tier architecture for consumer applications
4. A THREE-TIER ARCHITECTURE FOR
THE INTERNET OF THINGS
Datacenter functionality
• Long-term data analytic
• Long-term control
• Rule creation
• Reporting
• Enterprise applications
• Service management
Controller functionality
• Communications
• Data summary
• Real-time data analytics
• Real-time actions/rules
End point functionality
• Communications
• Data acquisition
6. Control (Middle) Tier
Data storage layer
RH storage is used for intermediate term data storage.
This data may be needed for tactical analysis, regulatory
or other reasons but it is not valuable enough to
transmit to the data center.
Real time data state layer
JDG provides real time in-memory key/value pair data
storage. This data is then monitored by BRMS for
action.
Business rules layer
BRMS is used to match patters in the data and take actions
based on pre-defined busines rules
Enterprise integration layer
EI automates routine services for applications. Examples
Include data routing, transformation, spiltting /
aggregation, protocol mediation, etc.
Data transport layer
A-MQ (with Qpid dispatch) is used to move data
Asynchronously between sensors, control points, etc. using
open standards based messaging
RHEL/Win
A-MQ
And Qpid Dispatch
FUSE ESB
BRMS
RH Storage
JDG
Hardware
Management
