“For IoT networks to become truly scalable, and not be dependent on a centralized cloud / management platform, decentralization of trust has to occur… and that’s the picture of blockchain!
Any decentralized IoT solution should support three foundational types of transactions:
– Trustless peer-to-peer messaging
– Secure distributed data sharing
– A robust and scalable form of device coordination.
With those three capabilities, the devices with IoT sensors will be…democratized. They no longer need a human for authorization, nor a central platform to make decisions. The greatest challenge will be the design of the blockchain network in this world of device democracy is scalable when billions or trillions of devices participate in transactions independently.”
Manav Gupta in a post on LinkedIn.
Check out the link above and the image within it. It articulates the concept of device democracy and the revolutionary business models that they will be able to facilitate.
lt also helps to suggest how blockchain and peer-to-peer messaging will change device coordination compared with how today’s OSS perform the task. The complex workflows managed by OSS also prime them for evolution to smart contracts. The opportunities are exciting.
But it makes me wonder about the types of fully-automated lifecycles suggested in the post. They’re all run by software but no software is infallible (as anyone in OSS knows only too well), nor is it able to predict every state or state change that could happen in an autonomous system.
If everything is happening automatically and without intervention, is it therefore overlooked or even forgotten? It’s incumbent on us to carefully plan the checkers that are watching for automated life-cycles that hare gone rogue.
It’s the same message in current OSS models. We don’t really have a way to reconcile all of the potential variants. Despite voluminous testing (often automated too), we still experience escaped defects.
Have you ever had an OSS or BSS project that’s impacted by poor data quality? The problem of data integrity gets raised on almost every
“One of my favorite things about designing software is designing the defaults. The defaults define the experience for everyone out of the box. And, therefore,
Have you ever been tasked with mapping out the processes for the telco you work for? Either as a way of documenting current state, or
In the last week alone, I’ve had two potent reminders that the world of OSS is simply (pun intended) too complex. This manifests in many
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
