Scenario execution, cycles, and phases

{{product name}} is a transactional system, similar to relational databases each {{scenario singular lowercase}} execution starts with the initialization phase , continues with at least one cycle composed of the operation and commit/rollback phases , and ends with the finalization phase during the initialization phase , all necessary connections are created they are also checked if each module is capable of performing their intended operation(s) each cycle represents an undividable unit of work composed of a series of operations it is possible to set the maximum number of cycles in the {{scenario singular lowercase}} settings the default number is 1 during the operation phase, reading and writing operations are performed the reading operation consists of obtaining data from a service that will then be processed by other modules according to a predefined {{scenario singular lowercase}} for example, the dropbox > watch files module returns new bundles (files) created since the last {{scenario singular lowercase}} execution the writing operation consists of sending data to a given service for further processing for example, the dropbox > upload a file module uploads a file to a dropbox folder if the operation phase is successful for all modules, the commit phase begins, during which all operations performed by the modules are committed this means that make sends information to all the services involved in the operation phase about its success if an error occurs during the operation or commit phase for any module, the phase is aborted and the rollback phase is started, making all operations during the given cycle void some modules do not support rollback and operations performed by these modules cannot be taken back modules that support rollback and marked with the acid tag modules without this tag do not support rollback and cannot be reverted back to their initial state in case of an error in other modules during the finalization phase , open connections (e g ftp connections, database connections, etc ) are closed and the {{scenario singular lowercase}} is completed example transfer of bundles between databases the following example shows how to connect three acid modules the aim of the {{scenario singular lowercase}} is to get new rows from a mysql database, insert (transfer) them into an mssql database, and then insert the ids of the rows from the mssql database into a postgresql database when the {{scenario singular lowercase}} starts, the initialization phase is performed first {{product name}} verifies connections to the mysql, mssql and postgresql databases one at a time if everything goes well and the connections are successful, {{product name}} moves on to the operation phase if an error occurs, the finalization phase starts instead of the operation phase and the {{scenario singular lowercase}} is terminated if there isn't an error, the operation phase begins a preset procedure selects (reads) the table rows (bundles) from mysql those rows are then passed to the next module that writes them to a selected table in the mssql database if everything is in order, the last postgressql procedure is called to insert the row ids returned by the preceding module into the table if the operation phase is completed successfully, the commit phase begins {{product name}} calls the sql commit command for each database and the write operations are committed however, if the operation or commit phase fails due to an error, (e g connection failure), {{product name}} calls for a rollback during the rollback phase , {{product name}} goes through all modules and executes the sql rollback command for each module to revert each database back to its initial state finally, during the finalization phase , each module closes its connection to the database