select API backend for persistent data and configuration

[tomkralidis]

wis2box-api uses Elasticsearch as a backend to manage data provided though OGC API.

For admin UI workflow, we would like the user to be able to manage the following:

• discovery metadata
• station metadata
• data pipeline configurations

The UI (as a deploy time option) needs to be able to interact with the API to manage the above.

Considerations:

• the above configurations:
  • are small in size
  • have a low transaction rate (design time)
• in process (SQLite, TinyDB, DuckDB) or full blown RDBMS (PostgreSQL, MySQL/MariaDB/etc.)
• resulting size of built (Docker) image
• pygeoapi requirements:
  • plugin availability
    • https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-features.html (station metadata)
    • https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-records.html (discovery metadata)
  • transaction capability (PUT, POST, PATCH, DELETE)

cc @isedwards

[tomkralidis]

2023-01-31

• use an in process database (MySQL, TinyDB, H2)
• maintain single source of truth on API backends