

Adrian Cockcroft on Microservices, Terraservices and Serverless Computing
10 snips Apr 18, 2016
Adrian Cockcroft, a technology advisor at Battery Ventures and former Netflix architect, dives into the evolving landscape of microservices. He discusses how programming languages influence tooling choices and warns against pitfalls like excessive timeout settings. Cockcroft highlights the importance of starting with a monolith before shifting to distributed architecture and introduces the trend of serverless computing. Additionally, he explores the impact of open source on IT and shares insights on AWS's role in shaping the tech community.
AI Snips
Chapters
Transcript
Episode notes
Language and Microservices
- Microservices architectures often correlate with a team's primary programming language.
- For instance, Java developers lean towards Netflix's Java-centric tools and Spring Cloud.
Timeout Strategies
- Optimize timeout values in a microservice architecture for increased stability.
- Use progressively smaller timeouts deeper in the system to prevent cascading failures.
Monolith First
- Start with a monolith and transition to microservices when team size or scaling demands it.
- Microservices offer better separation of concerns but introduce complexity early on.