Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
netflixtechblog.com
Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
1–10 of 108 posts
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#2[flagged]
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#3[deleted]
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#4Why would Netflix engineering host on Medium? Very odd. And you just lose readers to the popups but you don't benefit from their discovery much either.
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#5> ... RDF ... SPARQL ... OWL ...
I want to believe. (really! I think that's hugely underestimated tech).
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#6I really believe a common vocabulary makes sense. But it is hard, very hard as you spread across organization (some to be bought and integrated), business processes and time. As soon as it comes to generating stuff things become hard. One may be able to generate interfaces between two systems but which enterprise has only two layers? Yes, if all knowledge is captured in the central catalog we may be able to do it but who builds this perfect database and maintains it?
Attempts to do this and survived either restricted themselves to being very abstract or limited their scope to specific use cases.
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#7Doesn't Google achieve the same result with Protobuf?
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#8From the: What is ERM? We don’t need DBAs. Why use a SQL DBMS?-department.
On a more serious note, scaling of a distributed system and the associated teams necessitates handling one’s data systematically. Fixing it afterwards looks painful.
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#9I really believe a common vocabulary makes sense. But it is hard, very hard as you spread across organization (some to be bought and integrated), business processes and time. As soon as it comes to generating stuff things become hard. One may be able to generate interfaces between two systems but which enterprise has only two layers? Yes, if all knowledge is captured in the central catalog we may be able to do it but…
The problem I've seen is that you define your corporate entities, but then you have these systems in other divisions which need to extend it. Whether their division's special attributes get promoted to the corporate entity for everyone to use brings in politics and optimism. And making an update to a corporate-scoped entity then means you need solid change management.
IMO they can be very valuable in terms of reduced friction and costs, if you do it right and have enough rigor/discipline in the organization. Netflix might.
Re: Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix
#10Doesn't Google achieve the same result with Protobuf?
It's more like Google Knowledge Graph