Skip to main content
Continuous Verification In A Serverless World @ Open Source Community Day
  1. Blog/

Continuous Verification In A Serverless World @ Open Source Community Day

·1 min·
Table of Contents

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.

The talk
#

Continuous Verification is an extension to the development and deployment processes companies already have. It focuses on optimizing both the development and deployment experience by looking at security, performance, and cost. At most companies, some of these steps are done manually or scripted, but they’re rarely part of the actual deployment pipeline. In this session, we look at extending an existing CI/CD pipeline with checks for security, performance, and cost to make a decision on whether to deploy or not.

Slides
#

Talk materials
#

Related

Continuous Verification In A Serverless World @ Serverless Nashville

·1 min
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 Serverless Nashville, I got a chance to not only talk about what that means for serverless apps but also how we use serverless in some of the business units at VMware.

Building a Serverless Fitness Shop - Observability

·5 mins
If you’ve read the blog posts on CloudJourney.io before, you’ve likely come across the term “Continuous Verification”. If not, no worries. There’s a solid article from Dan Illson and Bill Shetti on The New Stack that explains it in detail. The short version: Continuous Verification means putting as many automated checks as possible into your CI/CD pipelines. More checks, fewer manual tasks, more data to smooth out and improve your development and deployment process. So far we covered the tools and technologies, Continuous Integration, and Infrastructure as Code aspects of the ACME Serverless Fitness Shop. This post is about observability.

Building a Serverless Fitness Shop - Infrastructure as Code

·7 mins
If you’ve read the blog posts on CloudJourney.io before, you’ve likely come across the term “Continuous Verification”. If not, no worries. There’s a solid article from Dan Illson and Bill Shetti on The New Stack that explains it in detail. The short version: Continuous Verification means putting as many automated checks as possible into your CI/CD pipelines. More checks, fewer manual tasks, more data to smooth out and improve your development and deployment process. In part one we covered the tools and technologies and in part two we covered the Continuous Integration aspect of the ACME Serverless Fitness Shop. This post is about Infrastructure as Code.