Thursday, December 29, 2011

Synchronous vs asynchronous

Synchronous messaging –

Synchronous dictionary meaning say, occurring at the same time.

Synchronous messaging is same as the dictionary meaning. Synchronous messaging occurs when two systems or application transmits data to and fro. The data or message first enters queue then delivered to the recipient.

The further communication cannot take place until response data or message is received back to the sender. Hence sender will wait till a response from other recipient is received. Synchronous messaging is also called as Synchronous Communication.

The information is transferred in synchronous communication after every certain time interval, provided response is received from recipient end.

Example of synchronous communication can be conversation over mobile phone. Unless you receive response from other end speaker you don’t seem to take the conversation ahead.

Asynchronous messaging –

Asynchronous dictionary meaning say, not occurring at the same time.

In Asynchronous messaging information transfer takes place between the two applications or system; however the sender system will not wait for response from recipient system. The message first enters in the queue and remains there till it is not received by recipient end.

The sender can continue the message sending even if no response has been received from recipient. The response data is required but it is not required on immediate basis.

Asynchronous messaging is also called as “Fire and Forget Information Exchange” or “Message Oriented Middleware (MOM)”.

The best example of asynchronous messaging is Email service. The sender can send more mails even if the response from recipient is not received.

The additional component is required in asynchronous messaging to ensure that message present in queue is received by intended recipient. This affects performance and reliability of the system.

Hope above example and explanation clears the difference between synchronous and asynchronous.

Followers

About Me

I am Kunal Chandratre. Working as Cloud Solution Architect @Microsoft. My speciality is Microsoft Azure Cloud platform.
Awarded as Most Valuable Professional (MVP) in Microsoft Azure for consecutive 3 years. Passionate speaker, trainer...In free time (which I don't get usually)I write blogs and answers the forum questions. I was doing it just for timespass but now I have got addicted to blogging...Apart from work, I do variety of things which I can't tell here:).. I am trekker, singer, actor, painter, f1 racer, super hero in my dreams.. ...and now trying my luck with technologies...Keep posting...

Visitors

Disclaimer:

The information shared in this blog is the result of my personal experience with various technology platforms. In no way it represents the company I work for.
The information provided here is "AS IS" with no warranties, and confers no rights. This blog does not represent the thoughts, intentions, plans or strategies of my current employer or past empolyers or any other forums or community I belong to. It is fully my own opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.I have full rights to edit/modify/delete any content of this blog without any prior notice to public/followers/RSS readers of this blog.