July 2017
Beginner to intermediate
358 pages
10h 54m
English
With asynchronous processing, all the communication to the downstream application happens by leveraging a queue or a message broker as an intermediary. Rather than communicating directly with the downstream service, messages dispatch to a queue such as AWS SQS/SNS, Google Cloud Pub/Sub, or NATS.io. Because there is no processing performed at this layer, the only delay is the time it takes to deliver the message, which is very fast. Also, due to the design of these systems, acceptance or not of a message is the only situation you must implement. Retry and connection handling logic is delegated to either the message broker or the downstream system, as is the storage of messages for archive or replay:
Read now
Unlock full access