DevOps in a Serverless Environment: The Common Blind Spots

Blind Spot 1: Serverless DevOps is the Same as Non-serverless

What to Watch Out For

DevOps in a serverless environment is fundamentally different, just like developing microservices is fundamentally different than working on a monolithic application.

Actions You Can Take to MitigateThis Blind Spot

To be successful with DevOps in a serverless environment, you’ll need to change your mindset. Doing so will change your processes so you can scale to accommodate the multitude of microservices that need to be deployed.

Blind Spot 2: Planning and Defining Your Process Before Implementing Automation

What to Watch Out For

It can be tempting to create automation for a single microservice’s deployment simply to get things going. Doing this can cause a problem as you can get stuck doing that every single time you have a new microservice. You’ll end up cloning that process and creating CI/CD automation for each microservice over and over.

Actions You Can Take to Mitigate This Blind Spot

When you add microservices, create templates and models that speed up onboarding. It can culminate in onboarding checklists. Process development should be done from the beginning of your DevOps journey. Every new development should be part of the process.

Blind Spot 3: Scaling Your DevOpsProcesses

What to Watch Out For

It’s short-sighted to assume you’ll only have a few microservices. If you start with that mentality, you’ll end up with processes that work today, but need to be completely re-designed tomorrow when your serverless footprint inevitably grows.

Actions You Can Take to Mitigate This Blind Spot

No matter how many microservices you have today, plan as if you have 100 times that amount. In our experience, we’ve never seen an AWS serverless implementation that contained fewer than 5 AWS Lambdas. As you add connectors and increase connectivity, it will only go up from there.

Blind Spot 4: Communications

What to Watch Out For

Historically, there has been a breakdown in communication between admins and developers. With the emergence of DevOps, that can be transferred to a communication breakdown between DevOps engineers and developers.

Actions You Can Take to Mitigate This Blind Spot

It’s up to DevOps to evangelize their processes to developers. DevOps should encourage collaboration, and the process should be communicated and enforced in coordination with the developers.

Blind Spot 5: The Perception ThatServerless Implementations Can Be Successful Without DevOps

What to Watch Out for

This blind spot may sound a little radical. You CAN indeed be successful with a serverless implementation without DevOps.

Actions You Can Take to Mitigate This Blind Spot

Serverless implementations go hand in hand with DevOps. There is no getting around it. As you plan to implement projects using serverless, you should bake DevOps design and implementation into the plan.

Blind Spot 6: Is it Measurable? DevOps Can Be Taken for Granted

What to Watch Out for

What does a successful serverless implementation look like for your organization? How will you know if you’ve achieved it? More importantly, how will the CIO realize you’ve achieved it?

Actions You Can Take to Mitigate This Blind Spot

Start with a baseline of your measures before DevOps is implemented if you can. If you’ve already started, take a look back at sprint retrospectives and velocities as well as other key measures that may already exist.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Aaron Lieberman

Aaron Lieberman

19 Followers

Aaron’s passion for technology drives him to find innovative ways to help advance organizations through technology.