[jboss-dev-forums] [Design of JBoss ESB] - Re: The message is important!

[driedtoast]

I do like the concept of breaking out the translation of the model from the model. In this approach you can start to imagine the bus taking on a whole service approach internally. 

For example,


Utility Services:

 - TRANSPORT - protocol that is used to connect to services
   - JMS
   - SMTP
   - TCP/IP
   - HTTP
   - JNDI/Local invocations

- FORMAT - format of the resulting or incoming information to the bus
   - XML
   - JSON
   - SOAP
   - etc...

- ROUTE - Routing of a message based on content or location

- CACHE - responds to messages that are flagged cacheable?

Auditing and Monitoring Services:

- NOTIFY - Notifications of the messages within the system
 
- AUDITING  - Storing the message  
   - DB
   - LOG
   - Etc..


Business Services:

- Actions - Services that are put into the bus for business logic


The whole thing could be tied together with a BPM strategy.
For example,

Transport -> Starts process XYZ
Process starts to run
XYZ -> FORMAT/TRANFORMATION to MODEL
XYZ -> ROUTE
XYZ -> CACHE
    NO CACHE: XYZ -> ACTION XYZ
XYZ -> FORMAT
XYZ -> TRANSPORT


Or alternatively

TRANSPORT - > XYZ 
XYZ -> FORMAT/TRANFORMATION to MODEL
XYZ -> ROUTE
XYZ -> FORMAT
XYZ -> TRANSPORT (External service)
XYZ -> AUDIT     
XYZ -> FORMAT
XYZ -> TRANSPORT


The idea would be that when a message comes in, the process starts based on the message/service. The service really being a process.

Thoughts?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024220#4024220

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024220