Serverless for Teams
Stackery sponsored this podcast.
A pay-as-you-go pricing model and increased velocity are two well-known effects that serverless technologies have on application delivery. Just as important, but often overlooked, is how serverless affects developer workflows and team dynamics. Rather than focusing entirely on business logic and code, developers take on more responsibility for configuring cloud resources.
“[Serverless] redistributes the responsibility of operations work and in the grand scheme it actually enforces the DevOps model,” Nate Taggart, CEO of Stackery, said. “Serverless is fundamentally DevOps. It’s developers having to iterate over operations work in the same cycle as their development work.”
Serverless adoption doesn’t start with the chief technology officer, Taggart said. Instead, organizations typically adopt serverless because their engineers have started to use AWS Lambda on their own in an effort to ship features faster. The absence of governance can create resiliency and scaling problems for organizations, as individual developers bring their own workflows into a team dynamic. Operations teams quickly lose visibility and control into the application as a whole, and rollbacks and troubleshooting become a concern.
“It’s actually harder to do serverless development with two engineers than it is with one engineer. And [the problem] scales up,” Taggart said.
In order to maintain efficiency and velocity, it becomes important for an organization to set standard practices for serverless architecture. This ensures that individual workflows can scale across the organization, and provides visibility and consistency in application delivery. For example, teams can adopt a playbook for how to roll back changes or know who shipped a commit.
In this podcast, learn how serverless architecture affects developer workflows and team dynamics, how serverless delivers on the DevOps ideal, and some of the ways that teams can begin to standardize practices around serverless application development with Stackery’s serverless toolkit.
In this Edition:
2:11: What is your approach to this serverless for teams idea?
6:38: What are some of the behaviors you’ve come across that Stackery has been learning?
13:17: How does version control change in the serverless world?
19:02: Exploring the serverless model and governance
21:57: Taggart’s perspective on serverless architectures in production versus on side projects
26:46: Why serverless development is more difficult with two engineers than with one
Feature image via Pixabay.
