Re: Cross-application transactions in middleware systems

> Well, it's never easy, and Microsoft doesn't lead in middleware, and
> BizTalk is a concept in search of a useful first implementation.

Oh dear, can I quote that? :-)

> I'd say you can construct the middleware to "know" where its partial
> transactions are, you can hide it from the client -- but that's you
> doing it, not the monitor. Distributed transactions aren't exactly
> impossible, but they are often prohibitively expensive in terms of
> middleware licenses, hardware resources, and execution time.
>
> Posting up, down, and sideways and propagating exceptions back and
> forth yourself is always possible instead. Maybe it's not as pretty,
> but it gets the job done.

Actually, we aren't looking into buying an MW system, we're investigating the development of an in-house system to streamline our internal workflow between some of our databases and applications. Now we're playing devil's advocate on how far we can go, theoretically. So, in a way, we're developing our own middleware. Just to see how far we could go with it, I wanted to find out what service levels are provided by the commercial MW systems.

After all this discussion, it seems that technology is definitely still far behind the hype generated by the mirriads of middleware advocates out there. Received on Thu Mar 29 2001 - 14:53:32 CEST