note to self: The Vogue has a good alcohol:price ratio
note to others: Apparently Norway lacks a sardonic sense of humor 
Last night wasn't a total loss (the Vogue was an okay place), and I worked out two simple models for SOA and J2EE systems. I used a standard MVC pattern for J2EE and assumed a heterogenous network for SOA (to require transformation transactions).
A diagram of transaction count spanning network organization -
A visual diagram is always good. In SOA, the ESB (bus) manages all control and some routing; in the MVC, the controller manages all routing, control and creation (remember our pattern model). So centralized traffic is high in MVC.
The assumption of heterogenous network is valid for large networks & companies, but you might argue that J2EE matches SOA across homogenous networks. But even then, the transaction count for the controller rises faster than for the ESB. SOA is more scalable because it pushes transactions to the periphery of the network (into the services) and puts less incremental traffic on the bus.
I see now that the issue with SOA is network latency, which might be why the phrase "coarse-grained services" shows up so often now in the design literature.
( Dec 25 2005, 06:57:30 PM EST ) Permalink Comments [1]
Posted by credit card terminal and processing on February 20, 2007 at 10:53 AM EST
Website: http://del.icio.us/credit_card_terminal #