O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Broughttoyou byHenrykKonsek The Internet of Things and the back-end developers
@hekonsek
What it takes for the enterprise software developer to become the IoT developer? This talk
- Enterprise vs Embedded - Architecture - Communication - Operations - The dark corners of the IoT adoption
Enterprise vs Embedded
Enterprise vs Embedded Enterprise software developers: ● software for the data center ● unified target platform ● high lev...
Enterprise vs Embedded Embedded software developers: ● software for the various hardware devices ● different target platfo...
IoT = Enterprise + Embedded IoT consolidates enterprise and embedded worlds.
Many existing non-embedded companies would like to join the party. The Internet Of Things = $$$
Can typical back-end developer be adopted to develop IoT solutions? The market is full of the enterprise developers
IoT and enterprise architectures
The enterprise systems are located in the data center. Enterprise systems in a nutshell
IoT architecture is the superset of the enterprise architecture. IoT architecture
Synchronous communication, usually via HTTP. Communication in the enterprise systems
How these new elements communicate? Communication in the IoT systems
Communication in the IoT
IoT systems are usually messaging-based. Messaging ● asynchronous ● one-way communication ● many, small messages
Many enterprise developers are familiar with the messaging technologies. Messaging legacy
Enterprise Integration Patterns “bible” still applies to IoT. Messaging architecture legacy
If developer understands JMS topics, (s)he’s halfway through understanding MQTT. MQTT
- small payloads (i.e. GSM and battery friendly) - works well with the unreliable networks - devices can talk MQTT Why dev...
MQTT can be bridged to JMS, AMQP, etc. MQTT bridge
Reliability- and interoperability-oriented messaging. AMQP
AMQP is pretty widely adopted in the enterprise world. AMQP
HTTP is still the most popular “messaging” protocol for IoT. REST
REST for the constrained devices. CoAP
Operations
DevOps practices are extremely important for the IoT adoption. DevOps
Enterprise developers can reuse their devOps skills. Linux is IoT friendly
Think about it ;) Docker for IoT?
The dark corners of the IoT adoption
Enterprise developers are not used to mix protocols in a single solution. Protocol wars
- high availability in the field is a luxury - design with the failure in mind Unreliable connectivity
- batteries - paid GSM data Constrained resources
- temperature - vibration - “GPS signal lost” Surviving environmental conditions
- remote deployment - remote monitoring - remote updates (over-the-air) Remoteness
Thank you!
Próximos SlideShares
Carregando em…5
×

Iot and the back-end developers

1.567 visualizações

Publicada em

Internet of Things is going to be big. Billions of connected devices and trillions of dollars of the economic value-add in the 2020. The existing enterprises are going to start collecting the enormous volume of data from the myriad of the heterogeneous devices. Data collected by the enterprises will be used to transform these organizations to be more efficient.

What does it mean for an average back-end developer hired in organization willing to adopt to the Internet of Things world? What should the developers know to stay relevant in the 2020? Which part of the existing knowledge and know-how can be reused? What new the developers have to to learn and master to be able to create the IoT-ready systems?

Are you back-end developer? Do you hire or manage developers? Then come, listen to my talk and learn what Internet of Things means for the developers and companies hiring them.

Publicada em: Tecnologia
no profile picture user

  • Entre para ver os comentários

Iot and the back-end developers

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

×