The core theme is that achieving both speed and robust data management practices in modern data architectures, like data mesh, requires a strong focus on the developer experience, facilitated by a self-service data platform and DataOps principles.
Mind Map
点击展开
点击探索完整互动思维导图
okay guys um ready to go uh my name is
Paul Rankin um xrush X IBM X Accenture
um I'm now uh freelance actually I do a
lot of uh consultancy for nor more
organizations um today I'm going to talk
a little bit about the developer
experience um especially when it comes
to data products distributed
architecture data mesh if you like a
little bit in there um what I see
working with a number of organizations
today is really two pass patterns yeah
when it comes to this kind of stuff is
is really one you have your very Central
you know monolithic it type of pattern
usually centralized built around a data
warehouse a data Lake you know very
stable highly skilled team of developers
data Engineers um dbas Etc and then you
have the the complete opposite which is
essentially very decentralized
business-led usually right um people
working with uh minimal data management
practices let let's call it like that
but it's fast yep and I think this is
where I see business is really
struggling today is they want fast yep
but they also from an IT perspective
want good data management practices they
want governance they want security you
know they don't want to be restricted
and blocked by those traditional it uh
governance processes so you know how do
we get businesses to be be fast and to
be secure to be governed sticking to
these good data management practices
because it shouldn't be an either or
right I mean businesses can expect to go
fast but also go fast you know well and
governed so you know you probably be
familiar with this scenario and this is
what you you know certainly I'm finding
in a lot of companies I'm working with
now is you know business ask it yeah we
need our data to solve a certain problem
we need it now we need to go fast and it
are kind of asking them well we need to
follow the processes please send your
requirements we'll let it to the backlog
and you know usually what happens is you
know it say well 6 months later we're
ready to start by that time business
have said no no we're we're just going
to go on our own we're going to get our
good friends from Accenture TCS to help
us here and you know hey Presto two
weeks they've uh they've got a team in
and they've gone it alone I mean any
anybody familiar with with this it's
probably yeah quite a familiar process
all right so introducing data mesh or
data products uh domain ownership
whatever you want to call it now this
was this was us uh you know three years
ago um at rash my good friend Omar is in
the audience here um we thought that
data mesh would solve all these problems
for us yeah at rash we were very slow we
had you know very long uh life cycle
very long release cyes Data Business
wanted to go fast it were a little a
little bit slow so we thought bring in
the data mesh guys we're going to uh
work with dams we're going to work with
thought Works everything's going to be
Rosy yeah what I find now today speaking
of other customers they think data is a
product and I get a lot you we just
change our data sets to data products
we'll just rename them everything will
be fine self service data platform we've
got AWS no problem that's covered uh you
know domain ship now what usually
happens and I see is the IT department
split themselves into verticals so they
have you know business-driven verticals
or a business align verticals and this
is what a lot of people see as as domain
ownership nowadays and I think it's
because it's easier to to do this rather
than facing the the difficult part
Federate governance actually speaking to
a lot of businesses they don't actually
know what it means for one and even
though they think they know what it
means a lot of them think it means that
we don't have to follow the govern it
governance anymore we can absolutely go
on our go on our own okay
so you know by companies that want to
follow this new transition to domain
ownership to data products usually what
happens is yes cross functional teams
arrive because that's clearly how they
can deliver data products how they can
deliver these you know this new way of
working and what I see in a lot of
companies is is developers are now you
know on board to these cross functional
teams and the business or the managers
of these teams are saying okay here's
all our tools y please build us these
data products and you know here's our
AWS account here's our get repository
here's our data quality tools etc etc
etc and you know you what do you expect
them to do you know it was okay in when
they were part of a central team a
central it team because then they could
work with each other it was very
centralized High highly skilled
developers but as soon as you move to this
this
distributed distributed architecture
distributed ownership these developers
are kind of brought in and left on their
own a little bit and this is what I find
uh today that people are moving to this
and I really feel sorry for developers
that you know they're having an absolute
nightmare at the moment and you know
just by moving to data product alone and
moving to cross functional teams are not
going to solve your problems and this is
where I find the developer experience is
so important to hear yeah now
introducing the self-service data
platform and and this is key to the
developer experience basically what
we're trying to do right here is we're
trying to abstract a lot of the
complexities away from these developers
we what we want is the developers to
come in have this guided developer
Journey yeah and I'll show you this in a
minute and not have to worry about well
how am I going to connect to my IAP
system how am I going to be able to
secure my data at a granular level how
am I going to meet all these governance
policies that I need to regulatory meet
you know um we as a a data platform team
essentially this is the the IT team
reborn as this enablement team if you
like we need to then be a service
provider to these data product teams we
need to be enable these developers to be
fast but also to build in a secure and a
a governed with good data practice good
data management practices all right and
and this is how I portray it a lot of
you may have seen that have listened to
me before have seen this portray of this
three tier data platform where it's all
focused around these uh these Persona
Journeys yeah and what we're going to
focus on a little bit now today is this
um this developer Journey here so if you
think about the developer Journey I've
tried to I mean this is one of the the
things we we do with a lot of customers
is is portray and visualize this
developer Journey because developers
most developers now they get onboarded
they're asked to build data products and
they don't yeah they may know the
tooling they may know you know
technically how to build it but they
need to understand you know what the
journey is and building a data product
clearly is you know involves a lot more charactertics
