Skip to content
* / softthoughts

Quality provided by the Dynamics Ax messaging module

There are several qualitative advantages for the Dynamics Ax platform when the Ax messaging module (AMM) is used. Some important ones are::

* The AMM is essentially a frame for handling documents, commands and events in the system and by doing this it provides a clear consistent tactic.

* Because the AMM uses a messaging broker there is a central messaging flow controller which takes away the knowledge that modules, subsystems or systems need to have, to communicate with eachother.
This loose coupling has several more advantages.

  • For example, it reduces the rippling effect that exist when the requirements change. Changing requirements are almost inherent to every project.
  • Under the right conditions it can make a system more configurable and thereby reducing the need for coding and so a possibility of errors.
  • Functionality can be more clearly seperated instead of a strong integration (spaghetti) with other modules, subsystems or systems. It can help thereby the idea of domain driven design. Although strong integration is a strength for RAD and performance, it can become a weakness. When systems will be reused a lot, a certain level of loose coupling and variation points in the architecture help the reuse of functionality.
  • Also a clear seperation of concerns is better for understandability and maintability.

* Monitoring the system becomes uniform. When events happen, commands are placed or documents are sent, all their statusses or progression can be monitored in the same way. This helps the usability and understandability of the system, and reduces the need to provided several monitor functionalities.

* A system like dynamics Ax is built to be a solution for a wide range of problems in the enterprise. Because a wide scope implicates a wide flavor of dependencies, the Ax messaging system can help to bring the Ax platform from a single distributed application to a full integrated enterprise application, having a local messaging broker like the one the AMM provides with for example a central message broker or a process manager like Biztalk.

* Not all tasks need to be handled synchronously. Making synchronous and asynchronous tasks explicit in the system can improve the executing of synchronous real time tasks, like when users of the system are working. Handling messages asynchronously is a fundamental tactic of the AMM.

* Biztalk is an expensive but very productive messaging system certainly for complex tasks. It is an interesting component to control the message flow at a central place in an enterprise. To control locally at a smaller scale the AMM can help and be a part of the message controlling hierarchy.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: