Updates & Improvements to the RDF Graph Database-as-a-Service

We’ve been quite busy in the last few weeks with various updates and improvements related to the RDF graph database-as-a-service (DBaaS) on the S4 platform.

As of the beginning of November, customers can use the latest GraphDB 6.5.0 database, instantly available in the cloud via the AWS Marketplace, without the need for hardware or license provisioning and software installation. The GraphDB team has added various improvements and bugfixes to 6.5.0, such as:

  • Query optimizer improvements
  • Improved special character handling
  • Improved optimiser statistics
  • Various improvements to the GraphDB Workbench, including limited access to non-authenticated users (useful when publishing Open Data sets)

The detailed changelog for GraphDB 6.5.0 is also available here.

A few important reminders regarding the self-managed GraphDB database in the AWS Cloud:

  • Developers can experiment with GraphDB on AWS for 5 days without any charges, so that they will be able to setup & configure the database and import sample data, run benchmarks, etc. before they start paying for the actual database usage
  • We have an instance migration guide that will help developers with the migration to the latest 6.5.0 database from one of the previous editions. The detailed instructions are available in the “Upgrading the GraphDB Product” section of the Self-managed database documentation
  • Ontotext and Keen Analytics are running a regular monthly webinar on GraphDB Fundamentals that provides on-boarding for developers who are new to Semantic Technology, with their first steps of using an RDF graph database. The webinar topics include: fundamentals of W3C  standards for graph databases: RDF/S, SPARQL and OWL; GraphDB reasoning strategies and graph analytics extensions such as RDFRank, Geo-spatial and Full-Text-Search; troubleshooting of most common problems

Publishing Linked Open Data Sets via S4

The fully-managed RDF graph database on S4 provided the option for developers to grant public read-only access to selected databases, so that 3rd party applications can easily access & reuse (Linked) Open Data sets without the need for API keys and authentication (which are required for any other access to the S4 services).

Recently we have improved this feature even further by making the public read-only access option more fine-grained, on the repository level (instead on the database level), so that developers can have within the same database both “public” and “private” datasets or knowledge graphs:


Note that even for repositories open to the public, the access is read-only, e.g. SPARQL queries or RESTful operations that can only read and query the data, but never modify or delete data.

Ongoing upgrade of the fully-managed RDF database-as-a-service (DBaaS)

As usual, we will gradually upgrade the instances of the fully-managed database-as-a-service (DBaaS), running on the S4 platform, to the latest GraphDB engine 6.5.0. The developers who are using the fully-managed DBaaS on S4 will be able to use the improved RDF graph database, without any service interruptions and downtime.

Next Steps

If you haven’t already done so, get your free 5 day trial of the self-managed RDF graph database via the AWS Marketplace, or register a developer account for the Self-Service Semantic Suite (S4) and get your free fully managed RDF database-as-a-service!

Marin Dimitrov

Marin Dimitrov

CTO at Ontotext
As the technological captain of Ontotext, he is leading the company on the right tech route and reserving our spot on the map of the world. His sharp mind can explain complex things in a simple way, making him an invaluable resource in semantics. Marin is a frequent speaker on semantic conferences and open data meetups at various technology related events.
Marin Dimitrov

Related Posts

Back to top