Jan 2, 2019 · 17m · a16z
a16z Podcast | Containing the Monolith -- From Microservices to DevOps
Martin Casado · 5m spoken Florian Leibert · 3m spoken Matt Biilmann · 3m spoken Kartik Rao · 3m spoken Sonal Chokshi · 33s spoken
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this panel moderated by Martin Casado, technology leaders discuss the evolution of software development, focusing on the shift from monolithic architectures to microservices, developer-driven operations, and automated CI/CD pipelines. They explore how tools like containerization, real-time telemetry, and Git-centric workflows enable rapid deployment and transform operational roles across modern and legacy enterprises.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
The host as informed peer 6.8 Guest teaching 3.4 Guest disagreement 2.2 The host pushing back 4.4
speaking balance: gold is the host, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 11:01 Florian predicts the total elimination of operations
Florian boldly claims that the entire operations role will disappear over time due to cloud automation, dismissing traditional ops infrastructure.
Hardest push from the host ▶ 11:07 Martin calls out the trillion-dollar operations marketMartin refuses to accept Florian's assertion that operations is disappearing, immediately interrupting to challenge the premise by referencing the massive size of the operations industry.
Biggest teaching moment ▶ 4:08 Matt provides metrics on backend developer declineMatt illustrates the shift to front-end microservice architectures by citing a real-world agency example where backend developer count dropped from 35 down to 2.
The host holds their own ▶ 13:50 Martin articulates the language-level infrastructure shiftMartin demonstrates deep technical vision by explaining how standardized CI/CD enables infrastructure vendors to integrate directly into application code, converting traditional appliance boxes into software libraries.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The host as informed peer | Guest teaching | Guest disagreement | The host pushing back | Why |
|---|---|---|---|---|---|---|
| Shift in IT Purchasing Power from Operations to Developers | 6 | 3 | 2 | 3 | Martin synthesizes the evolution of IT purchasing power into a structured layered-cake model, asking if data scientists now sit atop developers in influence. Florian adds nuance regarding platform services and playfully compares writing Visual Basic to Go to emphasize business output over technical plumbing. | |
| The Rise of Front-End Developers and Microservices Architecture | 7 | 3 | 1 | 4 | Martin demonstrates deep industry knowledge by citing specific tools like PubNub and Twilio while probing whether backend developers are becoming obsolete. Matt validates this with concrete real-world agency data showing a drop from 35 backend developers down to just two. | |
| Deep Integration with the CI/CD Pipeline and Git Workflows | 6 | 4 | 3 | 6 | Martin directly challenges the merging of development and deployment workflows, stating that removing dedicated ops teams sounds dangerous. Matt counters by explaining how immutable deploys, instant rollbacks, and automated staging environments mitigate deployment risks. | |
| The Future of Operations and Autonomous Infrastructure | 7 | 4 | 4 | 7 | Martin forcefully pushes back against Florian's claim that operations roles will disappear, pointing out that operations represents a trillion-dollar market. Florian doubles down by highlighting DBA errors, while Kartik politely disagrees with Florian by emphasizing specialized operational engineering skills. | |
| Containerization, Signal Collection, and Changing Developer Incentives | 8 | 3 | 1 | 2 | Martin offers an expert architectural thesis that standard CI/CD shifts the infrastructure boundary into programming languages, effectively turning hardware boxes into software libraries. The guests validate his framing and share insights on enterprise legacy migration and deployment telemetry. |
Statements from this episode (12)
Casado: Developers are increasingly driving IT infrastructure purchasing decisions
“If you sold something that was a piece of infrastructure, you sell it to the ops person or core IT or whatever. More and more developers are involved in this purchasing decision.”
Leibert: Writing Visual Basic is more joyful than writing Go applications
“And frankly, it's more joyful to write Visual Basic than it is to write Go, right? That you actually achieve Business results. I mean, seriously, right? Like, writing a Spark job, you see the output right away, whereas if you write a large Go application, I me…”
Front-End Developers Are Replacing Monolithic Backend Development via Microservices
“We used to have this very clear distinction between the back-end developers and then front-end developers that worked with the web were barely really developers. They would mostly take some design file and then cut it up and hand it over to a back-end develope…”
Biilmann: Agency cut backend developers from 35 to 2 using microservices
“We talked to one agency that's really been a pioneer of adopting this model you talked about of building sites that used to have, like, 55 developers instead, where 35 of those were back-end developers. And now they have around 33 developers, and two of them a…”
Karthik Rao: Software Deployment Velocity Shifted From Annual Updates to Tens of Thousands
“Instead of doing two or three updates a year, you could be doing thousands or tens of thousands of updates a year. And so, you know, the entire development lifecycle, deployment lifecycle, the entire toolset is evolving to support velocity. So how you design y…”
Biilmann: Git has become software developers' universal workflow engine
“Git has been such a massive trend that's been adopted by Developers universally, and it's become not just their version control system, but their main workflow engine and their main way of collaboration and communication, even in, in issues around Git and so o…”
Leibert: Traditional software operator roles will disappear over time
“So, I mean, I think the whole operator is going to go away over time, like with cloud, with tools like... Yeah, I think it's going to, I think, like, we're going to go towards a world where a lot of that stuff is autonomous.”
Leibert: Automated systems make dedicated database administrators obsolete
“But if you have systems where a lot of the recovery of failures is actually built in, and the level of automation is really high, you actually don't need these DBAs anymore sitting around and screwing stuff up.”
Rao: Operations will persist but require software engineering skills
“I still think there's an element of operations around these workloads though, right? It's just the skill set and the type of people who are doing it are different. It's not your Classic DBA sysadmin. It's going to be someone more of an engineering skill set.”
Rao: Developers instrument code when held responsible for production pages
“The developer does have an incentive to instrument his or her own code, because if something goes wrong, they're the ones that are going to get paged.”
Biilmann: WordPress is a bad idea, and web architecture will shift massively
“28% of all websites are still built with WordPress, and everybody kind of knows it's a bad idea, but it's even still slowly growing, and I think we're about to see a pretty massive sea change where the architecture of that will shift, and that I think will aff…”
Leibert: Mainframes will remain core enterprise infrastructure for 20 to 30 years
“So I think we're not going to see a rip and replace. I think we're going to see more and more systems built around the old systems. And for some of the core infrastructure, I think even in 20 or 30 years, we'll still have mainframes.”