Think Engineer are celebrating a high accolade! For the second year running we are one of ConnectTVT's 50 Game Changers in the Thames Valley region.
Having arrived home from EMF Camp 2018 late on Monday evening and taken time to recuperate and gather ourselves, it's about time we started to tell you guys about it. Other members of the team will no doubt go into more technical depth and talk about their various projects and talks. I will stick to the basics of the event and speak from a first timers perspective.
Building an Internet of Things project often relies on the well-established client-server architecture at scale. When the term was first used, it referred to users as the client, requesting to run jobs from a central computer, i.e. the server.  Nowadays, with IoT, clients are the edge devices requesting data to be stored/processed by a server. Although, in theory, a single server could handle a small batch of IoT devices, a sudden surge of device requests could easily overwhelm the server and affect availability and data integrity.
This is where distributed computing coupled with a microservice architecture comes in.
When you think of say, an audio signal or waveform, you think of this, right?
Figure 1: Audio waveform in the time domain.
Figure 1 depicts an audio signal in the time domain; essentially a visualisation of the variation of the signal’s amplitude (plotted on the y-axis) over time (plotted on the x-axis). So, by observing the signal in this way, how much information can actually be extracted?