Iot and the back-end developers
2 likes1,683 views
The document discusses the transition of enterprise software developers to IoT developers, highlighting differences between enterprise and embedded development. It emphasizes the importance of IoT architecture as a superset of enterprise architecture and the role of messaging protocols like MQTT in IoT systems. Additionally, it addresses the challenges in IoT adoption, including protocol integration and operational constraints.
Iot and the back-end developers
- 1. Broughttoyou byHenrykKonsek The Internet of Things and the back-end developers
- 2. @hekonsek
- 3. What it takes for the enterprise software developer to become the IoT developer? This talk
- 4. - Enterprise vs Embedded - Architecture - Communication - Operations - The dark corners of the IoT adoption
- 6. Enterprise vs Embedded Enterprise software developers: ● software for the data center ● unified target platform ● high level of abstraction
- 7. Enterprise vs Embedded Embedded software developers: ● software for the various hardware devices ● different target platforms ● low level of abstraction
- 8. IoT = Enterprise + Embedded IoT consolidates enterprise and embedded worlds.
- 9. Many existing non-embedded companies would like to join the party. The Internet Of Things = $$$
- 10. Can typical back-end developer be adopted to develop IoT solutions? The market is full of the enterprise developers
- 12. The enterprise systems are located in the data center. Enterprise systems in a nutshell
- 13. IoT architecture is the superset of the enterprise architecture. IoT architecture
- 14. Synchronous communication, usually via HTTP. Communication in the enterprise systems
- 15. How these new elements communicate? Communication in the IoT systems
- 16. Communication in the IoT
- 17. IoT systems are usually messaging-based. Messaging ● asynchronous ● one-way communication ● many, small messages
- 18. Many enterprise developers are familiar with the messaging technologies. Messaging legacy
- 19. Enterprise Integration Patterns “bible” still applies to IoT. Messaging architecture legacy
- 20. If developer understands JMS topics, (s)he’s halfway through understanding MQTT. MQTT
- 21. - small payloads (i.e. GSM and battery friendly) - works well with the unreliable networks - devices can talk MQTT Why developers should care about MQTT?
- 22. MQTT can be bridged to JMS, AMQP, etc. MQTT bridge
- 23. Reliability- and interoperability-oriented messaging. AMQP
- 24. AMQP is pretty widely adopted in the enterprise world. AMQP
- 25. HTTP is still the most popular “messaging” protocol for IoT. REST
- 26. REST for the constrained devices. CoAP
- 27. Operations
- 28. DevOps practices are extremely important for the IoT adoption. DevOps
- 29. Enterprise developers can reuse their devOps skills. Linux is IoT friendly
- 30. Think about it ;) Docker for IoT?
- 31. The dark corners of the IoT adoption
- 32. Enterprise developers are not used to mix protocols in a single solution. Protocol wars
- 33. - high availability in the field is a luxury - design with the failure in mind Unreliable connectivity
- 34. - batteries - paid GSM data Constrained resources
- 35. - temperature - vibration - “GPS signal lost” Surviving environmental conditions
- 36. - remote deployment - remote monitoring - remote updates (over-the-air) Remoteness
- 37. Thank you!