MillenniumDB: Property graph and RDF engine, still in development
1–10 of 43 posts
Re: MillenniumDB: Property graph and RDF engine, still in development
#2Re: MillenniumDB: Property graph and RDF engine, still in development
#3Re: MillenniumDB: Property graph and RDF engine, still in development
#4Re: MillenniumDB: Property graph and RDF engine, still in development
#5Re: MillenniumDB: Property graph and RDF engine, still in development
#6Re: MillenniumDB: Property graph and RDF engine, still in development
#7What is a domain graph?
Re: MillenniumDB: Property graph and RDF engine, still in development
#8Re: MillenniumDB: Property graph and RDF engine, still in development
#9Use of other systems involves factoring tradeoffs and considerations that are probably not the best for the newcomers. For example, qLever mentioned here is good in query performance and relative disk use but once the import is done, it's essentially a read-only DB and completely unsuitable for a typical OLTP scenario.
Having said that, the Chilean research group that is driving the development of MilleniumDB is very well-regarded in the RDF/semantic web querying space.
Re: MillenniumDB: Property graph and RDF engine, still in development
#10Both seem to have arrived at the stage of transitioning from research to production code.
Very exiting for those of us providing our data in RDF and exposing Sparql.
AWs Neptune analytics is also very interesting, allowing Cypher on RDF graphs. Even the Oracle inbuilt RDF+Sparql seems to have improved greatly in 23ai.