At VMware we define Continuous Verification as:
“A process of querying external systems and using information from the response to make decisions to improve the development and deployment process.”
At #OSSDay, I got a chance to not only talk about what that means for serverless apps and how you can build it into your existing pipelines using tools like GitLab, CloudHealth, Wavefront and Gotling.
Continuous Verification, by default, means it’s an extension to the existing development and deployment processes that companies already have. That extension focuses on optimizing both the development and deployment experience for those companies by looking at security, performance, and cost. At most companies, some of these steps are done manually or scripted, but hardly ever are they really part of the deployment pipeline. In this session, we’ll look at extending an existing CI/CD pipeline with checks for security, performance, and cost to make a decision on whether we want to deploy our app or not.
- Continuous Verification: The Missing Link to Fully Automate Your Pipeline
- Prowler: AWS Security Best Practices Assessment, Auditing, Hardening and Forensics Readiness Tool
- ACME Serverless Fitness Shop - Payment Service
- Tanzu Observability powered by Wavefront
- The ACME Fitness Shop