A small, targeted technical experiment for resolving uncertainty before committing to an implementation path.
A code spike is a small, targeted technical experiment that helps answer a risky question before the team commits weeks or months to an implementation path. section 2.3
Test the unknowns
A team might use a spike to check whether a third-party library can handle its scale or whether a cloud service is a good fit. section 2.3
How Grokking Software Architecture covers it
How deep it goes
Defines spikes as targeted experiments but gives no execution steps or evaluation criteria.
Examples
Checks whether a third-party library can handle scale or whether a cloud service is suitable.
What you can do after
Apply targeted experiments to resolve technical questions before committing to a risky path.
How it connects
Connects software architecture with technical risk and implementation decisions.
enabler storykind of · An enabler story is an Agile work item supporting exploration, architecture, infrastructure, compliance, or other activities needed to enable future functionality.
risk scoutused by · A Risk Scout is an architectural role responsible for identifying and investigating technical risks before they impede development.
test-driven developmentused by · Test-driven development is a software development practice in which tests specify expected behavior and guide incremental implementation, typically being written before the corresponding code.
learning testuses · A learning test is an automated test that verifies assumptions about code and teaches how that code behaves.
set-based designused by · An engineering approach that explores multiple design options in parallel, narrows them as evidence arrives, and delays commitment until further exploration is no longer worthwhile.
This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.