Data Plumbing From Stovepipes To Firehoses

Data is everywhere, but we already know that. What we may not always know or think about is the plumbing that goes on under the data services we all connect to every day.

In today’s era of smart toasters and intelligent doorbells, we’re drinking from a fire hose in very real terms in terms of the amount of data taken in. The point now is that we’re not trying to drink from the data fire hose if it’s fueled by a lower-level stovepiped information architecture; the potential for pipes to burst creating a flood or gouge that drowns us is (or at least should be) too much of a risk to take.


What is stovepipe technology?

So what do we mean by this term stovepipe technology? Both in the real world and in software engineering, a stovepipe system is a kind of single chimney that can only push its flow (smoke, water or data) through a single channel. A stovepipe functions on its own, individually. See the article : Plumbing employee arrested, charged with murder in triple shooting. It does not share a connection with other pipes, gutters or outlets, so it is more prone to overload, crack or otherwise deteriorate.

If you let your applications drink from the fire hose of modern data ubiquity, you don’t want them exposed to all that power with the vulnerability of an archaic system underneath.

“Stovepipes are a great way to support unique missions, such as automating a single business process or reporting the activities of a single business team. But to be truly insightful, you need the complete picture of all your business processes and teams. In the world of the cloud, the web and modern applications, the mantra I fear should be (and cover your ears if you must) stovepipes is doomed,” said Shawn Rogers, vice president of analytics strategy at TIBCO.

The real problem for today’s technology platforms is the fact that many organizations will use legacy relational databases with stovepipe architectures. In contrast, the cloud computing model of virtualized and abstracted interconnected systems is almost the antithesis.

Stovepipes have a single channel. In contrast, the cloud has a potentially infinite number of distributed scale-out nodes and channels in its architectural makeup.

“While the cloud has an inherent technological advantage, the data passing through it also needs to be harmonized. Include customer data in sales and marketing or accounts and receivables. When those data sources are throttled, they grope in the dark. Either way, to delight your customers and when you interact with them, you must first harmonize your customer data using master data management to provide a clear channel through which the company can breathe,” added Rogers of TIBCO.

To see also :
Mark Radcliffe’s entrepreneurial spirit was evident when he lied about his age…

An impedance mismatch

The end result of legacy data structures trying to serve higher-level cloud-based expansion is an impedance mismatch. See the article : 3 plumbers rescue man who fell into creek. Both constructs cannot exist in the modern IT universe without a leak, blockage, or catastrophic rupture.

This subject is close to Jim Walker’s heart. In his role as VP of product marketing at Cockroach Labs, Walker talks about leveraging cloud data orchestration technologies, such as the much-famous Kubernetes.

Walker reminds us that the old data systems of the past were not built to work in the distributed information universe in which we exist today. Even worse, although organizations will try to adapt, adapt and change these legacy systems, the inevitable result is the creation of a bottleneck, or worse, a single point of failure for the application.


“Running a NoSQL database on Kubernetes is a finer tuning that can help overcome some of the challenge here, but organizations will likely still face transaction consistency issues. The stovepipe architecture of our legacy relational databases contradicts the distributed scale-out architecture of Kubernetes because they are not built with the same architectural primitives,” said Walker.

This may interest you :
Plumbing and Water Management Systems Industry Outlook 2021 The outbreak of covid-19…

A contained answer to the challenge

Much of the tech industry has looked at containerization as a means of building the next era of cloud-native technologies, but what everyone realized is that when applications are containerized (i. To see also : Plumber’s union ordered to grant Kelowna woman membership after discriminatory denial – Kelowna Capital News.e. built from smaller individual individual components), our databases te . Are legacy databases built with the kind of modern modular interchangeability and connectivity that today’s software application development engineers can use? Well, in a word, no.

Walker of Cockroach Labs advises that a forward-looking, future-proof database should ultimately look and feel like a traditional database, while taking advantage of all the benefits of a cloud infrastructure.


“Just like parts of a car, you can replace certain parts, but the rest of the car remains the same. This is the type of architecture developers and enterprises need to consider to efficiently develop, deploy, and maintain software containers,” he says.

To see also :
Cy de Cynic gave me a lift to the club, and at…

From stovepipes to internet pipes

If we think about the way forward here, we can use a lot of what we learned in the stovepipe era (the last few decades of the last millennium…and possibly further back in some cases) because the absolute core logic of data movement is still there. is . In tech circles we still call the internet a pipe and we need it to be as pipe-like as a stovepipe, we just need it to be smarter and stronger.

In the future we may think about opening wide and drinking from the data fire hose in bigger gulps, the stovepipes will crumble and new plumbing will be installed.

Comments are closed.