3 ms·

Thanks, that's a solid resource that I wasn't aware of. It's interesting how you're generating Java stubs using your K Schema format. I like the idea of using

Thanks, that's a solid resource that I wasn't aware of. It's interesting how you're generating Java stubs using your K Schema format. I like the idea of using RDF as a universal data model. I buy the power of graphs in general, and RDF seems much more useful than a generic object-property graph thanks to built in support for namespaces and reasoners. My hesitation about the concept comes from concerns around performance and implementation difficulty. It looks like you've built some solid tools to ease the initial modelling challenge, how are you addressing the performance challenges? That is, once you pull several data sources into a huge graph, how do you keep query speed up?

PaulHoule 10y ago
The "huge" graph is only virtual. It exists in principal but you are not going to materialize the whole thing when it gets huge. Or if you are you are going to do it with stupid Hadoop methods, not by trying to grow traditional databases up. Trying to get the whole world inside one "envelope" is scalability pornography, i.e. SAP HANA. Realistically you create the indexes and data structures necessary for your workload, it is not that different from any other technology except in the case of RDF the math is known.