[FOLIO-2725] Review state control of modules Created: 17/Aug/20  Updated: 11/Jul/22

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Umbrella Priority: TBD
Reporter: Oleksii Popov Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by FOLIO-3539 [NFR] Review state control of modules... Open
is cloned by MODRTAC-43 Review state control of modules Closed
Defines
is defined by FOLIO-2736 Check that Folijet modules are stateless Closed
is defined by CIRC-904 Review state control of mod-circulation Closed
is defined by CIRCSTORE-238 Review state control of mod-circulati... Closed
is defined by MDEXP-270 Review state control of module Closed
is defined by MODCXINV-50 Review state control of mod-codex-inv... Closed
is defined by MODINV-340 Review state control of mod-inventory Closed
is defined by MODINVSTOR-565 Review state control of mod-inventory... Closed
is defined by MODUSERBL-107 Review state control of mod-users-bl Closed
is defined by MODUSERS-218 Review state control of mod-users Closed
Relates
relates to EDGORDERS-35 Review state control of edge-orders Closed
relates to MODAUD-25 Review state control of mod-audit Closed
relates to MODFIN-150 Review state control of mod-finance Closed
relates to MODFISTO-145 Review state control of mod-finance-s... Closed
relates to MODGOBI-108 Review state control of mod-gobi Closed
relates to MODINVOICE-197 Review state control of mod-invoice Closed
relates to MODINVOSTO-82 Review state control of mod-invoice-s... Closed
relates to MODORDERS-426 Review state control of mod-orders Closed
relates to MODORDSTOR-176 Review state control of mod-orders-st... Closed
relates to MODORG-16 Review state control of mod-organizat... Closed
relates to MODORGSTOR-84 Review state control of mod-organizat... Closed
relates to MODQM-37 Review state control of mod-quick-marc Closed
relates to MODCAL-80 Review state control of mod-calendar Closed
relates to MODEMAIL-38 Review state control of mod-email Closed
relates to MODEVENTC-21 Review state control of mod-event-config Closed
relates to MODFEE-102 Review state control of mod-feesfines Closed
relates to MODNOTIFY-79 Review state control of mod-notify Closed
relates to MODPATBLK-49 Review state control of mod-patron-bl... Closed
relates to MODSENDER-34 Review state control of mod-sender Closed
relates to MODTEMPENG-55 Review state control of mod-template-... Closed
relates to MODCXEKB-108 Review state control of mod-codex-ekb Closed
relates to MODCXMUX-65 Review state control of mod-codex-mux Closed
relates to MODKBEKBJ-502 Review state control of mod-kb-ebsco-... Closed
relates to MODNOTES-155 Review state control of mod-notes Closed
relates to MODPWD-40 Review state control of mod-password-... Closed
relates to MODTAG-40 Review state control of mod-tags Closed
Sprint:
Development Team: None

 Description   

In order to achieve a possibility to run multiple instances of the same module state control verification should be done.
Each team should verify their back-end modules code in order to ensure that the module is stateless.

In another case - raise it and each module technical design should be reviewed separately.

Teams responsibility for modules: https://folio-org.atlassian.net/wiki/display/REL/Team+vs+module+responsibility+matrix



 Comments   
Comment by Marc Johnson [ 12/Oct/20 ]

Has the definition for state control been agreed upon, allowing teams to perform this evaluation?

Comment by Marc Johnson [ 12/Oct/20 ]

Oleksii Popov

What is the expected output of each of these tasks? Is this information being collected somewhere? How is it going to be used?

Comment by Oleksii Popov [ 12/Oct/20 ]

Marc Johnson
We expect to understand where changes are needed.
All information is tracking on this ticket.

More information about scaling is listed here: https://docs.google.com/document/d/1kmafhus497R5UF1D3GxJb3QoJMRPvBdadfolGVkq6G0/edit

Generated at Thu Feb 08 23:22:47 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.