| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Canonical Message Format |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mut1ey |
 Posted: Wed Sep 16, 2009 2:02 pm Post subject: |
 |
|
Acolyte
Joined: 07 Oct 2005
Posts: 74
Location: England
|
| Vitor wrote: |
But the reason you have a canonical format is to reduce those required changes. Or you might just as well use the original message formats. |
And that is my point. Change is invevitable. If you hook your canonical format into your "core" flows, at some point you are going to have to extend it for that new application that comes along. To my mind, that means you either externalise the changes into a specific set of flows, or you have to change your canonical format. If you have to change you canonical format, that could have a huge impact. If you are only left with the externalise option, then is there any value in trying to define a canonical format? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Sep 16, 2009 2:23 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| If you have to change your canonical format, that could have a huge impact |
Only if you made some bad decisions when you designed the canonical format.
If your business deals with data from 3 or more external message formats, then a canonical format can act as the 'pivot' or 'hub' format. Instead of creating many flows to transform between each pair of formats, you simply provide a transformation flow to and from the canonical format for each external message format.
If the canonical format was designed to be extensible, you should be able to add new fields in a controlled way without breaking existing message flows. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 17, 2009 7:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kimbert wrote: |
| Quote: |
| If you have to change your canonical format, that could have a huge impact |
Only if you made some bad decisions when you designed the canonical format.
If your business deals with data from 3 or more external message formats, then a canonical format can act as the 'pivot' or 'hub' format. Instead of creating many flows to transform between each pair of formats, you simply provide a transformation flow to and from the canonical format for each external message format.
If the canonical format was designed to be extensible, you should be able to add new fields in a controlled way without breaking existing message flows. |
And I couldn't have put it better myself.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
