Complex RDF takes lot of time from Jena

[denevers]

Jena takes a lots of time to compile small RDF model and it might now scale very well when we add more data. This is particularly an issue when using EmbeddedStore. We are using full OWL reasoner, maybe we could settle for something less demanding (we need a limited set of functionnalities like symmetrics, inverseOf, transitivity and inheritance (others ).

Another option is to NOT use RDF and rely on a clever relational database for the whole database and just pull RDF from it to create the landing page.

[dblodgett-usgs]

I would be OK setting up a requirement to use an external object store as long as we can get it working as a simple dockerized resource. That said, whatever gets the job done with minimal additional for this phase of the project is probably OK. Let's get the pilot area working then think bigger.

[denevers]

we are exploring docker for GIN right now (already have the infrastructure in place) and from what Alex could gather, (large) database in docker is not the best idea. Maybe db API in docker and db on backend or maybe shared resources .. anyway - we are exploring this.

[dblodgett-usgs]

Docker should scale up fine as long as it has access to resources. See the open pull request for a docker container for this project. Works like a charm. I do:

mvn package war:war
docker-compose up --build

And I have a localhost app running.

[denevers]

yes, my point essentially. ideal for GSIP. even better GSIP with DB outside the container.

[jvanulde]

See #27.