.NET Windows Communication Foundation - What is WCF part 1

First let’s give a short answer to this: - “WCF (Indigo was the code name for WCF) is a unification of .NET framework communication technologies “. Ok let me tell you a story.
Long Long time a ago there lived a hard working and a nice architecture. He used to work for a travel agent with his small and happy team software professionals. Travel agent had tie ups with many big flight carriers. The nice and hardworking architecture and his team developed a nice booking engine by which you can book tickets through any of the flight carriers. The Travel Agent Company was very happy with the architecture and his team member’s achievements.
As time passed by the travel agent’s business grew in multiples. Travel agent started his own franchise. Travel agent wanted to provide this booking engine service to his franchise. So one fine morning he called the hard working architecture. Architecture was very excited of the new work and started on it day and night. He prepared a list of franchise and made personal visits to see what infrastructure they had. He saw all the franchise worked in Microsoft Windows platform. Booking engine was located in the main head office and all the franchise should communicate to this booking engine. After discussing with his team members he concluded that the best way to communicate is .NET remoting because the head office where the booking engine was hosted was also on windows platform and the other franchise where also on the same. He then worked day and night with his team members to implement .NET remoting to enable communication between the franchise and the booking engine hosted in the head office. After months he rolled out his project successfully.
Travel Agent was very happy with his architecture and the team. Travel agent was now providing his booking service to his franchise in the most efficient manner. Time passed by and because of the good automated booking service more companies wanted to take the franchise from the travel agent. But the big issue was many of the franchise did not have windows operating system. They worked on Linux and other Non-Microsoft operating systems. Due to this limitation travel agent was loosing lot of franchise business. So one fine day they again called the Architecture and said that the booking engine should also be available to Non-Microsoft platforms. Architecture again went in to action. He setup a high level team meeting and discussed the best solution on Non-Microsoft platforms. After long discussion’s they concluded Web services as the solution. His team again went in to action and implemented the solution. So now his booking engine architecture was working with two technologies .NET remoting and Web services. He kept .NET remoting so that he can get speed and performance benefits from common windows platform and he also kept Web services so that he can operate seamlessly with Non-Microsoft platforms. Travel agent was now at his peak of happiness as he had the world at his tips. Franchise now started making huge ticket bookings through the booking engine. Booking engine had the capacity of serving 20 tickets / second but it had now to serve 50 tickets / second. End franchise client had to wait to get response and was not able to process the next ticket booking until the first one was served. Travel Agent started receiving huge complaints because of this synchronous processing. They again called the architecture and proposed the problem before him. Now architecture was really at a fix as he did not wanted to touch the booking engine logic to increase performance. So he concluded to use MSMQ (Microsoft Message Queuing) service. He analyzed that the main problem was that the travel agent had to wait until his first ticket booking is not completed.