Ontotext is pleased to announce Ontotext Platform 3.6, which makes it even easier for DevOps teams to deploy and operate the Platform. One of the major functionalities we have added is the ability to validate that the generated GraphQL schema corresponds to the data stored in the knowledge graph. Another improvement is that the Ontotext Platform Workbench now allows users to be much faster when visually “constructing” correct GraphQL queries and mutations.
Read on to learn about all the improvements featured in the new release.
Schema Validation
At the heart of Ontotext Platform 3 are the Semantic Objects Service, which implements an efficient GraphQL to SPARQL translation, and the declarative way of providing GraphQL APIs over knowledge graphs. Thanks to it, application developers can efficiently work with knowledge graphs without having to develop back-end APIs or complex SPARQL. This is achieved by introducing the Semantic Object Modeling Language schema and by enabling its generation based on the RDF ontology model.
In Ontotext Platform 3.6, we have improved the schema generation process by introducing schema validation against the available data in the knowledge graph. The new type of validation reports inconsistencies between the schema and the available data such as cardinality violation, range mismatch, multiple ranges, multiple parents, etc. In this way, it is much easier for data experts to spot schema or ontology model errors, or data inconsistencies and to improve the overall query performance.
GraphQL Query Builder
Another exciting new feature in the new release is that we have decided to include the GraphiQL Explorer in the Ontotext Platform Workbench. This has been based on extensive user feedback about the usability of writing GraphQL queries and mutations when using big and complicated schemas.
The GraphiQL Explorer is an interactive explorer plugin for GraphiQL. It allows users to visually “construct” queries and mutations without having to know the specific syntax and makes it much easier to write such queries.
Deployment and Operations Improvements
Last but not least, we have continued to boost the deployment and operation efficiency of the Platform. We have upgraded some of the key components (GraphDB, FusionAuth and Elasticsearch) to newer versions and have introduced additional improvements such as:
- switching to official Helm charts for Kong, Grafana and InfluxDB;
- introducing separate Helm charts for the specific Platform services;
- removing Ontotext Platform CLI (OPCTL) provisioning from Helm;
- removing MongoDB deployment;
- switching to dynamically provisioned persistent volumes;
- improving conditional deployment and global configurations;
- adding role-based access control (RBAC) schema provisioning.
To see the reasons behind these changes and to upgrade to the new version, just go to our Migration Guide and follow the instructions.
Get ready to take advantage of all new Ontotext Platform 3.6 features!
For more information, contact Doug Kimball, Chief Marketing Officer at Ontotext