bertails

4 ms·

1.
by bertails 1y ago
"REST" is our industry's most successful collective delusion: everyone knows it's wrong, everyone knows we're using it wrong, and somehow that works better than being right.
2.
by bertails 1y ago
We have a little bit of runtime checks in the Java projections but it's still tied to SHACL/SPARQL through the Jena library. We are exploring ways to keep using SHACL at scale for advanced data profiling, and also try to identify
3.
by bertails 1y ago
It is important in UDA for the data models to be part of the same knowledge graph as the data container representations and the mappings, and eventually the instance data too. Our metamodel Upper is strongly inspired from RDFS, SHACL, and O
4.
by bertails 1y ago
Exactly. In UDA, each Movie entity belongs to a specific business domain. Universality isn't an inherent truth, it's a social alignment within a group, useful only to the extent that it helps solve shared problems.
5.
by bertails 1y ago
This does look interesting. Does the Ash Framework yield a knowledge graph? How good is it a cataloging existing data containers?
6.
by bertails 1y ago
UDA does not believe in the existence of universal data entities. We embrace the idea that 2+ teams may have different opinions on how to represent the world. We are focused on the discovery of existing entities across systems and their reu
7.
by bertails 1y ago
We joke internally that Upper is like "RDF: The Good Parts".
8.
by bertails 1y ago
> The whole point of GraphQL is to create a unified view of something, not to have 23 different versions of "Movie". GraphQL is great at federating APIs, and is a standardized API protocol. It is not a data modeling language. W
9.
by bertails 1y ago
Great question. It really depends on the projection. For example, the projections to GraphQL and Java are mostly limited to what can be expressed there. But the projection to SHACL has access to all of SPARQL Constraints, which is what&#x27
10.
by bertails 1y ago
> I wonder how they deal with versioning or breaking changes to the model. Versioning is permission to break things. Although it is not currently implemented in UDA yet, the plan is to embrace the same model as Federated GraphQL, which h
11.
by bertails 1y ago
> Of course, details on "Upper", PDM, and Sphere are well - missing, but at least I have concepts to focus on :) Definitely coming soon ;-)
12.
by bertails 1y ago
The price is in the 500+ domain graph services federated into our GraphQL enterprise gateway, which will all be exposed to Sphere through UDA. That's real.
13.
by bertails 1y ago
> How does this relate to domain-driven design? The "Domain" in `upper:DomainModel` is the same D as in DDD (Domain-Driven Design) as the D in DGS (Domain Graph Service). > in DDD it's kind of expected that the same con
14.
by bertails 1y ago
> Would also be more than happy to skip the whole GraphQL end of it. Netflix benefits from a large GraphQL ecosystem with federation, which is why it's so central in UDA from day 1. But adding a projection to "REST" would
15.
by bertails 1y ago
UDA embraces the duplication of models: it's a fact of life in the enterprise. That is why "domains" are first-class citizen. We believe that good discovery capabilities will increase reusability of the domain models. Our nex
16.
by bertails 1y ago
> It is fundamentally a business problem, rather than a technical problem, but it has impact on development speed, so it's secondarily a technical problem. Yes it is a "fundamentally a business problem" but we believe it c
17.
Model Once, Represent Everywhere: UDA (Unified Data Architecture) at Netflix(netflixtechblog.com)
9 points by bertails 1y ago|0 comments