1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Maximilian Schellhorn(he/him)Senior Solutions ArchitectAWSDirk Frhner(he/him)Principal Solutions A
2、rchitectAWSIntegration patterns fordistributed systemsA P I 3 1 5 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.All photos by Dirk Frhner 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.In(modern)systems design,integration isnt an afterthought,but an essential
3、 part of the application architecture and the software delivery lifecycle.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Connecting two systemsBA 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Connecting two systemsBA 2025,Amazon Web Services,Inc.or its affili
4、ates.All rights reserved.Connecting two systemsBA 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Connecting two systemsBSync/async?Interaction model?Data format?Pub-sub or point-to-point?Conversation state?Error handling?Distributed?Partial failures?Retries?Idempotency?Backoff?Da
5、ta 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.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.DirkTrying to manage expectationsNo architecture decision comes with
6、out trade-offs-every decision brings some pain.Your job as software architect is to identify the least painful option on the table.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Distributed system fundamentalsCoupling andits dimensionsDelivery semantics and message orderControl f