You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2024. It is now read-only.
The roadblock right now is we are using SDO's reference implementation of OCS, which saves the "DB" info in files in a persistent volume. If multiple instances of OCS are running, we could get file corrupition (w/o locking).
The FIDO release of SDO (1H21), the equivalent of OPS will have a JDBC interface to its persistence, so we can plug in our own DB (postgresql) and don't have to implement our own OCS. This will be by far the easiest/best way to support multiple replicas of the SDO services.
The text was updated successfully, but these errors were encountered:
The roadblock right now is we are using SDO's reference implementation of OCS, which saves the "DB" info in files in a persistent volume. If multiple instances of OCS are running, we could get file corrupition (w/o locking).
The FIDO release of SDO (1H21), the equivalent of OPS will have a JDBC interface to its persistence, so we can plug in our own DB (postgresql) and don't have to implement our own OCS. This will be by far the easiest/best way to support multiple replicas of the SDO services.
The text was updated successfully, but these errors were encountered: