Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • G GeoSpatial
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 76
    • Issues 76
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Consumption Services
  • GeoSpatial
  • Issues
  • #28
Closed
Open
Issue created Jul 27, 2021 by Marten Hogeweg@mhogewegMaintainer

Define GCZ System Architecture

Define the makeup of the initial infrastructure needed for the different features (GCZ Data Manager, GCZ Data Server, GCZ Data Catalog). This infrastructure will host functional component such as:

  • Apache Ignite (for persistent storage)
  • KoopJS (used as the GCZ Data Server)
  • Geoportal Server Catalog (used as the GCZ Data Catalog)
  • ...

and be built on:

  • docker containers etc
  • API gateways?
  • authentication/authorization model?
Edited Aug 10, 2021 by Marten Hogeweg
Assignee
Assign to
Time tracking