Cloud as a Story - Vunvulea Radu

Testing, Unit Tests, TDD (Test Driven Development) are one of the first thing that we learn when we are in university and study computer science. A part of us might be lucky enough to have a specific course for TDD. Code is written by people for machines that needs to resolve problems. People do mistakes and this is why it is so important to test our code. I didn’t have the opportunity to see until now a working application, without bug or issues from the beginning. I would say that a complex application that is not covered by unit tests and without a testing process will end up in the trash. At the beginning of each project there is a classical discussion related to unit tests and code coverage. - Do we need unit tests?  - Yes. - What is the code coverage target? - 80%, 60%, 20%, 100%.... It is pretty clear that we need unit test. An engineer needs to be able to test his code and check if what we develop is working as expect or not. The response for the first question is

The current trend in IT industry, especially in IoT world is to store all the data that is produced by all the devices or systems that are connected to a network. The storage is so cheap, that companies prefers to store and archive all this data, without caring if the data can be used now or in the future. The main scope of this approach is to have all the information that might be needed in the future, if a system like Machine Learning or Hadoop is used. You never know what parameter or logs might become relevant in the future for an insight or a trend. Things are becoming interesting in the moment when your devices contains more than100 or 200 sensors per device, with a sample rate of 1s or 0.1s. Let’s take as example a bottle manufacture, that has plants all around the globe. Each plant has 800-1000 devices connected that runs 24/7. The quantity of data that is produced every day can reach easily 0.2-0.5TB. Each day new data will arrive to the platform in the warehouse. Colle