Enterprise Integration for Beginners

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