Why # We have been doing similar workflows for 5+ years now, much longer if you count fully custom tools. So have countless others. Yet, if you asked a new engineer to build this, you can wave goodbye to a few weeks of their effort as they navigate obtuse documentation and outdated StackOverflow answers. This is […]
From Metal To Alerts With AWS IoT, Timestream and QuickSight Read More »
Before we start, what is HTTP? # This is what HTTP REST looks like…ClientServerIdentify Yourself!SSL HandshakeAuthenticateAuthorizeMake a RequestAsk for dataSend dataTypical Client-Server FlowClientServerIdentify Yourself!SSL HandshakeAuthenticateAuthorizeMake a RequestSend dataAcknowledgeA bit later… We noticed some issues… # Each request is preceded by an SSL handshake (if HTTPS) and authentication This can consume significant resources (CPU, time, memory) each time
Websockets for Hardware Engineers – Part 1 Read More »
Yes, really. Let me explain why. It all arises because of the dependence of the vast majority of IoT solutions on a cloud back-end. While attractive for many reasons, using a cloud based solution for certain key parts of your infrastructure can lead to pretty dramatic loss of functionality when things go wrong. It’s not
IoT’s big dirty secret – It’s the cloud! Read More »
