『Observability at Scale with Erik Grijzen, Principal Software Engineer at New Relic』のカバーアート

Observability at Scale with Erik Grijzen, Principal Software Engineer at New Relic

Observability at Scale with Erik Grijzen, Principal Software Engineer at New Relic

無料で聴く

ポッドキャストの詳細を見る

このコンテンツについて

In this episode of Señors @ Scale, Erik Grijzen, Principal Software Engineer at New Relic, joins Dan to share his journey from web designer to principal architect and what it really takes to scale UI development across dozens of teams. Erik walks us through how New Relic built one of the first large-scale micro-frontend architectures before the term even existed, designing tooling that lets teams ship independently—from CLI bootstrapping to runtime composition. He explains how to manage hundreds of deploys a day without breaking the platform, and how observability keeps complex systems reliable when they inevitably fail.We dive deep into observability at scale—how metrics, logs, traces, and business data blend to show what’s happening inside distributed systems, and why visibility isn’t just for developers anymore but a business priority tied to uptime, revenue, and customer trust.Erik also shares what technical leadership looks like at New Relic: influencing without authority, scaling architecture through culture, and using processes like RFCs and change documents to make better decisions. He emphasizes writing before building, POCs before roadmaps, and the mindset shift from coding features to guiding direction.The episode closes with a thoughtful discussion on burnout, balance, and habits for longevity in engineering—from sports and shutdown rituals to books like A Philosophy of Software Design and 4,000 Weeks.Whether you’re an architect, staff engineer, or team lead scaling a complex frontend platform, this episode is packed with real lessons on architecture, observability, and leadership at scale.Chapters00:00 Introduction to Erik Grijzen and His Journey08:48 Building a Unified Platform at New Relic13:34 Challenges and Solutions in Micro-Frontend Development18:47 How Observability Works Behind the Scenes32:02 Organizing Teams Around Domains36:38 Testing in Micro Frontends43:38 Technical Leadership and Management49:38 Effective Processes for Teams54:05 Decompressing and Work-Life Balance---Follow & Subscribe:📸 Instagram: https://www.instagram.com/senorsatscale/📸 Instagram: https://www.instagram.com/neciudev🎙 Podcast URL: https://neciudan.dev/senors-at-scale📬 Newsletter: https://neciudan.dev/subscribe💼 LinkedIn: https://www.linkedin.com/in/neciudan💼 LinkedIn: https://www.linkedin.com/company/se%C3%B1ors-scale/---Additional Resources[https://newrelic.com/blog](https://newrelic.com/blog)[https://micro-frontends.org/](https://micro-frontends.org/)[https://web.stanford.edu/~ouster/cgi-bin/book.php](https://web.stanford.edu/~ouster/cgi-bin/book.php)[https://oliverburkeman.com/books/4000-weeks/](https://oliverburkeman.com/books/4000-weeks/)#microfrontends #observability #softwarearchitecture #newrelic #frontend #softwareengineering #leadership #teammanagement #engineeringculture #señorsatscaleDon’t forget to like, comment, and subscribe for more engineering stories from the front lines. How is your team scaling architecture and observability? Share below 👇

まだレビューはありません