Chapter 10. Validating at Scale
For digital products hosted in CSPs, the resources that host, store, and serve your content, your infrastructure, are the foundation for your operations. It’s like the land and structures on and in which a purveyor of commodity goods conducts business. Without it, you have no permanence and no guaranteed business continuity. In the case of physical infrastructure—the buildings you occupy and the ground beneath them, for example—you’re easily able to see, with your own eyes, the state of affairs: the building is in need of repair after an unforeseen event or due for an upgrade from normal wear and tear; that it is sinking due to unstable ground. You would even likely have protocols and contingencies in place, either codified in corporate guidance or provided for you by local government bodies, in the case of both deprecation and disasters that were established and refined over hundreds—if not effectively thousands—of years of evolution in commercial practices. Given that the concept of web-based software is still only a few decades old and the cloud computing paradigm even much younger, and since we don’t have the ability to physically see with our own eyes the components that make up our infrastructure, we must fast-forward the advancement of validation and auditability with limited stock visibility.
Over time, different techniques have been developed to validate software. Some of them, such as the classic debug-with-logs technique, are applicable ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access