[FOLIO-3539] [NFR] Review state control of modules - MG Created: 11/Jul/22 Updated: 13/Jul/22 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Denis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||||||||||
| Development Team: | None | ||||||||||||||||||||||||||||||||
| Description |
|
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:
The scope of the feature is to verify the compliance of the following five modules against feature requirement:
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 |
| Comments |
| Comment by Khalilah Gambrell [ 13/Jul/22 ] |
|
Denis - is this required for Morning Glory? Or for Nolana? |
| Comment by Denis [ 13/Jul/22 ] |
|
Hi Khalilah Gambrell, |