2019-12-xy.aws-reinvent-2019.API315.application-integration-patterns-for-microservices

One of the implications of applying the microservices architectural style is that a lot of communication between components is done over the network. In order to achieve the promises of microservices, this communication needs to happen in a loosely coupled manner. In this session, we discuss some fundamental application integration patterns mostly based on messaging and connect them to real-world use cases in a microservices scenario. We also point out some benefits that asynchronous messaging can have over REST APIs for communication between microservices.

This talk ran in four repeats at re:Invent 2019.

Transcript

1. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Application Integration Patterns for Microservices Dirk Fröhner A P I 3 1 5 Solutions Architect, Amazon Web Services @dirk_f5r
2. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Application Integration Patterns (not only) for Microservices Dirk Fröhner A P I 3 1 5 Solutions Architect, Amazon Web Services @dirk_f5r
3. Agenda Introduction Application integration patterns Concrete use cases
4. Related breakouts ARC314 Decoupled microservices: Building scalable applications
5. Related breakouts ARC314 Decoupled microservices: Building scalable applications API304 Scalable serverless event-driven apps using Amazon SQS & Lambda API306 Building event-driven architectures API307 Build efficient and scalable distributed apps using Amazon MQ API309 Durable Serverless Architecture: Working with Dead-Letter Queues API311 Managing business processes using AWS Step Functions API316 Building serverless workflows using AWS Step Functions API318 Deep dive on event-driven development with Amazon EventBridge
6. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
7. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. “If your application is cloud-native, or large-scale, or distributed, and doesn’t include a messaging component, that’s probably a bug.” Tim Bray Distinguished Engineer AWS Messaging, Workflow Management
8. Potential drawbacks of synchronous systems Synchronous systems are tightly coupled. A problem in a synchronous downstream dependency has immediate impact on the upstream callers. Retries from upstream callers can all-too easily fan-out and amplify problems. Photo: Dirk Fröhner
9. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
10. Message exchange One-way Request-response
11. Message exchange One-way Request-response Message channel Receiver No response expected Synchronous vs. fire-and-forget Sender
12. Message exchange One-way Request-response Message channel Receiver No response expected Synchronous vs. fire-and-forget Response expected Return address Correlation ID Sender Message channel Responder Requester Message channel
13. Message channels Point-to-point (queue) Publish-subscribe (topic)
14. Message channels Point-to-point (queue) Publish-subscribe (topic) Consumed by one receiver Easy to scale Flatten peak loads Receivers Sender Queue
15. Message channels Point-to-point (queue) Publish-subscribe (topic) Consumed by one receiver Easy to scale Flatten peak loads Consumed by all subscribers Durable subscriber Receivers Sender Queue Subscribers Publisher Topic
16. Message channels Point-to-point (queue) Publish-subscribe (topic) AWS service for queue functionality: Amazon Simple Queue Services (SQS) Serverless & cloud-native AWS service for topic functionality: Amazon Simple Notification Service (SNS) Serverless & cloud-native Receivers Sender Subscribers Publisher Amazon SQS Amazon SNS
17. Message channels Point-to-point (queue) Publish-subscribe (topic) AWS service for queue functionality (non-serverless): Amazon MQ (managed Apache Active MQ) For apps constrained to protocols like JMS, AMQP, etc. AWS service for topic functionality (non-serverless): Amazon MQ (managed Apache Active MQ) For apps constrained to protocols like JMS, AMQP, etc. Receivers Sender Subscribers Publisher Amazon MQ Amazon MQ
18. Message channels Visibility timeout, inflight messages, message acknowledgement
19. Message channels Visibility timeout, inflight messages, message acknowledgement Time receive message receive message delete / acknowledge message visibility timeout
20. Message channels Visibility timeout, inflight messages, message acknowledgement Time receive message receive message delete / acknowledge message visibility timeout Time visibility timeout receive message receive message receive message receive message
21. Message channels Topic-queue-chaining
22. Message channels Topic-queue-chaining Publisher Topic
23. Message channels Topic-queue-chaining Publisher Topic Queue Queue
24. Message channels Topic-queue-chaining Publisher Topic Queue Queue Application 1
25. Message channels Topic-queue-chaining Allows fan-out and receiver scale-out at the same time Publisher Topic Queue Queue Receivers Application 1 Application 2
26. Message channels Dead letter queue (DLQ)
27. Message channels Dead letter queue (DLQ) Sender Queue
28. Message channels Dead letter queue (DLQ) Transient failure mitigation Poison-pill handling Sender Queue Receivers X
29. Message channels Dead letter queue (DLQ) Transient failure mitigation Poison-pill handling Sender Queue DLQ Receivers X
30. Message channels FIFO queue Message groups
31. Message channels FIFO queue Message groups Guaranteed ordering Queue Receiver Sender Order!
32. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
33. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
34. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
35. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
36. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
37. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
38. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
39. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
40. Message channels FIFO queue Message groups Guaranteed ordering Messages grouped by discriminator attribute Example: Amazon SQS with sender provided message group IDs – no further consumption as long as messages with particular message group ID are invisible Queue Receiver Sender Receivers Sender Queue Order!
41. Message channels Message delivery QoS At least once At most once Exactly once Queue Receiver Sender
42. Message channels Message delivery QoS At least once At most once Exactly once Queue Receiver Sender Exactly once? Well! Tunable / configurable messaging systems: Choose between at least once or at most once Deduplication capabilities to detect and eliminate messages which are sent more than once to or by the messaging system But how to deal with a situation where the message was consumed, but never acknowledged? → Your systems still have to be able to handle duplicate messages → Messages should be processed in an idempotent manner
43. Message routing Message filter Recipient list
44. Message routing Message filter Recipient list Receive only a relevant subset of messages Controlled by subscriber Publisher remains completely unaware Subscribers Publisher Topic color = blue color = yellow
45. Message routing Message filter Recipient list Receive only a relevant subset of messages Controlled by subscriber Publisher remains completely unaware Send only a relevant subset of messages to a subscriber Controlled by publisher or separate component Potentially adds coupling Subscribers Publisher Subscribers Publisher Topic color = blue color = yellow Recipient List
46. Message routing Scatter-gather
47. Message routing Scatter-gather How to distribute a request across potentially interested / relevant parties and capture their individual responses? - RFQ scenarios, i.e. search for best response - Parallel processing scenarios, i.e. divide and conquer
48. Message routing Scatter-gather Requester Topic Responders How to distribute a request across potentially interested / relevant parties and capture their individual responses? - RFQ scenarios, i.e. search for best response - Parallel processing scenarios, i.e. divide and conquer
49. Message routing Scatter-gather Requester Topic Responders Queue How to distribute a request across potentially interested / relevant parties and capture their individual responses? - RFQ scenarios, i.e. search for best response - Parallel processing scenarios, i.e. divide and conquer
50. Message routing Scatter-gather Requester Topic Responders Queue Aggregator Processor How to distribute a request across potentially interested / relevant parties and capture their individual responses? - RFQ scenarios, i.e. search for best response - Parallel processing scenarios, i.e. divide and conquer
51. Message routing Pipes and filters
52. Message routing Pipes and filters Event source Result target
53. Message routing Pipes and filters Event triggers chain of processing steps (“filters”) Event source Pipe Filter Result target Step 1
54. Message routing Pipes and filters Event triggers chain of processing steps (“filters”) Knowledge of destination for next step(s) is wired into each filter Event source Pipe Filter Filter Pipe Pipe Result target … Filter Step 1 Step 2 Step n
55. Message routing Pipes and filters Event triggers chain of processing steps (“filters”) Knowledge of destination for next step(s) is wired into each filter Similar patterns: chain of responsibility, processing pipeline, saga choreography Event source Pipe Filter Filter Pipe Pipe Result target … Filter Step 1 Step 2 Step n
56. Message routing Saga orchestration
57. Message routing Saga orchestration Event source Result target
58. Message routing Saga orchestration Event triggers orchestrated workflow Event source Orchestrator Result target
59. Message routing Saga orchestration Event triggers orchestrated workflow Knowledge of workflow is externalized into orchestrator component, as well as for potential rollback Event source Orchestrator Result target
60. Message routing Saga orchestration Event triggers orchestrated workflow Knowledge of workflow is externalized into orchestrator component, as well as for potential rollback Workflow participants remain as loosely coupled as possible Processor Event source Orchestrator Step 1 Result target
61. Message routing Saga orchestration Event triggers orchestrated workflow Knowledge of workflow is externalized into orchestrator component, as well as for potential rollback Workflow participants remain as loosely coupled as possible Processor Processor Event source Orchestrator Step 1 Step 2 Result target
62. Message routing Saga orchestration Event triggers orchestrated workflow Knowledge of workflow is externalized into orchestrator component, as well as for potential rollback Workflow participants remain as loosely coupled as possible Processor Processor Event source Orchestrator … Step 1 Step 2 Result target
63. Message routing Saga orchestration Event triggers orchestrated workflow Knowledge of workflow is externalized into orchestrator component, as well as for potential rollback Workflow participants remain as loosely coupled as possible Processor Processor Processor Event source Orchestrator … Step 1 Step 2 Step n-1 Result target
64. Message routing Saga orchestration Event triggers orchestrated workflow Knowledge of workflow is externalized into orchestrator component, as well as for potential rollback Workflow participants remain as loosely coupled as possible Processor Processor Processor Processor Event source Orchestrator … Step 1 Step 2 Step n-1 Step n Result target
65. Message routing Saga orchestration AWS service for saga orchestration (serverless): AWS Step Functions Processor Processor Processor Processor Event source Orchestrator … Step 1 Step 2 Step n-1 Step n Result target
66. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
67. Context: Wild Rydes, Inc.
68. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
69. Use case: Submit a ride completion Unicorn Wild Rydes Unicorn App
70. Use case: Submit a ride completion { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion
71. Use case: Submit a ride completion AWS Cloud { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Unicorn Management Service Wild Rydes Unicorn App https://... submit-ride-completion
72. Use case: Submit a ride completion AWS Cloud { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion Rides Store Unicorn Management Service
73. Use case: Submit a ride completion AWS Cloud { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service
74. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service
75. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Interested in rides with fare >= x distance >= y Rides Store Unicorn Wild Rydes Unicorn App https://... submit-ride-completion Unicorn Management Service 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> }
76. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service Integration via database? Interested in rides with fare >= x distance >= y
77. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service Integration via database? Oh my! Interested in rides with fare >= x distance >= y
78. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service Integration via REST APIs? Interested in rides with fare >= x distance >= y
79. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Unicorn Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service Integration via REST APIs? Absolutely, but… Interested in rides with fare >= x distance >= y
80. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } https://... https://... https://... https://... https://... Recipient list Unicorn Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service
81. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } https://... https://... https://... https://... https://... Recipient list service Unicorn Request Distribution Service https://... Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service
82. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } https://... https://... https://... https://... https://... Self-managed filtering Unicorn Request Distribution Service https://... Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service Interested in rides with fare >= x distance >= y
83. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } https://... https://... https://... https://... https://... Self-managed filtering Unicorn Request Distribution Service https://... Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service Interested in rides with fare >= x distance >= y Integration via messaging? Absolutely!
84. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Publish-subscribe (topic) Unicorn Ride Completion Topic Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service
85. Use case: Submit a ride completion AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } SNS message filter: fare >= x distance >= y Message filter Unicorn Ride Completion Topic Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service
86. Use case: Submit a ride completion Unicorn AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Ride Completion Topic Topic-queue-chaining Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service SNS message filter: fare >= x distance >= y
87. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
88. Use case: Prebooking campaigns Wild Rydes Customer Wild Rydes Customer App
89. Use case: Prebooking campaigns Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." }
90. Use case: Prebooking campaigns AWS Cloud Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Ride Booking Service
91. Use case: Prebooking campaigns AWS Cloud Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking Ride Booking Service { "from": "...", "to": "...", "when": "...", "customer": "..." } Prebookings Store
92. Use case: Prebooking campaigns AWS Cloud Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } 201 Created Location: http://... Content-Location: ... { <prebooking-repr> } Ride Booking Service Prebookings Store
93. Use case: Prebooking campaigns AWS Cloud Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } 201 Created Location: http://... Content-Location: ... { <prebooking-repr> } Ride Booking Service Prebookings Store Massive campaign with CTA: Book today!
94. Use case: Prebooking campaigns AWS Cloud Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Ride Booking Service Further decoupling
95. Use case: Prebooking campaigns AWS Cloud Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Ride Booking Service Further decoupling Prebooking Submission Resource
96. Use case: Prebooking campaigns AWS Cloud Further decoupling Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Prebooking Notification Topic Ride Booking Service Prebooking Submission Resource
97. Use case: Prebooking campaigns AWS Cloud Further decoupling Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Prebooking Notification Topic 202 Accepted Location: ... Content-Location: ... { <task-status-repr> } Ride Booking Service Prebooking Submission Resource
98. Use case: Prebooking campaigns AWS Cloud Further decoupling Prebooking Notification Buffer Queue Prebooking Processing Buffer Queue Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Prebooking Notification Topic Ride Booking Service Prebooking Submission Resource 202 Accepted Location: ... Content-Location: ... { <task-status-repr> }
99. Use case: Prebooking campaigns AWS Cloud Datalake Ingestion Service Ride Booking Service / Prebooking Processing Resource Further decoupling Prebooking Notification Buffer Queue Prebooking Processing Buffer Queue Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Prebooking Notification Topic Ride Booking Service Prebooking Submission Resource 202 Accepted Location: ... Content-Location: ... { <task-status-repr> }
100. Use case: Prebooking campaigns AWS Cloud Datalake Ingestion Service Further decoupling Prebooking Notification Buffer Queue Prebooking Processing Buffer Queue Wild Rydes Customer Wild Rydes Customer App https://... submit-ride-prebooking { "from": "...", "to": "...", "when": "...", "customer": "..." } Prebooking Notification Topic Ride Booking Service Prebooking Submission Resource 202 Accepted Location: ... Content-Location: ... { <task-status-repr> } Massive campaign with CTA: Book now! Ride Booking Service / Prebooking Processing Resource
101. Use case: Prebooking campaigns Wild Rydes Customer Wild Rydes Customer App https://... AWS Cloud Datalake Ingestion Service Action=SendMessage &MessageBody=... ... Prebooking Notification Topic Even further decoupling Prebooking Notification Buffer Queue Prebooking Processing Buffer Queue Prebooking Submission Buffer Queue 200 OK ... <SendMessageResponse> ... </SendMessageResponse> Ride Booking Service Prebooking Submission Resource Ride Booking Service / Prebooking Processing Resource
102. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
103. Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App Scatter-gather
104. Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... submit-instant-ride-rfq { "from": "...", "to": "...", "customer": "..." } Scatter-gather
105. Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... submit-instant-ride-rfq AWS Cloud Ride Booking Service { "from": "...", "to": "...", "customer": "..." } Scatter-gather
106. Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... submit-instant-ride-rfq AWS Cloud Ride Booking Service { "from": "...", "to": "...", "customer": "..." } Scatter-gather 202 Accepted Location: ... Content-Location: ... { "links": { ... }, "status": "...", "eta": "..." }
107. Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... submit-instant-ride-rfq AWS Cloud Ride Booking Service { "from": "...", "to": "...", "customer": "..." } Request For Quotes Topic Scatter-gather 202 Accepted Location: ... Content-Location: ... { "links": { ... }, "status": "...", "eta": "..." }
108. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... submit-instant-ride-rfq AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource { "from": "...", "to": "...", "customer": "..." } Request For Quotes Topic Scatter-gather … 202 Accepted Location: ... Content-Location: ... { "links": { ... }, "status": "...", "eta": "..." }
109. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... submit-instant-ride-rfq AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource { "from": "...", "to": "...", "customer": "..." } Request For Quotes Topic Scatter-gather RFQ Response Queue … 202 Accepted Location: ... Content-Location: ... { "links": { ... }, "status": "...", "eta": "..." }
110. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... submit-instant-ride-rfq AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource { "from": "...", "to": "...", "customer": "..." } Request For Quotes Topic Scatter-gather 202 Accepted Location: ... Content-Location: ... { "links": { ... }, "status": "...", "eta": "..." } RFQ Response Queue …
111. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... retrieve-rfq-status AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource Request For Quotes Topic Scatter-gather RFQ Response Queue …
112. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... retrieve-rfq-status AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource Request For Quotes Topic Scatter-gather RFQ Response Queue … 200 OK { "links": { ... }, "status": "running", "eta": "..." }
113. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... retrieve-rfq-status AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource Request For Quotes Topic Scatter-gather RFQ Response Queue … 200 OK { "links": { ... <link-to-result> ... }, "status": "done" }
114. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... retrieve-rfq-result AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource Request For Quotes Topic Scatter-gather RFQ Response Queue …
115. Unicorn Management Service Use case: Instant ride RFQ Wild Rydes Customer Wild Rydes Customer App https://... retrieve-rfq-result AWS Cloud Ride Booking Service Unicorn Management Resource Unicorn Management Resource Unicorn Management Resource Request For Quotes Topic Scatter-gather RFQ Response Queue … 200 OK { "links": { ... }, "from": "...", "to": "...", "quotes": "..." }
116. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
117. Use case: Submit a ride completion Unicorn AWS Cloud Customer Notification Service Customer Accounting Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Ride Completion Topic Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service SNS message filter: fare >= x distance >= y
118. Use case: Submit a ride completion Unicorn AWS Cloud Customer Notification Service Customer Loyalty Service Datalake Ingestion Service Extraordinary Rides Service { "from": "...", "to": "...", "duration": "...", "distance": "...", "customer": "...", "fare": "..." } Ride Completion Topic Wild Rydes Unicorn App https://... submit-ride-completion 201 Created Location: ... Content-Location: ... { <cmpl-ride-repr> } Rides Store Unicorn Management Service SNS message filter: fare >= x distance >= y Customer Accounting Service
119. Use case: Fare collection Saga orchestration
120. Use case: Fare collection Saga orchestration Payment Service Discrete transactions: 1. Credit card pre-auth Payment Gateway API
121. Use case: Fare collection Saga orchestration Payment Service Discrete transactions: 1. Credit card pre-auth 2. Charge card using pre-auth code Payment Gateway API Payment Service Payment Gateway API
122. Use case: Fare collection Saga orchestration Payment Service Discrete transactions: 1. Credit card pre-auth 2. Charge card using pre-auth code 3. Update customer account Payment Gateway API Customer Accounting Service Payment Service Accounting System Payment Gateway API
123. Use case: Fare collection Saga orchestration Payment Service Discrete transactions: 1. Credit card pre-auth 2. Charge card using pre-auth code 3. Update customer account To be treated as one distributed TA, to leave the systems in a semantically consistent state. Payment Gateway API Customer Accounting Service Payment Service Accounting System Payment Gateway API
124. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
125. Resources / call-to-action
126. Resources / call-to-action AWS blogs and other content about application integration http://bit.ly/2019-api315
127. Resources / call-to-action AWS blogs and other content about application integration http://bit.ly/2019-api315 Hands-on workshop on implementing the patterns from this talk ARC314 during this re:Invent (Monday + Tuesday) Ask your AWS SA for an application integration immersion day
128. Resources / call-to-action AWS blogs and other content about application integration http://bit.ly/2019-api315 Hands-on workshop on implementing the patterns from this talk ARC314 during this re:Invent (Monday + Tuesday) Ask your AWS SA for an application integration immersion day Keep in mind Loose coupling is always better than lousy coupling!
129. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
130. Thank you! © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Dirk Fröhner @dirk_f5r