Deployment Architecture
Deploy OntoPop to the Microsoft Azure cloud computing platform, integrated with Azure managed services including Azure Key Vault, Azure Storage, Azure Service Bus, Azure Functions and Azure Web Apps.
Please note that the OntoPop backend open-source software project, which includes the event-driven data pipelines and APIs, is undergoing extensive redesign and refactoring as part of OntoPop Community 3.x in order to improve performance, security, extensibility and maintainability. As a result, the documentation on this page will be significantly updated. Please refer to the OntoPop Roadmap for further information.
Overview
The following diagram illustrates an example deployment architecture when deploying to the Microsoft Azure cloud computing platform and integrated with Azure managed services including Azure Key Vault, Azure Blob Storage, Azure Service Bus, Azure Functions and Azure App Services (Web Apps).
Azure Managed Services
In the example Azure deployment architecture above, we deploy OntoPop's Spring Boot API applications to Azure App Services (Web Apps), integrated with the following Azure managed services.
| Service | Example Azure managed service |
|---|---|
| Graph Database | Azure Cosmos DB (Gremlin API) |
| Messaging | Azure Service Bus |
| Object Storage | Azure Blob Storage |
| Relational Database | Azure SQL Database |
| Search Engine | Azure Cognitive Search (formerly known as Azure Search) is the native managed search service of the Azure cloud computing platform. Whilst it is supported by OntoPop, at the time of writing it is not recommended due to the fact that it only supports pre-defined fields. In other words, the search index schema must be explicitly defined, along with EDM types, prior to indexing and there is no support for dynamic field creation. Given the nature of ontologies and the fact that new OWL object properties and class properties may be added during their normal iterative development life cycle, it is not feasible to continuously and explicitly define search index schema fields after every change to the ontology. Therefore in the example Azure deployment architecture above, we integrate OntoPop's search services with an Elasticsearch cluster managed via Elastic Cloud. |
| Secrets | Azure Key Vault |
| Serverless Functions | Azure Functions |
| Triplestore | At the time of writing, the Azure cloud computing platform does not offer a native triplestore managed service. Therefore in the example Azure deployment architecture above, we integrate OntoPop's triplestore services with the open-source Apache Jena (Fuseki) triplestore (deployed either to an Azure virtual machine or deployed as a Docker container). |