VOOZH about

URL: https://thenewstack.io/dataops-is-more-than-devops-for-data/

⇱ DataOps Is More than 'DevOps for Data' - The New Stack


TNS
SUBSCRIBE
Join our community of software engineering leaders and aspirational developers. Always stay in-the-know by getting the most important news and exclusive content delivered fresh to your inbox to learn more about at-scale software development.
REQUIRED
It seems that you've previously unsubscribed from our newsletter in the past. Click the button below to open the re-subscribe form in a new tab. When you're done, simply close that tab and continue with this form to complete your subscription.
The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our Terms of Use and Privacy Policy.
Welcome and thank you for joining The New Stack community!
Please answer a few simple questions to help us deliver the news and resources you are interested in.
REQUIRED
REQUIRED
REQUIRED
REQUIRED
REQUIRED
Great to meet you!
Tell us a bit about your job so we can cover the topics you find most relevant.
REQUIRED
REQUIRED
REQUIRED
REQUIRED
REQUIRED
Welcome!

We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.

What’s next?

Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.

Follow TNS on your favorite social media networks.

Become a TNS follower on LinkedIn.

Check out the latest featured and trending stories while you wait for your first TNS newsletter.

PREV
1 of 2
NEXT
VOXPOP
As a JavaScript developer, what non-React tools do you use most often?
Angular
0%
Astro
0%
Svelte
0%
Vue.js
0%
Other
0%
I only use React
0%
I don't use JavaScript
0%
Thanks for your opinion! Subscribe below to get the final results, published exclusively in our TNS Update newsletter:
NEW! Try Stackie AI
From clobbered drafts to real-time sync
Apr 14th 2026 10:00am, by David Moore
TypeScript 6.0 RC arrives as a bridge to a faster future
Mar 14th 2026 9:00am, by Darryl K. Taft
Mastra empowers web devs to build AI agents in TypeScript
Jan 28th 2026 11:00am, by Loraine Lawson
2020-12-07 11:46:49
DataOps Is More than 'DevOps for Data'
feature,

DataOps Is More than ‘DevOps for Data’

“DataOps is taking that management of the data, using it correctly with the correct tooling, whether it’s Kafka or Pulsar, and lifting it up a level and combining it with the strategy and applying governance and security around it.” 
Dec 7th, 2020 11:46am by Emily Omier
👁 Featued image for: DataOps Is More than ‘DevOps for Data’

As the name suggests, the fast answer to “what is DataOps?” is that it’s DevOps for data workflows. As data workflows have become increasingly cloud native, the relationship between data engineers and operations has started to look more like the relationship between dev and ops in a DevOps world — thus the name DataOps. If you build a data product, you need to monitor it, update it and patch it, just as you would need to do with a software product.

“I think what we’re seeing is that everybody, every organization needs to handle data in a better way, especially as real-time data is on the rise,” said Andrew Stevenson, chief technology officer at Lenses.io. “DataOps is taking that management of the data, using it correctly with the correct tooling, whether it’s Kafka or Pulsar, and lifting it up a level and combining it with the strategy and applying governance and security around it.”

Stevenson thinks that DataOps goes far beyond just bringing data engineering and operations together, however. True DataOps is about more than just managing the flow of data — it’s also about ensuring everyone involved knows why the data workload is running and what the desired business outcome is. According to Stevenson, understanding business logic is key: although traditional DevOps metrics like speed and resiliency are part of DataOps, too, the companies that do it well are bringing data engineers together with the people who want to use the data, who have some business need that requires data. That relationship is more important to DataOps than simply speeding up the data pipeline. Though that speed is important, too.

Making Data Jobs Faster

Processing data has not traditionally been something that companies expect to do quickly. “We got a little comfortable with data procrastination,” explained Patrick McFadin, vice president of developer relations at DataStax. “It was like, my Hadoop job will run for a month, I’m okay with that. Now it’s ‘how fast can we get things done.’”

In a DataOps world, that kind of delay isn’t acceptable, any more than it would be for a DevOps team to wait a month for continuous integration testing. Instead, teams are looking for ways to optimize their data pipelines and make sure that they are running as fast as possible.

“When I think of DataOps, I think of everything that related to the orchestration and collaboration on the data journey,” explained Douwe Maan, project lead at Meltano, an open source data integration platform by GitLab.

Speed of Change

Driving this change in how data is processed is the need for business leaders to use data inputs in everyday decisions. It used to be that running a Hadoop job for a month was fine, because the end result was for a quarterly report made to the company’s executive board. Now, though, executives expect information on an hourly or at least daily basis. This has been especially critical for companies as they navigate the changing markets over the past eight months. Companies that had prioritized digital transformation, including using DataOps to improve the speed of data workflows, have been able to adapt much faster and roll out new features quicker, McFadin said.

He gave a concrete example: Target. “They were doing well as a retailer as well as an e-retailer,” McFadin said, about the pre-pandemic situation. “When the shutdown happened, they were able to quickly shift to curbside pickup. It was easy for them to do. All their stuff runs on a Cassandra database, and they were able to scale it when they needed to because everything was already in place. The DataOps people were jamming.”

Just Another XxxOps?

“The biggest misconception about DataOps is that it’s just another ‘Ops,’ there’s DevSecOps, MLOps, etc,” Stevenson said. “There’s also a misconception is that you can literally just take a tool and that one tool will solve everything and give you DevOps. We see the same thing with DataOps. There’s a set of best practices but it’s also a cultural shift.”

The key to success with DataOps, everyone agrees, isn’t even about following a specific set of best practices or a precise formula for optimizing the data pipeline. Sure, pipeline optimization is important so that data analysis doesn’t become a bottleneck in the organization, but the ways that companies use data is so varied that it’s hard to put your finger on a one-size-fits-all formula.

“You have to understand the business,” McFadin said. He cited Home Depot as another company that has used DataOps to give customers a better digital experience. Instead of just being a place to pick up screws and lumber, the company invested in creating a digital experience and did so with an IT and data team that intimately understood not just how to make data pipelines fast but how data products could be applied to meet a customer need. A customer in Home Depot can look up a product and see what aisle and row it’s in. “They have a keen understanding of the business but they are also playing with these really cool things,” McFadin said. “The DataOps people are the ones who understand how to connect A to B.”

The Technical and Cultural

DataOps will always have a technical element, largely, Stevenson said, around selecting the right tools to both optimize the pipeline and allow collaboration between data engineers and subject matter. Nonetheless, a big mistake companies when trying to adopt DataOps is focusing too much on the technology.

“They pick a technology and focus purely on that,” he said. “But what’s the strategy? What’s the governance? What about tooling? What about security and who can and can not access the data?”

And then, of course, DataOps can’t just be about a fast pipeline — there’s that “ops” part. Thinking about scaling, updating and monitoring also has to be part of the equation.

Enterprises that have adopting DataOps are thinking these questions through ahead of time, ensuring that there’s a clear business rationale for whatever data products are being built, that they can operate them in production and that the data pipeline doesn’t become an organizational bottleneck.

Feature image via Home Depot.

TRENDING STORIES
Emily helps open source startups accelerate revenue growth with killer positioning. She writes about entrepreneurship for engineers, and hosts The Business of Open Source, a podcast about building open source companies.
Read more from Emily Omier
SHARE THIS STORY
TRENDING STORIES
SHARE THIS STORY
TRENDING STORIES
TNS DAILY NEWSLETTER Receive a free roundup of the most recent TNS articles in your inbox each day.
The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our Terms of Use and Privacy Policy.