Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
36 results for “Branching Models”
Merge Queue
A serialising gate that tests each change against the current tip before merging, so a green branch cannot break the mainline.
Cloud Pricing Models
The purchase options for cloud compute — on-demand, committed use, and spot — which differ by up to 90% for identical hardware.
Burstable Instance
An instance that provides a low baseline CPU allocation and accrues credits while idle, spendable for short periods of full performance.
Capability Model
A structured map of what a business does, independent of how it is organised or which systems support it, used to align technology investment with function.
Causal Consistency
A model guaranteeing that operations which causally depend on one another are seen in the same order everywhere, while concurrent operations may be seen in any order.
Consistent Prefix Read
A guarantee that if a sequence of writes happens in a given order, a reader sees a prefix of that sequence — never an out-of-order subset.
Egress Pricing
The asymmetric charging model in which data entering a cloud is free and data leaving is billed, shaping architecture more than compute pricing does.
Embedding Model Migration
The process of moving a corpus to a new embedding model, which requires re-embedding everything because vectors from different models are not comparable.
Instance Family
A group of instance types sharing a resource profile — general purpose, compute optimised, memory optimised, storage optimised, accelerated — chosen by which resource the workload…
Linearizability
The strongest single-object guarantee — every operation appears to take effect instantaneously at some point between its call and its return.
Model Inventory
A complete register of models in use with their purpose, owner, risk tier and validation status — the artifact everything else in model governance depends on.
Operating Model
How an organisation arranges people, process, technology and governance to deliver its capabilities, which constrains architecture as strongly as any technical factor.
Purpose-Based Access
Granting access for a stated and recorded purpose rather than by role alone, which is what several data protection regimes actually require.
Read-Your-Writes Consistency
A session guarantee that a client always sees its own updates, even when reads are served from replicas that may lag.
Trunk-Based Development
All developers integrating small changes into a single shared branch at least daily, with long-lived branches avoided entirely.
Trust Boundary Diagram
A diagram marking where data crosses between zones of differing trust, which is the structure a threat model is built on and the form security findings are best communicated in.
A transformation project has grown to 600 models with chains twelve deep. A change at the base has an unknowable blast radius. What do you do?
Treat it as a software architecture problem, because it is one Six hundred models with twelve deep chains is a codebase with no module boundaries. The remedies
A vendor SaaS product embeds a model that scores customers, and its output drives an automated decision in your process. Your model governance framework covers models you build. What do you do?
The obligation does not transfer with the outsourcing You are accountable for the decision. That the scoring is performed by a vendor changes who operates the m
A fleet of 200 instances averages 15% CPU and 85% memory. Finance wants a 40% cost reduction. What do you do?
The diagnosis The instance family is wrong. 15% CPU and 85% memory means the workload is memory bound running on general purpose or compute optimised instances,
Branching Models
GitFlow, trunk and release branches as delivery constraints rather than Git preferences.
Cloud Pricing Models
On-demand, committed and spot, and the crossover arithmetic.
Communicating Threat Models
Making risk legible to people who will fund or accept it.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Consistency Models
Linearizable, sequential, causal, eventual, and the session guarantees between them.
Data Access Models
Role, attribute and purpose-based access over analytical data, and how they compose.
Operating Models
How delivery, platform and governance functions fit together.
Reference Models
Shared conceptual frames — layering, tiers, viewpoints — and their limits.
AI-Era Architecture
General material on architecting systems that include models.
CQRS
Separating the write model from the read models that serve queries.
CQRS
Separate models for writing and reading, each optimised for its job.
Model Risk Management
Inventory, validation, monitoring and challenge for models that make consequential decisions.
Performance Test Design
Workload models, warm-up, think time, and the distribution the average hides.
Transformation Frameworks
Declarative SQL transformation with tests, lineage and versioned models.