In order to guarantee high availability for the FOLIO platform using horizontal scaling (running multiple instances of the same module) state control verification for all back-end modules should be done.
Based on current deployment approach of Bugfest environment where two instances are deployed for almost all backend modules, the explicit list of modules that are deployed using a single instance is as followed:
mod-data-export-spring
mod-data-export-worker
mod-data-export
mod-quick-marc
mod-data-import
The scope of the feature is to verify the compliance of the following five modules against feature requirement:
mod-data-export-spring (Firebird) - SA: Mikhail F./Taras S.
mod-data-export-worker (Firebird) - SA: Mikhail F./Taras S.
mod-data-export (Firebird) - SA: Mikhail F./Taras S.
mod-quick-marc (Spitfire) - SA: Taras S.
mod-data-import (Folijet) - Olamide
Each team should verify their back-end modules' code to ensure that every module is stateless.
In another case, team will need to raise it and each module technical design should be reviewed separately with SAs and planned for implementation in nearest time.
Hi , it would be helpful to have such analysis completed as soon as possible to understand the state of the modules listed and the scope of work required to comply with HA requirement (if needed). Based on that data we could plan the work (whether it fits in MG or to be deferred for Nolana).
cc
Khalilah Gambrell July 13, 2022 at 1:03 PM
- is this required for Morning Glory? Or for Nolana?
P2
In order to guarantee high availability for the FOLIO platform using horizontal scaling (running multiple instances of the same module) state control verification for all back-end modules should be done.
In 2020 the details on the high availability (horizontal scaling) were captured on the wiki (updated in 2022): https://folio-org.atlassian.net/wiki/display/DD/Stateless%2C+Horizontal+scaling%2C+and+High+Availability
Based on current deployment approach of Bugfest environment where two instances are deployed for almost all backend modules, the explicit list of modules that are deployed using a single instance is as followed:
mod-data-export-spring
mod-data-export-worker
mod-data-export
mod-quick-marc
mod-data-import
The scope of the feature is to verify the compliance of the following five modules against feature requirement:
mod-data-export-spring (Firebird) - SA: Mikhail F./Taras S.
mod-data-export-worker (Firebird) - SA: Mikhail F./Taras S.
mod-data-export (Firebird) - SA: Mikhail F./Taras S.
mod-quick-marc (Spitfire) - SA: Taras S.
mod-data-import (Folijet) - Olamide
Each team should verify their back-end modules' code to ensure that every module is stateless.
In another case, team will need to raise it and each module technical design should be reviewed separately with SAs and planned for implementation in nearest time.
Teams' responsibility for modules: https://folio-org.atlassian.net/wiki/display/REL/Team+vs+module+responsibility+matrix