Complete the sentences with the words from the box

tightly coupled · decompose · network latency · distributed system · cohesion · service mesh · loosely coupled · modular monolith · service boundary · coupling · domain-driven design · bounded context

• Because the modules in Chicago were so ____ , we couldn't change the payment system without breaking the billing service.
• By designing a ____ system, our Seattle engineers can deploy updates to the shipping service independently.
• The architects in Boston used ____ to align the software structure with our business departments.
• We need to define a clear ____ around our order processing so that no other team can directly modify its database.
• If you want to transition to microservices, you must first ____ your massive legacy application into smaller parts.
• Our Dallas team chose a ____ because it keeps the code in one repository but separates the logical modules clearly.
• When we moved to a ____ , we spent too much time dealing with network calls instead of actual business logic.
• To manage secure communication and load balancing between our services, we installed a modern ____ in our Seattle cloud.
• Because of high ____ between London and New York, our distributed transactions are taking too long.
• The main issue with our current architecture is high ____ , meaning our modules know too much about each other's internals.
• To make our Boston codebase easier to maintain, we should aim for high ____ , keeping related functions together in the same module.
• Before we write any code, we must establish a strict ____ so that our inventory team doesn't interfere with the checkout team.

Sources: photo by Anna Tarazevich on Pexels