Enterprise Integration for Beginners

In my previous post  , I have discussed about the facts you need to consider when selecting an integration solution for your enterprise IT infrastructure. I didn't provide any clue on what is the best vendor you can select since that depends on your requirements and budget and many other reasons. In this post, I will do a comparison between several open source and proprietary solutions and differentiate WSO2 ESB (my employer) features with them. Proprietary ESB  Pros  Suite of solutions included and work smoothly with each other (eg: CEP, BPEL, MB, Registry) Powerful and stable tooling and monitoring capabilities Excellent support for price Cons High price, High complexity Licensing and non-transparent pricing model Different components may come from different code bases acquired through different companies Heavy products Installation may need consultants and take more time Open source ESB Pros Simple installation and intuitive tooling Some ve

If you are an IT architect responsible for designing your enterprise IT system, you may have already experienced this topic. Modern IT systems consists of so many different systems developed by different vendors with different technology stacks. Even though those are developed independently, those systems should interact with each other to provide a seamless business experience to your stake holders. This is where the challenge of integration comes into the picture. Integrating heterogenous systems is a very complex task and you need to consider so many things before choosing a proper solution. With this blog post, I am going to discuss about the things which you need to consider when choosing an integration solution for your enterprise. I have grabbed some ideas from the following blog post[1] which also describes a similar topic. [1]  http://www.infoq.com/articles/ESB-Integration Mainly, there are 2 streams of product categories available in the market. Open source software

HTTP is the most widely used application layer protocol in the world. Entire Web is running on top of this protocol. HTTP 1.1 was introduced in 1999 and is still the de-facto standard for web communication. With the improvements of the web and the way people interact with the web (mobile devices, laptops, etc..), this protocol has been hacked to provide new functionality. This hacking is no longer stable and the world of internet needed a new protocol version. That is why IETF has developed HTTP/2 protocol to address the challenges which are faced by the web community. You can find the latest draft of this protocol here . Why we need HTTP/2 Early days, bandwidth was the limiting factor. But today, average internet user in US has a bandwidth of 11Mbit/s Latency is the new bandwidth. End users will not worry about the bandwidth as long as they get better responsive applications. HTTP 0.9 - Initial version of the protocol introduced in 1991. Required a new TCP connection per re

It has been months since I have written a blog post. One of the main reason for that was the subject of this post. We have been working on ESB 4.9.0 release day in day out and most of the time beyond mid night. With all the efforts, we have released the most awaited ESB release. You can download the binary from the following location http://wso2.com/products/enterprise-service-bus/ What is special about WSO2 ESB 4.9.0 WSO2 ESB has been well known for the near zero latency and the ultra performance of its mediation engine. We made this mediation engine faster and more feature rich than ever. Inbound Endpoints make ESB the ultimate integration engine with more dynamism.  Coordination support for Scheduled tasks, Message Processors and Inbound endpoints make sure that you are safe unless there is at least one node up and running Integration with different MQ protocols has been extended with RabbitMQ, MQTT, Kafka Message storing capabilities has been extended with JDBC, Rabbi

Recently, I found a nice video on facebook which was shared by Sanjiva Weerawarana (CEO @ WSO2), which was a narration by Matt Damon. The original paragraph was taken from a speech by Howard Zinn's 1970 speech. https://vimeo.com/48834336 According to that, world is topsy turvy (upside down). Wrong people are in power, Wrong people are out of power. But there is one thing missing in that speech. Which is that wrong people are using software, wrong people are not using software :). Sorry about going out of the topic. But this speech has really moved me. Anyway, let's start talking about the subject. WSO2 ESB is the central hub of your SOA architecture. It will communicate with all kinds of heterogenous systems. These systems can go mad sometimes. In such a scenarios, WSO2 ESB should not go mad. If you haven't done proper error handling at WSO2 ESB, even though it does not go mad, people will feel that it has gone mad by looking at lengthy error logs and exceptions. So w

This blog post is a continuation to my previous blog post where I have described the concepts of WSO2 ESB transports mechanism. Since we have covered the basics, let's start writing some real code. I will be using the ISO8583 standard as my subject to this custom implementation. I will be grabbing some content from this blog post for my reference to ISO8583 java implementation (Business logic). Thanks Manoj Fernando for writing such an informative post. http://manoj-fernando.blogspot.com/2013/08/iso8583-with-wso2-esb.html Idea of the custom transport implementation is to provide a mechanism to write your business logic which can plug in to the WSO2 ESB runtime. I am not going to tell more about ISO8583 or it's internal implementations. I will be using already implemented java library jPos for this purpose.  It has the functionality to cover the basic use cases of ISO8583 implementations. Sample use case Let’s take the scenario of a certain financial application needi