[transcript]

32:07 made almost completely out of ivory. Bingo, bingo. I'm not 32:23 using ivory pianos. I was my husband's piano. I never

[transcript]

15:59 me y yeah, my heck, yeah, my hecker. I'm with 16:04 a whole bunch of hackers. We're in a Hecker quad here.

[transcript]

43:07 Katie penis what is in ivory right now? To preserve it.

[transcript]

1:02:08 Weil es ist so ein Hecker, schleichting auch. 58:06 Und ich spiele im Spielen Hecker oder eine Heckerin. 1:01:59 ich bin auch so ein Hecker und habe mir das Gefühl, dass das eigentlich egal ist, was man macht.

[transcript]

07:08 Ich spiele zum Beispiel lieben gerne so ein koreanischem Hecker 16:19 eine ganze Stadt aus rekrutierbaren Menschen, die du rekrutieren kannst in dein Hecker 22:22 in diesem Hecker Heideraut, wo dann die drauf, aber es ist wirklich so egal, dass das lustige

[transcript]

51:46 Ich bin Miniatur, Hecker, innen. 51:42 Ich kann das ja sagen, ich mache es in wie eine Geschichte über die Hecker.

[transcript]

03:24 hören, weil das dann nicht ständig, weiß nicht Impfstoff, Suche, 3D-Drucker, Hecker, die

[transcript]

15:03 beautiful ivory car with a red interior and that's kind

[transcript]

14:20 got high walls with ivory growing in, lots of military 22:24 gold plated rifles and some ivory handled pistols collector's pieces

[transcript]

08:46 You think to yourself, you take some ivory proof and

[transcript]

46:01 you're like seven inch Ivory multi speed hard plastic vibrator

[transcript]

2:15:25 Merkt man ja auch manchmal in den Diskussionen, das wird Wissenschaft oft vorgeworfen, so ihr Ivory Tower, ihr Elfenbeinturm.

[transcript]

37:24 and Ivory. No, too afraid and too immature to actually

[transcript]

20:48 that sells black market ivory combs. I don't want to

[transcript]

14:58 made of ivory. I've contributed to the ivory ivory trade. 02:30 model for Ivory Soap. Can you imagine that eleven months old?

[transcript]

02:01 nice slacks, I brushed the mustache with my ivory comb,

[transcript]

19:42 some sort of Victorian, some sort of merchant Ivory movie. Right, yes,

[transcript]

04:33 So eine halbversieburgte hecker in ingenieurin und die zum beispiel die hat tatsächlich mehr als zwei drei farben also die ist dann schon bisschen detaillierter aber auch weil es das modell mir hergibt.

[transcript]

07:10 Ja und am ende habe ich mir so gedacht man hätte das alles mit der hecker edek erledigen können aber gut ich bin also ich ich bin ich bin also echt amüsiert gewesen und es dauerte halt irgendwie ja.

[transcript]

00:58 dass ich da irgendwie prädestiniert für sein das weiß ich auch nicht aber gut vielleicht naja podcastende lehrkraft mit mit mit hecker space mitgliedschaft vielleicht gehör ich da dazu.

[transcript]

45:21 filled with what's called hornbill ivory, which is a hard

[transcript]

26:54 of fashion as medicine. Already, the Ivory Coast burned three

[transcript]

55:35 thirty two thousand year old ivory sculpture that is shaped

[transcript]

32:46 These goggles were carved from bone antlers or walrus ivory. Later,

[transcript]

1:25:28 for cape lions, the Caribbean monk, seal, the ivory build woodpecker. Uh.

[transcript]

18:28 Yeah, yeah, good question. So I mean, this question reminds me of another thing that we've done in software engineering over the last few years, which is moving off the monolith moving off the monolith to microservices. And what what did we do? What did every business do? So essentially, what we did is we said, okay, let's break up the monolith. It's break it up into components, but then I need to put something in between as a kind of a measurer. I mean, one of the examples that was very common was an enterprise service. of us putting an enterprise service bus where we pass around discrete small little messages to so that these different components can kind of talk to each other in a little bit of a decoupled way. And so really, this is kind of similar to what the migration path looks like for moving off a classic data platform into a little bit more of us distributed governance environment. And I'll just reiterate, and governance is just one of those pillars, right. And I think the reason why I'm choosing that is because it's usually one of the first things that people want to do put in governance strategies in their business. And you can also just imagine that, okay, this can get really complex as I add the extra pillars of data management in, but essentially the kind of the kind of experience with the migration, as I alluded to before, it's a gradual move. It's it's really saying okay, and how we Gonna start splitting up this monolith. And typically the way we did it in software engineering was say, let's identify the main components of the platform. So we would split logging out to its own service, we would split, maybe jobs out to its own service, we would split something like data access, potentially out to its own service. Now, other architectures in in micro services would say, No, no, no, like, split the service out to have all of its components sitting behind it. So logging will have a database, it'll have a data layer, because that's all it's responsible for now, whichever way you did it, it's still kind of, it's still going to help in this example. But really the the approach that we've seen our customers take because majority of our customers started out with the model if they said, Okay, we've got one central hub of data, and it's got all of our data in one place. We've got all the governance rules in there. Oh, God. It I didn't realize how complex the governance rules were across the different businesses, there has to be some way to split this up. So I would say the migration path if you've done that before, in breaking up the monolith, it's very similar to that type of situation. Now to answer the second part of it, which is about making this data available to the rest of the business, whether this is just internally or potentially to the public, once again, there's there's multiple parts of that governance plays into it, of course, access control, and things like that play into it as well. But what the hub architecture basically does, like it does with the other components is it takes what is typically a top down approach, which is how from the my white ivory tower, do I set the overarching rules for my global business on how we share data. Now, one of the beauties of the hub architecture is that it instinctively has a hierarchy within it. So a graph is just a higher fidelity version of a tree. So for example, if I'm wanting that top down approach where global says, Listen, we have a global policy on sharing data, that we can't give out anything that's personal. So, in fact, the hub orchestrator can be responsible for saying, Ah, got it. So in fact, there's some policies that the local hubs don't have any control over. They've been in, they've inherited these rules from the global headquarters or from the regional hub, and they're enforced by default, on to the localized hub. Now, whether that localized hub can then say, I'd like to override those rules. That's kind of the responsibility of the hub architecture to, to know if that's even allowed or not. But what this means is that, at least the higher level parents can say listen You might have some extra ways that you want to share data in your local hub. But from a global business, we're handing down these rules, whether you've got rules to add on top of that, or override that sub for the hub orchestrator to actually figure out if those route rules can actually are compliant with each other or not.