Amount of data graphs

[richarddi...@gmail.com]

Good morning,

Do technical of practical reasons exist for limiting the amount of data graphs to e.g. 1000? From a data governance (DQ, corrections etc) perspective I evaluate a graph architecture with more data graphs than one would expect.

Richard D

[Taryn Madey]

Hi Richard, can you confirm the limit you are referring to? Limit on the amount of data graph collections you can have or limit to the search results in a data graph?

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/d24f0a64-3d29-4ea0-b6b8-313f3331ff49n%40googlegroups.com.

--

Taryn Madey

Development Manager

TopQuadrant Inc.

Raleigh, NC

[richarddi...@gmail.com]

We mean the "Limit on the amount of data graph collections" (as being the number of graphs, bad English, sorry) . We might get several hundreds data graphs. When this will become a problem we could use Shacl for what we want; 'perfect data governance'.

[Holger Knublauch]

Hi Richard,

one thing that definitely will slow down almost all operations is if you have large import closures, i.e. a graph that owl:imports many other graphs (transitively). This is because all queries will need to go against the various subgraphs individually and the results then merge (we do not use/have a shared index across all these graphs).

OTOH only some operations will become slower if you have hundreds or thousands of individual graphs that are largely independent. For example the page to browse all Data Graphs will become slower. I am aware of customers that have hundreds of graphs. If you run into significant problems in that area then please let us know.

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/b96d782a-1c8d-4cac-a642-d263491b344en%40googlegroups.com.

[robatki...@gmail.com]

FYI We use hundreds (and expect thousands) of graphs and have developed additional modules to deal with automation and replicability of state.  Some of the UI browsing paradigms don't scale, and we provide alternative approaches to discovery based on modular governance domains and inter-graph relationships.

As Holger says, the key is in knowing what and when to include in import closures depending on what you need to do with the graphs.

Rob Atkinson

SURROUND Australia.

[richarddi...@gmail.com]

Rob, Holger,

Thank you for the feedback. I will assume that no negative issues will occur and design a proof of concept which will result in many datagraphs that are managed through EDG and and external application.

regards, Richard