A large graph and the interorganization

Source: Max Delbrück Center for Molecular Medicine

Warning: I will mention Web3 in this article.

To underestimate the obvious, vendors, journalists, and enthusiasts often overpromise when it comes to new data technologies like Web3.

I use the term web3 in a hopeful way with a broad definition in mind, which is unfamiliar to most people. When I mention web3, it would be nice if you could put aside the associations with cryptocurrency, blockchain, and an endless, speculative-driven hype cycle for a while.

Instead, think of the benefits of an open, borderless Web — a shared, tightly connected, and automatically scalable infrastructure with less hassle, more built-in benefits, and no inherent silos.

A website where you can publish on demand and simultaneously control access, in an architecturally integrated way, to all the data you publish.

A website that supports chance discovery and rapid community building in many new and different ways.

A large, less centralized peer-to-peer graph allows meta-organizations and cross-organizations to organically form, evolve, merge, grow, and reform.

Unlike the “metaverse” (which won’t be real until border-crossing, malleable, and interactive organizations become the norm), the technology for this great graph is here and now. Most people just haven’t learned how to use it to their best advantage yet, if they’ve learned how to use it at all.

A great innovation graph

Let’s avoid the hype and avoid talking about “decentralized autonomous organizations” or DAOs (neither decentralized nor autonomous). Instead, think of dynamic, machine-assisted, human-in-the-loop inter-organizations — what IDC called the innovation graph five years ago.

What I found compelling about IDC’s conceptualization of the innovation graph when I first saw it was that with data literacy and maturity, a new form of With agility comes a new form of agility – the ability for individuals and organizations to skate along the edges to different nodes of industry value that they didn’t have. t been able to pursue or capture before.

For example, companies can become data providers when they were not. Consultants can also use their relationships across industry boundaries to help clients cross those boundaries.

IDC Innovation Chart

The most data-heavy and mature attack on all fronts today, similar to how Amazon began to make a name for itself in healthcare, logistics and cloud subscription services there ten or fifteen years old.

Web3 as an evolution of P2P networks + shared file systems

P2P data networks like the Interplanetary File System (IPFS) are critical to the feasibility of an upgrade to the peer-to-peer network. Unlike the W3C web standard, IPFS offers logically derived unique identifiers and content addressing.

Two examples of the benefits of content identifiers (CIDs) and content-only addressing:

Elimination of duplicates. “The CID created with IPFS provides a digital fingerprint that can guarantee authenticity and uniqueness. This simplifies deduplication by creating a single data instance with an immutable CID. And because there is only one copy of each resource, authentication is much easier.

Since there is no duplication, IPFS minimizes the storage space consumed by data backups and archives. This creates a huge advantage for any organization that archives its data. »

– From IPFS hardware optimization provider Silicon mechanics’ to place

Eliminate link rot. “Thanks to content addressing, link rot can be a thing of the past. A content-oriented system like web3.storage is like our key-value based DNS, with one significant difference: you can no longer choose keys. Instead, keys are derived directly from file contents using an algorithm that will always generate the same key for the same content.

– From the IPFS provider web.storage to place

Keep in mind that file systems in general are growing in capacity. The implication is that more developers aren’t using databases as much as they used to; they use file systems instead.

In this sense, they can circumvent the drawbacks of databases (such as their inherent siloing, centralization, and feature bloat). They can use a large graphic with its built-in file system instead. IPFS, in this sense, provides an automated file system for all.

All these liberated features are now available on another kind of open web. While ease of use is not yet often a part of these capabilities, a critical mass of good enough user experience should materialize over the next few years.

Legacy: the gift that keeps on giving (when we want)

With the scaling benefits of IPFS and the growing ecosystem around it, collaboration could scale at a much faster and more dynamic pace than it has. What could hold us back? This is what market analysts call the installed base.

The software installed base involves technical debt and inertia on a giant, monolithic scale. It’s the Software Wasteland, all the code that serves one purpose and just different enough not to interoperate, all the architecture that still gets in the way and keeps popping up in today’s cloud services. These are all the methodologies our education system continues to re-teach, the provincial silos in yet another editions of relational database textbooks that students still have to rent, the dearth of .edu courses on the commonalities of content, data, and knowledge graphs which should all be treated as such…..

These are the packaged software monoliths that embraced microservices a decade or more ago and were born as… cloud monoliths, with cloud and SaaS software suites, duplicate data proliferation and all the other modern dilemmas.

The biggest challenge facing innovators today is maintaining integrity and continuing to progress despite temptations. It’s easy to give in and take the biggest paychecks from rebranded legacy markets as new. The real One Big Graph web3 without all the titular inhibitions is here to be taken – if we’re going to fight hard enough for it.


Comments are closed.