Update data-store-variables-and-jms-queues-when-to-use-which-option-6… #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi SAP Team,
In general this documentation doesn't mention the Data Store Sender adapter. I don't remember, but I think this adapter is relatively new - so I guess that's the reason. With the availability of the DS Sender adapter, in my opinion, most of the disadvantages compared to the JMS adapter are eliminated. Or am I missing something?
In respect of this, also the Async decoupling usecases explained here: https://help.sap.com/docs/cloud-integration/sap-cloud-integration/use-cases-for-data-store-and-variables need to be adjusted as no (timer based) polling is needed anymore.
Kinds regards,
Philippe