DataOps Is More Than Devops For Data, Delphix CTO Says

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

Summarized by: Marcos Lozano García

“DataOps Is More Than DevOps For Data,


Delphix CTO Says”
(Jack Vaughan, Search Data Management, 22 February 2019)

“DataOps today: Essentially, the problem to be solved is data delivery. It's


about people, practices & breaking apart departmental silos as much as it's
about technology”

https://searchdatamanagement.techtarget.com/feature/DataOps-is-more-than-
DevOps-for-data-Delphix-CTO-says

Data operations are increasingly used as part of projects that put data at the
center of development. 1) DataOps is about the flow of information in the data &
how you manage it in a self-service fashion: A) capture data. B) secure data. C)
to curate, prepare & move data. D) to deliver it giving end consumers not just
access to the data, but actual control over it. 2) Nowadays everybody has a
different pattern & a different set of practices around DataOps: A) analytics or AI
or ML. B) application development. 3) figure out ways to use data to deliver new
capabilities and insights. It all comes with competing in the market: A) IT
methods just aren't cutting it. They're too slow, they're too fragile, they're too
insecure (e.g., data breaches, poor application quality or stalled projects). B)
DataOps is about finding ways to really manage that end-to-end delivery &
lifecycle of data & do it in a way that's fast & efficient & secure. 4) Eric
Schrock, Delphix CTO: “With DataOps, you start to think in terms of how you
get data to the people who need it while ensuring it is secured. When there is
one set of people who are focused on making that happen, it brings together
the managers & the consumers of that data”.

[TAGs: data ops, AI, machine learning, data insights automation, dev ops, data
management, data innovation, data delivery, IT, silos, DBA]

FACTS & FIGURES

 Technology is progressing. Actually, refreshing a database now takes


three minutes instead of three weeks.

THESES/ MAIN IDEAS

 Data operations are young compared to DevOps, but it is increasingly


used as part of projects that put data at the center of development.
 DataOps is about the flow of information in the data & how you manage it
in a self-service fashion.

 For now, everybody has a different pattern & a different set of practices
around DataOps. Some of them are geared more toward analytics or AI
or ML, others toward application development.

 The challenge is how to get data everywhere it needs to be in the


enterprise.

 DataOps is about finding ways to really manage that end-to-end delivery


& lifecycle of data & do it in a way that's fast and efficient & secure.

 With DataOps, you start to think in terms of how you get data to the
people who need it while ensuring it is secured.

SCENARIOs:

 DataOps has a similar challenge, & while it's gaining momentum, it's
definitely still nascent.

 We're starting to see practices & techniques start to come together &
start to try to solve problems that we see with data in the enterprise.

 Everyone's becoming a software company.

RECOMMENDATIONS

 DataOps requires you to look at all the pieces needed to capture data;
secure data; to curate, prepare & move data; & finally, to deliver it, giving
end consumers not just access to the data, but actual control over it.

 DataOps it is still developing, but at the end of the day, what it's about is
looking at not just technology, but also the people & process.

You might also like