There are many others within code, infrastructure, networking, business processes, etc.
INDIRECTION BAND SOFTWARE
This is just one example of indirection within a software system. However, these trade-offs are typically negligible as your system scales out to more and more moving parts. Some of the trade-offs with this approach include absorbing the added complexity of introducing the queuing infrastructure and properly handling asynchronous tasks. No team dictates the others' methodologies or workflows.Engineering teams can independently optimize and iterate on their components, maintaining separate software development life cycles.Documentation can be a simple diagram and a brief description of the expected message payload.This new approach has the following advantages: One of those subscribers can be a queue that is processed by the order management service, which asynchronously handles the message.
Rather than having the website communicate directly with the order processing service, we can have it store the order and publish a message to inform subscribers that an order has been placed. Let's get back to our e-commerce site example and explore how adding a level of indirection, through infrastructure, can optimize the communication between teams and components. Luckily, technology has evolved to give us more powerful tools for adding levels of indirection in code, and in infrastructure, that can lessen the burden of maintaining highly detailed documents. Engineers are notoriously bad at maintaining technical documents. This strategy, although effective at times, is not scalable. And if that situation does start occurring, we mitigate that issue with tools like Confluence to ensure that the documentation lives in "one place." We typically don't want developers sending emails to each other every time there is a need to integrate two or more components. Documentation is itself a level of indirection. Traditionally, documentation provided a way for engineers to effectively communicate their deliverables to other teams. The breakdown occurs because of the entanglement between the two teams.
0 kommentar(er)
