This site uses cookies to enhance your browsing experience and deliver personalized content. By continuing to use this site, you consent to our use of cookies. COOKIE POLICY COOKIE POLICY
The long answer is a bit more nuanced. To really understand whether blockchains are right for your organization, you need to pose a single starting question. Are you the only one who maintains the data that you’re considering for storage in a blockchain? If the answer is “yes”, then you absolutely don’t need a blockchain.
To understand this answer, you need to have a clear understanding of why blockchains even exist. And the answer to that is “trust”. With a private database, the consumer is required to trust the maintainer of the database. This is how applications and services have operated since the beginning of time. We can do things like perform third party audits to verify that the state of the system is as the owner claims (and that’s an entire industry in itself!), but in the end we have no concrete, verifiable mechanism to authenticate the data as it is presented.
A blockchain is the internet’s solution to this problem. It allows actors or participants that don’t trust each other to operate in a way that ensures that everyone always knows the state of the system. It broadcasts transactions and uses mathematically proven concepts to assure all participants that:
The state of the system is accurate
The history of the system is accurate
The participants must acquiesce to the transactions
So, when is a blockchain right for an organization? To answer that, we must first differentiate between “permissionless” and “permissioned” blockchains. The difference is apparent in the name; one blockchain allows some central individual or group to decide who gets to participate and one blockchain does not. Popular permissionless blockchains include Bitcoin, Litecoin, and Ethereum, among others. These blockchains allow *anyone* to participate, requiring only that you adhere to their mathematical rules. One upside is that they require no trust for any third party to use and they are transparent, meaning everyone can see every transaction. However, this transparency is a double-edged sword, as competitors and others may be able to glean information from these transparent blockchains. The permissioned blockchain is better suited for groups that would like to interact in a manner that doesn’t require complete trust, but also don’t want to broadcast their entire transaction set to the whole world.
So, if you have a situation where you want to share data but not all of the participants trust a single source to keep and maintain that data, or you would like to share data across users without giving a single user power over the data, a permissioned blockchain may be right for you. If you have a situation where you want to expose transactions to the world, permissionless blockchains probably already exist that you can utilize. But if you’re the sole arbiter of the data, then a blockchain is just a Rube-Goldberg version of a database.
When There’s Too Much to Fix: How Smart Prioritization Unlocks Revenue at Scale
Every operations team has a backlog. The question isn’t whether you can clear it — it’s whether you’re clearing it in the right order. For most teams, the honest answer is no. And that gap between the order work gets done, and the order it should get done is quietly costing organizations millions. The Volume Problem High-volume exception processing shows up across […]
Creating Reusable Code Templates to Reduce Client Project Startup Time
In consulting, one of the least visible but most expensive phases of a project is the beginning. Teams can spend days or weeks setting up repositories, agreeing on structure, wiring basic infrastructure, and solving problems that have already been solved many times before. Code templates are a practical way to reduce overhead while improving consistency. […]
Player Three Has Entered the Game: How AI Is Finally Bridging the Divide Between Design and Engineering
As AI begins to become more prominent in our day-to-day lives, I find myself in a unique position. As a practicing software engineer and UI/UX designer, I am genuinely happy to see the introduction of AI tools begin to take shape in our industry. But more importantly, I am happy to start seeing the effects it is having on what has historically been a pretty challenging relationship: the […]
The Disappearing Middle of Software Work: Why the Bookends – Strategy & Impact – Matter Most Now
Here’s a question nobody in enterprise software wants to sit with: what happens to the middle? Not the middle of the org chart. The middle of the work. The vast, expensive layer of effort that has defined enterprise software delivery for thirty years—translating what the business wants into working code. The requirements-to-implementation pipeline. The “build phase.” […]
Full distributed tracing and exception capture for any application — without writing a single line of instrumentation code. View the source code on GitHub → The Premise Observability is essential for understanding what’s happening inside your services, but instrumenting an application by hand — adding trace spans, logging calls, and metric counters throughout your codebase […]
Building a Consultant in the Trenches: How Playing Offensive Line Shaped My Consulting Career
People often ask me the same question when they find out that I played college football: “Do you miss it?” On the surface, it’s a bad question with an obvious answer. Yes. However, if I give myself a minute to sit with that question, the answer is more nuanced. Yes, I miss playing football, but […]