Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Consent Architecture”
Consent Propagation
Ensuring a consent decision reaches and is honoured by every system that processes the data, including those that received it before the decision changed.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Architecture Decision Log
The ordered, immutable collection of a system's decision records, read as a history rather than as a specification.
Architecture Decision Record
A short, immutable document capturing one architectural decision, its context, the alternatives, and its consequences.
Architecture Development Method
TOGAF's iterative cycle for developing enterprise architecture, which is valuable as a checklist of concerns and harmful when followed literally.
Architecture Principle
A durable, agreed rule that constrains design decisions in advance, stated with its rationale and its implications.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Architecture Roadmap
A sequenced plan of architectural change expressed as capability outcomes and decision points rather than as a fixed timeline of projects.
Architecture Sinkhole
A request that passes through every layer of a layered architecture without any layer adding logic, indicating that the layering is pure overhead for that path.
Architecture Style
A named, coarse-grained way of organising a whole system, as distinct from a pattern that solves one recurring problem inside it.
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.
Architecture Viewpoint
A perspective on a system tailored to the concerns of a particular audience, recognising that no single diagram serves everyone.
Cell-Based Architecture
Partitioning a service into complete, independent copies of itself, each serving a subset of customers, so a failure is bounded to one cell.
Clean Architecture
Concentric layers with a strict dependency rule — source code dependencies point only inwards, towards higher-level policy.
Consent Management
Capturing, storing, honouring and evidencing a data subject's permissions for specific processing purposes, including withdrawal.
A regulator asks how you ensure marketing consent withdrawal is honoured everywhere. What does the architecture need to show?
The answer they want is mechanism plus evidence Not "we have a consent database". They want to see how a withdrawal reaches every system that could act on it, a
A CFO asks why the architecture function should be funded when it ships no features. You have five minutes. What do you say?
Do not answer with activities "We produce standards, run a review board and maintain the technology radar" describes what the function does, not what the busine
Architecture decisions in your organisation are either ignored or bottlenecked in a review board. Design something better.
Why both failure modes have the same cause A review board is a synchronous, low bandwidth, high latency channel: teams wait, decisions are made by people distan
Consent Architecture
Capturing, versioning and propagating consent to every system that acts on the data.
AI-Era Architecture
General material on architecting systems that include models.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Architecture Communication
General material on communicating architecture.
Architecture Compliance Checks
Automating conformance to standards so review effort goes to the genuinely novel.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Architecture Decision-Making
General material on making and recording architectural decisions.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Architecture Documentation
What to write down, at what altitude, and what nobody will ever read.
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Patterns
General material on architectural patterns and their trade-offs.
Architecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Architecture Reviews
Reviewing early enough to influence rather than to veto.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
Architecture Styles
System-level organising shapes, and how they differ from problem-level patterns.
Business Architecture
General material on the business side of architecture.
Cell-Based Architecture
Complete isolated copies each serving a subset of customers.
Certification Impact on Architecture
What SOC 2 and ISO 27001 actually require of a design, and what they do not.
Clean Architecture
Concentric layers with dependencies pointing only inwards.
Client State Architecture
Server state, UI state and derived state, and why conflating them causes most bugs.
Cloud Architecture
General material on designing for cloud platforms.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Data Architecture
General material on structuring, storing and governing data.
Data Platform Architecture
General material on designing the analytical data estate end to end.
AI-Era Architecture
AI workloads meeting security, data, networking, reliability and cost.
API & Integration Architecture
Contracts between systems, and the compatibility discipline that keeps them working.
Architecture Communication
Explain the same architecture to a CEO, an engineering manager and an engineer.
Architecture Decision-Making
Where senior engineer becomes architect: evaluate, choose, write it down.
Architecture Fundamentals
What architecture actually is: drivers, constraints, trade-offs and the principles behind them.
Architecture Patterns
Patterns as tools for recurring problems, with forces and consequences.
Business Architecture
Connecting technology decisions to the outcomes that fund them.
Cloud Architecture
Cloud as a set of architectural capabilities, not a catalogue of service names.
Cost Architecture & FinOps
Architecture is also economics; exceptional architects can price their designs.
Data Architecture
Where state lives, how it is modelled, replicated, partitioned and governed.
Data Platform Architecture
The analytical estate: storage layout, ingestion, transformation and the compute that reads it.