Lists Home |
Date Index |
On 5/11/06, email@example.com <firstname.lastname@example.org> wrote:
> OO generally refers to the interaction of pieces of code running in a single process on a single
> computer, whereas SOA refers to the interaction between different
> processes running on (possibly) different computers.
One of the things I've been thinking about in my day job, as part of
using xmpp as transport for an SOA based on mobile pub-sub
transducers, is optimising communities of such transducers into single
processes (the sort of thing that
http://www-static.cc.gatech.edu/~shivers/papers/fcoro.pdf is about) .
If you understand each service as a transducer, and allow reversible
beta-reduction (as you may have to de-optimise and reconfigure as more
transducers join (for example, some are backed by realtime 3D so need
to take control of timing, whereas most are event driven), then
whether or not the interactions should be generally below the level of
your architecture, in the same way as whether or not a function is
inlined is below the level of many compiler input languages.
Though my xmpp 'bots are probably much smaller and less 'enterprisey'
than most soa applications.