III.11 Risks

Following are the risks that influence the architectural decisions:

• The Receiver component suffers from overly complicated source code that's created by a number of developers without consent. Most production bugs result from this part of MaMa-CRM.
• The runtime flexibility of import/export configurations and campaign processes might lead to incorrect and undetected behavior at runtime as there are no configuration checks. Mischievous administrators can misconfigure any MaMa-CRM instance at any time.
• Configuration settings are not archived and therefore might get lost (so there might be no fallback to the last working configuration in case of trouble).
• CoMeS is an overly trivial and resource-wasting synchronization mechanism and should be replaced with a decent async/event-based system as soon as possible.