Make deployment of DB service optional when not using the admin module
esune opened this issue · comments
When not using the admin module for Issuer Kit, running the database service connected to the API is redundant: no information is being stored in the database, as everything is related to invite records.
As of now, not deploying the database may result in errors during the lifecycle of the API service since it will still try to connect to it, even if it will not read/write anything.
Some options to investigate:
- making the API service configurable so that it could live without a database
- making the API service resilient to failed connections to the database
- update the API service so that it could run an in-memory or sqlite database when a full database is unnecessary
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has become stale.