Skip to main content

EPOS Platform Architecture

The EPOS Platform is built as a robust, scalable, and modular microservice-based architecture. This design allows for independent development, deployment, and scaling of individual components, ensuring flexibility and resilience.

This document provides a high-level overview of the platform's architecture, illustrating how its various services interact to provide a unified geospatial data integration system.

EPOS Platform Architecture Overview

Core Components Overview​

The EPOS Platform is composed of several interconnected microservices, each responsible for a specific set of functionalities:

  • EPOS API Gateway: The central entry point for all client requests, routing them to the appropriate backend services.
  • External Access Service: Handles interactions with external geospatial services, including data retrieval and initial processing.
  • Converter Service: Responsible for transforming data payloads from external services into formats compatible with the EPOS GUI.
  • Ingestor Service: Manages the ingestion of metadata (e.g., from .ttl files) into the system's metadata catalogue.
  • Backoffice Service: Provides administrative functionalities, including metadata management and system configuration.
  • Resources Service: Manages service descriptions and catalogue information.
  • RabbitMQ: Facilitates asynchronous communication between services, ensuring efficient and reliable data processing.
  • Metadata Catalogue: The central repository for all service descriptions and catalogue information.

Key Architectural Principles​

The platform's design adheres to several key architectural principles:

  • Microservices Design: Each service is loosely coupled and focuses on a single responsibility, enhancing maintainability and scalability.
  • Extensibility: The plugin-based Converter Service allows for easy integration of new or custom data formats.
  • Scalability: Services can be scaled independently to handle varying loads, ensuring high availability and performance.
  • Standards Compliance: Built upon open standards (e.g., OGC, DCAT-AP) to ensure interoperability and broad compatibility.

Data Flow (High-Level)​