Armchair Architects: How do architects think about IoT?

Resources

Related Episodes (Twitter)

Chapters
00:00 Introduction
01:02 How do architects think about enterprise-scale IoT solutions when designing for brownfield or greenfield scenarios?
02:57 Device patterns for legacy devices add an extra level of complexity
03:59 The differences between designing a solution for a plant vs. a factory
05:23 Is the incoming volume of telemetry something that architects think about in consumer devices or that more of a concern when designing for a manufacturing plant?
06:56 Architects must always consider the context of the incoming data
08:22 Manufacturing plants, while large, usually send a finite number of messages, whereas a modern consumer-based service is far more dynamic, and can generate a much higher volume of messages.
09:23 The relevance of data determines how and where it should be processed, transmitted, and stored
12:47 Are there IoT-specific design patterns?
14:38 What are the three main criteria that an IoT architecture has to satisfy?

[ojpitre]

Armchair architects once again raising so many good IoT questions: Where do you react ? How fast do you need to react ? Short-term twitch reaction or long-term ? Real-time reaction or post-processing analysis ? Archiving needs ? Data needed for AI models ?

Armchair Azure Architects >= Armchair Baseball Managers

[georgeollis]

A very good video! Thanks, both Uli, Eric and David.