![]() Data lineage is built on top of data integrity, which has to be solved first.Also, protecting logical entities is even harder in the cyberspace, both in data transportation and storage. ![]() One example is, tracking every single piece of coal from a carrier ship sounds crazy, but tracking every data signal from thousands sensors from the very same ship is quite common. The granularity of data has much more detailed scale in IoT and Big Data world.We are tracking logical entities (bits, files or data streams) instead of physical entities (coal, car parts or packages).However, compares to the traditional industries, data lineage are facing new challenges. You can easily compare this with the traditional supply chain of raw materials in manufacturing industry and/or logistic industry. It also helps to trace errors back to the root cause, and comply with laws and regulations. It increases trust and acceptance of result of data process. The goal of data lineage is to track data over its entire lifecycle, to gain a better understanding of what happens to data as it moves through the course of its life. Various data sets are generated (most likely by sensors), transferred, processed, aggregated and flowed from upstream to downstream. If we say “Data is the new oil”, then data lineage is an issue that we must to solve. For example, Timestamp is now an optional field. Specified mandatory fields and optional field in the format.Have an unified format that covers both lightweight format and standard format, but more flexible and self-explained.The IOTA Tangle is designed to meet these requirements.This article is now expanded to an article series, where we have more detailed discussion and open-source code, check them out! Since IOTA was designed for large swarms of small scale devices on the Internet of Things, its ledger must be dynamic, very decentralized and lightweight. Several projects use DAG’s instead of linear blockchains. It’s represented in a computer program via a well known data structure called a DAG. The IOTA Tangle is IOTA’s decentralized ledger. If you didn’t constrain the system to two TX’s required to verify a next one, you could end up with several independent blockchains growing in various directions. This guarantees that the DAG will stay slim and not too many branches will grow outwards instead of forward. ( Blockmesh shares a similar concept.) Staying SlimĮvery network participant must verify 2 previous transactions before they issue one TX. You may think of an IOTA Tangle as multiple blockchains moving in parallel. If the previous TX’s are valid and they also validate the present one, it guarantees that the next TX’s must also be valid.īy building a graph of relations this way, we end up with a data structure that looks like this: IOTA Tangle Illustration By Navinram CC BY 2.0 via Wikipedia Then it makes those TX’s “parents” of a new TX. Instead, each device must verify two previous parent transactions. In IOTA there’s no need to reach consensus for a single block every X seconds or minutes. If each IOTA node employed a rigid blockchain data structure like Bitcoin, there’d need to be a more rigid synchronization mechanism among all these small scale devices. So each little device in a mesh of thousands, perhaps millions, of devices must be able to swiftly send and receive transactions. IOTA works like this because it’s designed for IoT – Internet of Things. (For details about this see the aforementioned DAG post). In this post we talk about a DAG application in the IOTA ecosystem – the IOTA Tangle.Īs you may have guessed from the Wikipedia illustration at the top of this article, a tangle looks like a graph of transactions.Īt first look it might seem like a messy spiderweb, but it’s actually a special graph that moves only one way. In a previous article, we’ve discussed the concept of a DAG – Directed Acyclic Graph.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |