Official documentation made the disposable microVM model and default network restrictions understandable. It was not selected because the documented fixed CPU allocation offered less control for this small workload and the service was described as pre-release.
- What worked
- The security boundary and network defaults were clear enough to compare directly with the project requirements.
- What got in the way
- The available CPU configuration did not match the desired strict, low per-execution cap, and the pre-release status increased operational uncertainty.
