ESB

Today, more than 94 million active users around the globe flock to eBay to find the best deals in cyberspace. In 2010 alone, the total value of goods sold on eBay was a staggering $62 billion or $2,000 every second.

Today, organizations rely on their enterprise software applications to carry out business functions more efficiently. However a disconnected heap of independent software applications can cause more problems than they solve. In order to make the most out of enterprise software deployments, they should be integrated to work together in perfect synchronicity. Though it seems simple enough, connecting a myriad of diverse applications with their different programming languages, platforms, data formats, protocols, and QoS requirements can be an architect's worst nightmare.

All Enterprise Service Bus (ESB) products may be used to build and deploy services, encapsulate legacy systems, route messages, transform message formats, and perform protocol mediation. Many WSO2 prospects ask me ‘What differentiates WSO2 Enterprise Service Bus?’ This blog post shares my perspective and scales the conversation.

Continue reading Chris Haddad's blog.

In this article we focus on the performance benchmark aspects of the WSO2 ESB under two different approaches: Message Relay (MR) and Pass-Through (PT). We discuss how efficiently the ESB can handle messages of different sizes under different concurrency levels. We provide a set of detailed statistics to allow comparison of the different approaches.

This is the part 1 of a series of articles that describes various file exchanging scenarios which can be implemented using WSO2 ESB. This first article describes how to read or fetch a file or a special file (such as an archived file like *.zip, *gz or *.pdf etc..) from various sources such as a local file system, an ftp server or sftp server. Although the material is suitable for readers who have experience with WSO2 ESB, the material is self explanatory as much as possible.

Ability to store a message in a temporary storage is a fundamental requirement in many enterprise integration scenarios. There are many occasions where a systems integrator would have to design a message flow which simply dumps all the messages into some kind of a storage facility for later retrieval. Here are several scenarios that I’ve encountered while working on real-life integration projects which required me to consider using an intermediate message store:..

Read the complete blog post.

Best practices in Enterprise Application Integration (EAI) include a Service Oriented Architecture (SOA) and the Enterprise Service Bus (ESB) model to implement a service broker pattern for connectivity, mediation, process orchestration and security.

Security is a key aspect of any successful enterprise SOA solution which allows channels for internal and external parties to access business assets. Security measures should also enable other vital aspects of the solution such as

• Flexibility - By catering to new security requirements which arise with changing business policies
• Interoperability - By facilitating secure communication with heterogeneous systems which talk over different security protocols.