1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Z U R I C H|1 1 S E P T E M B E R 2 0 2 5 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Integration patterns for distributed systemsDirk FrhnerA P P 3 0 6(he/him)Principal Solutions ArchitectAmazon Web ServicesM
2、aximilian SchellhornNicols Dorado(he/him)Senior Solutions ArchitectAmazon Web Services(he/him)Senior Director Professional ServicesNagravision,Kudelski Group 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Connecting two systemsBSync/async?Interaction model?Data format?Pub-sub or
3、point-to-point?Conversation state?Error handling?Distributed?Partial failures?Retries?Idempotency?Backoff?Data or control flow?Polling?Systems or instances?AMessages vs.events?Dedicated vs.shared resources?2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.No architecture decision yo
4、u take comes without trade-offs.Every architecture decision brings some pain.Your job as software architect is to identify the least painful option on the table.DirkTrying to manage expectations 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Distributed system fundamentalsCouplin
5、g and its dimensionsDependencies between systemsControl flow and data flowPushing messages vs.pulling messagesDelivery semantics and message orderRetries,how-often,and FIFO delivery*selection of very relevant aspects 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Distributed syst
6、em fundamentalsCoupling and its dimensionsDependencies between systemsControl flow and data flowPushing messages vs.pulling messagesDelivery semantics and message orderRetries,how-often,and FIFO delivery 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Distributed system fundamenta