What happens when the fast-paced world of the web meets the resource limited world of distributed embedded systems? During our time putting the internet in the Philips Hue lightbulbs, we encountered interesting challenges. How do you create a cost-effective IoT architecture that scales? What changes when your product has both a local and a remote API, each with different capabilities? An architectural overview, war stories and passing on some key learnings.

1. Lighting the way for the
Internet of Things
@lukasvan3l

19. “An escalator can never break:
it can only become stairs”
–Mitch Hedberg

22. www.huelandsspoor.nl

27. Logging Monitoring Debugging

31. Keep critical critical

32. Build so you can open it up

33. Be pragmatic

34. Single point of truth

35. Constant evolution

41. www.superslideqam.nl

47. Build your own device
• Build with failure in mind
• Electric Imp
• IFTTT

48. Build your own cloud
• Keep critical critical
• Be pragmatic
• Iterate

49. @lukasvan3l
@q42