Difference between revisions of "Talk:Power TAC Architecture"
Grampajohn (talk | contribs) (Created page with "==Server Architecture Refactoring== ===Main Idea=== Extend the message driven nature of the overall TAC Energy design (JMS Messaging between server and broker clients) to also c...") |
Grampajohn (talk | contribs) (→Example) |
||
Line 7: | Line 7: | ||
===Example=== | ===Example=== | ||
− | Refactored order (shout) handling during execution phase using spring integration on top of the current server architecture | + | Refactored order (shout) handling during execution phase using spring integration on top of the current server architecture:[[File:Example.jpg]] |
Latest revision as of 19:35, 22 November 2010
Server Architecture Refactoring
Main Idea
Extend the message driven nature of the overall TAC Energy design (JMS Messaging between server and broker clients) to also cover the inner core of the TAC Server itself. Spring Integration seems to be the natural choice as implementation base for the necessary refactoring, as it extends Spring Core with an appropriate messaging infrastructure (e.g. introducing concepts such as Message, Channel, Endpoints, Transformers etc.) and comes with out of the box JMS, REST, JMX adapters / connectors.
Example
Refactored order (shout) handling during execution phase using spring integration on top of the current server architecture:File:Example.jpg