Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
32 results for “Trade-off Analysis Methods”
Architecture Trade-off Analysis Method
A structured evaluation that scores an architecture against prioritised quality-attribute scenarios and identifies the points where those attributes conflict.
Trade-off Analysis
Making the costs of an architectural choice explicit and comparable, rather than presenting a recommendation as if it were free.
Cost vs Reliability Trade-off
The non-linear relationship between availability and spend, which makes each additional nine roughly an order of magnitude more expensive.
Security vs Usability
A trade-off that is usually resolved by varying the control with the value of the action, rather than by choosing a uniform level of friction.
Dropbox's Move Off S3
Dropbox moved the majority of its file storage off Amazon S3 onto custom infrastructure, reporting savings that its S-1 filing put at roughly $75 million over two years.
Egress Path Analysis
Tracing where data physically moves in an architecture, because transfer charges follow paths that appear nowhere on the diagram.
Stakeholder Analysis
Identifying who is affected by an architecture, what each of them needs from it, and how much influence they have over whether it proceeds.
Delivery vs Maintainability
Choosing where to take deliberate shortcuts, based on which kinds of debt are cheap to repay and which compound.
Denormalisation
Deliberately duplicating data across records to make reads cheap, accepting the write-time cost of keeping copies in step.
Etsy's Continuous Deployment
Etsy moved from infrequent, risky releases to dozens of deploys a day, demonstrating that deployment frequency and stability improve together rather than trading off.
First-Principles Reasoning
Reducing a problem to the physical, mathematical or economic facts it rests on, then reasoning up, rather than reasoning from analogy or convention.
Monolith vs Microservices
A trade of deployment independence against distributed-systems complexity, decided by team topology far more often than by technology.
Negotiation
Reaching an agreement that both sides own, by trading on interests rather than arguing positions.
Operational vs Analytical Store
The separation between the store serving the application's transactions and the one serving reporting and analysis, and the mechanism connecting them.
REST
An architectural style for APIs built on resources identified by URLs, manipulated with uniform HTTP methods, and stateless requests.
Time to Market
How long it takes to get a capability in front of customers — often the constraint that dominates every other architectural quality.
Netflix built its own CDN; Dropbox moved storage off S3. Both are usually wrong. What conditions made them right, and how do you test for those conditions?
What the interviewer is testing Whether you can extract the conditions from a famous decision rather than the decision itself. These two cases are the most comm
The team can ship in six weeks with an approach that will need rework, or five months with one that will not. How do you decide, and what do you do either way?
What the interviewer is testing Whether you can make a debt decision deliberately rather than by default, and whether you know which debts are cheap and which a
Trade-off Analysis Methods
ATAM, scenarios, and naming the points where qualities conflict.
Trade-off Analysis
Making costs explicit and comparable rather than asserting a preference.
Trade-off Fundamentals
Why every architecture is a set of purchases, and how to state what you gave up.
Bottleneck Analysis
Finding the constraint, and expecting a second one behind it.
Explaining Trade-offs
Naming what was given up, and the condition that would change it.
Stakeholder Analysis
Who is affected, what they need, and who can block you late.
Architecture Patterns
General material on architectural patterns and their trade-offs.
Capability Maps in EA
The stable frame for hanging investment, ownership and health off.
DORA Metrics
Throughput and stability moving together rather than trading off.
Decommissioning
Actually switching the old system off, and proving nothing depended on it.
Multi-Agent Systems
Coordination, hand-off and whether more agents actually help.
REST Design
Resources, uniform methods, status codes and statelessness.
Time to Market
The constraint that dominates most products, and how to trade against it.