PANEL DISCUSSION + Live Q&A
Panel: Microservices - Are they still worth it?
Lots of us have moved away from monolithic architectures and embraced microservices but do we see the bang for the buck? Is the impact they are having a positive one or negative one? Is there an alternative middle ground? Have we learnt how to wrangle all the operational complexity inherent with large distributed systems?
Our panel have moved from the monolith to microservices and in some cases back again. They have strong opinions on monorepos, on operating distributed systems and on the best way to structure your organisation to make a success of this architecture.
Speaker
Luke Blaney
Principal Engineer Operations and Reliability Programme @FT
Luke has worked for the Financial Times since 2012 as a Developer and then Platform Architect. Now a Principal Engineer on their Reliability Engineering team, tasked with improving operational resilience and reducing duplication of tech effort across the company.
Read moreSpeaker
Alexandra Noonan
Software Engineer @segment
Alexandra Noonan is a backend engineer who spends most of her time building reliable, scalable systems. She's been at working at Segment for the past 4 years, focused distributed systems and scaling the core data pipeline.
Read moreFind Alexandra Noonan at:
Speaker
Manuel Pais
IT Organizational Consultant and co-author of Team Topologies
Manuel Pais is an independent IT organizational consultant and trainer, focused on team interactions, delivery practices, and accelerating flow. Manuel is co-author of the book "Team Topologies: Organizing Business and Technology Teams for Fast Flow" (IT Revolution Press, 2019). He...
Read moreFind Manuel Pais at:
Speaker
Matt Heath
Senior Staff Engineer @Monzo
Matt Heath is an engineer at Monzo, a new kind of digital bank, where he works on Monzo's microservice platform and payment services. Having previously worked as the Technical Lead of Hailo's global platform, Matt has an unhealthy obsession for scaling fault tolerant, high volume,...
Read moreFind Matt Heath at:
Location
Fleming, 3rd flr.
Track
Next Generation Microservices: Building Distributed Systems the Right Way
Topics
MicroservicesSlides
Slides are not available
Share
From the same track
Monolith Decomposition Patterns
Patterns to help you incrementally migrate from a monolith to microservices. Big Bang rebuilds of systems are so 20th century. With our users expecting new functionality to be shipped more frequently than ever before, we no longer have the luxury of a complete system rebuild. In fact, a big bang...
Sam Newman
Microservice, Cloud, CI/CD Expert
Beyond the Distributed Monolith: Rearchitecting the Big Data Platform
The BBC’s Audience Platform Data team collects, transforms and delivers billions of events each day from audience interactions with mobile apps and web sites such as BBC News, BBC Sport, iPlayer and Sounds.Last year we migrated to a new analytics provider and we took this as an...
Blanca Garcia-Gil
Principal Engineer on data platform @BBC
Monitoring All the Things: Keeping Track of a Mixed Estate
Monitoring all of a team’s systems can be tricky when you have a microservice architecture. But what happens when you have many teams, each building systems using totally different technology stacks? Add in decades of legacy systems and a sprinkling of third-party tools and you’ve got...
Luke Blaney
Principal Engineer Operations and Reliability Programme @FT
Why Distributed Systems Are Hard
Every company that has adopted microservices architecture operates a complex distributed system. It's basically a full-time endeavor to keep up with the ever-changing landscape of technologies and tools to build, maintain, and scale these towering production systems, but the fundamentals of...
Denise Yu
Senior Software Engineer @GitHub
To Microservices and Back Again
From the start, Segment embraced a microservice architecture in our control plane and data plane. Microservices have many benefits: improved modularity, reduced testing burden, better functional composition, environmental isolation, and development team autonomy, etc. but when implemented wrong...
Alexandra Noonan
Software Engineer @segment