asynchronous interface vs synchronous interface

[GabrielSagaya]

can you explain asynchronous interface vs synchronous interface with adv & disadv.

[Former Member · Accepted solution]

hi Gabriel,

one thing i know as a practicle examle,

synchronous interface flow is like Phone call.

Means either Picked up if receiver is reachable(Successful) or not picked up if receiver is not reachable(failure)

So as you have to make a another call just like that yo have to send anther message with same data.

But in async interface flow

it is like email service.

means the service will wait for the receiver even if it is not reachable.

when the receiver is reachable then message will be processed after restarting.

Ya its right that we can not compare these two.

As per the business requirement we use it.

**PS:reward points if useful**

regards,

Sumit Gupta

[Former Member]

Hi Gabriel,

sumit already has explained with a very good example.

In addition to him in synchronous interface you can receive acknowledgement (quality of service BEST EFFORT) but if this comes in error then you have to send it again.

In Asynchronous interface (quality of service EXACTLY ONCE, EXACTLY ONCE IN ORDER) you can not receive acknowledge but if message comes in error then it still persissts and you can restart it again.

For example : if message is in error due to incorect payload then you can reimport correct payload then restart asynchronous message and it will be successful

hope it may clear your concept

Thanks

Sandeep

PS: if helpful plz reward points

[Former Member]

Gabriel,

<b>synchronous</b>

the sender sends a request message to the receiver and waits for a response message.

for eg. consider a scenario.. where u have a customer no. and u need customer details.which is stored in R/3...so u can configure a HTTP to R/3 synchronous scenario... a http request will be sent to R/3 having a CUSTOMER NO....and in response u will get details of customer like...cust name,address, etc...

<b>asynchronous</b>

sender send a request message but doesn't wait for response.

for eg consider a file to file scenario .where u need to pick a file from a source location to a destinartion location....so...it will asynchronous interface

hope u r lil bit clear!!.

Regards

Biplab

[Former Member]

Gabriel,

Just note down...the point mentioned by srivastava..

-->SAP recommends the use of Async interfaces as far as possible. This is because once a sync communication starts, the sender has to wait for the response from the receiver which consumes the resources.

this is very critical...

so go for sync only when required..

Regards,

[prateek]

Async - One way coomunication

Sync - 2 way coomunication, Sender getting response from receiver

SAP recommends the use of Async interfaces as far as possible. This is because once a sync communication starts, the sender has to wait for the response from the receiver which consumes the resources.

In async case however, the sender just has to send the data and XI is responsible for delivering it to the receiver.

Regards,

Prateek

[vikas_agarwal]

Hi,

if you want the response back into the system then you uses synchronous interface or we can say for Synchronous communication( like you want data from RFC/BAPI) we have to use Synchronous Interface

and if we want asynchronous communication(like Idoc) we use asynchronous Interface.

You cannt compare the adv and disadv. of these two.

It is accroding to our need, which interface has to use.

Thanks