Book Image

Arduino Data Communications

By : Robert Thas John
5 (1)
Book Image

Arduino Data Communications

5 (1)
By: Robert Thas John

Overview of this book

In our modern, internet-connected world, where billions of devices constantly collect and send data to systems to be stored and processed, it’s surprising how the intricacies of data transmission and storage are often overlooked in the IoT domain. With Arduino Data Communications, you'll bridge the knowledge gap and become an expert in collecting data from IoT sensors, transmitting data, and configuring your own databases. This book is an exploration of IoT’s inner workings, guiding you through the process of setting up an end-to-end system that you can employ to prototype your own IoT solutions, using easy-to-follow examples. It begins with a general overview of the Arduino ecosystem, acquainting you with various sensors and shields and unveiling the art of data collection. You’ll then explore data formats and methods to store data, both locally and on database servers. As you progress through the chapters, you’ll learn how to set up REST and MQTT infrastructure to communicate with databases and get hands-on with LoRaWAN, Ethernet, cellular, HC-12, and RS-485. The final chapters are your training ground for real-world projects, imparting the essential knowledge you need to tackle complex challenges with confidence. By the end of this Arduino book, you'll have seamlessly configured an end-to-end system, all while immersing yourself in practical scenarios that bring the world of IoT to life.
Table of Contents (20 chapters)
1
Part 1:Introduction to Arduino and Sensor Data
7
Part 2:Sending Data
14
Part 3: Miscellaneous Topics

Understanding high availability

High availability (HA) refers to a characteristic of a computing system that aims to provide an agreed level of performance. This normally refers to the proportion of time that the system is available and is given in terms of a percentage. You can convert this percentage into the number of days in a year that the system is guaranteed to be available, or conversely, the maximum number of days in a year during which the system can be down or unavailable.

For example, if the availability of a system is given as 95%, then the system is guaranteed to be available for approximately 347 days in a year and could be unavailable for up to 18 days in a year. Does that sound good?

The answer to that question, like everything, is “It depends.” A continuous 18-day outage could lose you customers, but when you look at it from a monthly perspective, that would translate to an average outage of 1.5 days every month. Does that sound acceptable? That...