In the first post of this series we’ve been looking into architecture styles and explored both centralized and decentralized application architectures, and highlighted the differences between those and a truly distributed application architecture. Both decentralized and distributed architectures are really interested within the domain of IoT, because the projected fleet of billions of devices will probably be communicating in these ways. That’s a good reason to explore this a bit more.
The blog is written by our tech-team with Andreas Schmidt, CTO of ThingForward. If you have any questions or comments please get in touch. He and his Crew are always happy to “talk tech” with you. If you have any questions or comments please get in touch.
In our first part of this testing series we outlined how to set up unit test cases for an embedded project using PlatformIO’s testing capabilities. Our first test cases have been running on the native platform, that is, a developer notebook or a CI server. Now we’re going to look at bringing test code onto devices.
This blog post is the first part of a series of post on how to set up a test-driven development environment for embedded device testing. We started using PlatformIO for our educational track’s prototyping workshops, and PlatformIO offers integrated testing mechanisms which we’ve found really useful.
This is the first part of a tech blog post series i’d like to start on the topic of decentralized and distributed IoT computing. At ThingForward we spend a lot of time on coding protocol and communication software and firmware for small sensor devices, and the IoT model brings up an architecture model which in part differs from the one we find in web app architectures. We already had a webinar on this topic last month and we’d like to investigate this a bit further.