How esdlmapeditoressim/docker-toolsuite works
Main Components
• Frontend/Client Interface: ESDL MapEditor (the map-based UI) and the ESSIM dashboard.
• Simulation Engine: ESSIM for energy system simulation.
• Identity & Access Management: Keycloak to manage user accounts, roles, and authentication.
• Cloud Storage/Versioning: ESDL Drive, which maintains and versions ESDL files.
• Data Persistence:
• PostgresDB (with PostGIS) for relational storage (also used by ESDL Drive)
• InfluxDB for time series data (panel service data source)
• MongoDB for document-based storage.
• Supporting Services:
• Panel Service for visualizing time-series data via Grafana.
• Boundary Service to provide geospatial boundaries.
• Infrastructure and Deployment:
• BaseInfrastructure that provides docker-compose configurations for the databases and services, along with environment templating.
• Experimental directories that show configurations for automated deployments and for Kubernetes (indicating future scalability or alternate deployment scenarios).
• Reverse proxy (e.g., Traefik) and other tools (docker swarm, portainer) for cloud deployments if needed.
• The top-level directories such as “BaseInfrastructure”, “ESDLDrive”, “ESDLMapEditor”, and “ESSIM” directly correlate with discrete services.
• The “Experimental” folder contains various deployment setups (both docker-compose and Kubernetes manifests) that emphasize how the system can be scaled or deployed in different environments.
• UI layer where the ESDL MapEditor interacts with end users and communicates with backend services.
• ESSIM as a simulation engine that may receive scenario data from MapEditor and stores or retrieves simulation results in the database layer.
• Panel Service (and its integration with Grafana) to the underlying InfluxDB for visualization, and also indicate its connection from the MapEditor for dashboarding.
• Boundary Service as a separate microservice that provides geodata to the MapEditor.
Architectural Patterns and Design Principles
• Microservices: Many components operate as individual services (ESDL MapEditor, ESSIM, Keycloak, ESDL Drive, etc.) communicating typically over HTTP or through API gateways.
• Security and Access Control: Clearly show the IAM (Keycloak) service and its role in securing access for MapEditor, ESSIM, and even underlying APIs.
• Data Flow: Highlight that data flows from the user interface into the simulation engine and then to visual analytics (Grafana/Panel Service) while authentication and file accessing tie them together.