Ronald Schmelzer, an analyst with ZapThink LLC, based in Waltham, Mass., said, “Alchemy is focused on the sometimes-connected client, or basically those Web services consumers who aren’t always on the network. So, to include them in an SOA, one has to use asynchronous messaging protocols and other reliable Web services mechanisms.

“Much of what is written about ESBs centers on the fact that they extend message-oriented middleware with Web services and service container interfaces,” Schmelzer said. “Since message queuing and interacting with heterogeneous, and perhaps sometimes-connected systems, is part of that ESB message, this Alchemy feature set definitely adds some potency to BEA’s offering.”

Read more at: eWeek