# System Architecture & Design Developers are obsessed with architecture patterns. There are many ways of writing the same application. Each stating its superiority over the other. Our approach is to keep the user and the customer's business needs at the center. We then work our way upward, keeping budget and time constraints in mind to pick the right design pattern. In most cases the best design patterns are simple. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://playbook.wednesday.is/engineering-playbook/system-architecture-and-design.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.