Every requirement and recommendation in the VCF design guidance lists these: the knock-on effects of a choice, whether good or bad. Typical ones are cost, footprint, operational effort, dependencies, impact on other qualities and options that are no longer open.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Implication in context, with comparison tables and the common traps.
Terms in this definition
- Requirement
A need that is stated clearly enough to be measured or tested, leaves no ambiguity and is essential for the result to be accepted.
- VMware Cloud Foundation
Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.
- Table options
Set only at creation with
OPTIONS, these key-value storage settings can't be altered or dropped afterwards; on Delta tables they also show up among the table properties.
Related terms
- Decision record
Documents a single design decision: what was chosen, why that beats the other options, which requirements or constraints it answers, and its consequences, such as cost, options ruled out and effects on teams and other qualities. VCF design elements share the ID, justification and implication layout without linking back to any customer's requirements.
- Design decision
Explains, for one choice made in a design, the requirement or constraint it serves, the reasoning, the consequences and what was actually decided. VCF's design guide writes up its own recommendations and requirements using that same pattern of ID, justification and implication.
- Design element
A single entry in the VCF design guide, be it a requirement, a recommendation or a choice, labelled with an ID and accompanied by justification and implication text. Elements outside the chosen configuration are not implemented.