MOM architecture (Cloud)
(→Queues) |
|||
| Ligne 5 : | Ligne 5 : | ||
[[image:Cloud-architecture-mom-overview.png]] | [[image:Cloud-architecture-mom-overview.png]] | ||
| − | + | ==Asynchronous operations== | |
When the MOM architecture is used, the front services execute user actions as asynchronous tasks. | When the MOM architecture is used, the front services execute user actions as asynchronous tasks. | ||
| Ligne 21 : | Ligne 21 : | ||
Because transparent asynchronous task require a minimum latency, the queue used for these tasks is separate and listeners used a shorter polling rate. | Because transparent asynchronous task require a minimum latency, the queue used for these tasks is separate and listeners used a shorter polling rate. | ||
| − | + | ==Queues== | |
The MOM architecture rely on a set of message queues. | The MOM architecture rely on a set of message queues. | ||
| Ligne 51 : | Ligne 51 : | ||
{{tip|Azure infrastructure offers two queue services, Azure Service bus and Azure queue storage. The later is used because of it's better latency.}} | {{tip|Azure infrastructure offers two queue services, Azure Service bus and Azure queue storage. The later is used because of it's better latency.}} | ||
| − | + | ==Configuration== | |
The MOM architecture replace the scheduler and business processes (workflow) available in On Premise deployments. | The MOM architecture replace the scheduler and business processes (workflow) available in On Premise deployments. | ||
Version du 27 février 2017 à 11:26
Overview
Because Sage FRP 1000 Cloud solution is based on the concept of separation of a front and back roles, communicating by messages, a new MOM architecture has been developed to implement this concept.
Asynchronous operations
When the MOM architecture is used, the front services execute user actions as asynchronous tasks.
The user action concerned are :
- Application processes which can be scheduled.
- Printing and preview.
- Exporting.
Depending of the user task nature, the asynchronous aspect of the execution may be transparent or not :
- When an action is executed as a transparent asynchronous task, the user has immediately the result.
- When an action is executed as a not transparent asynchronous task, the user as the result in his message box and is notified in the interface of the execution status.
Because transparent asynchronous task require a minimum latency, the queue used for these tasks is separate and listeners used a shorter polling rate.
Queues
The MOM architecture rely on a set of message queues.
There is an indirection level between the logical queues used by the Application Code and the physical queue used by the MOM architecture. This is defined during the configuration.
Queue are specialized by task nature :
| Logical Queue name | Used for |
|---|---|
| TASKP | This queue is used for scheduling of tasks. |
| TASK | This queue is used for Application processes. |
| USER | This queue is used for transparent asynchronous user actions. |
| This queue is used for print actions. | |
| EVENTS | This queue is used for events processing. |
|
Tip : Azure infrastructure offers two queue services, Azure Service bus and Azure queue storage. The later is used because of it's better latency. |
Configuration
The MOM architecture replace the scheduler and business processes (workflow) available in On Premise deployments.
It must be selected and configured at the Folder level in the administration.
Note that in a multi tenancy deployment the MOM architecture is the only option available because the scheduler service and the Business processes service can't be started.
