Ever wondered how big engineering orgs actually scale UI development across dozens of teams — without breaking the product or each other’s deployments?
In the latest episode of Señors @ Scale, I sat down with Erik Grijzen, Principal Software Engineer at New Relic, to talk about how they built one of the earliest micro-frontend architectures — before the term even existed — and how observability became a key part of scaling both systems and teams.
We covered:
How New Relic unified 20+ SPAs into a single extensible platform
Why observability isn’t just about logs and metrics anymore — it’s a business reliability layer
How to organize frontend teams by domain, not feature
The hidden challenges of runtime composition, dependency duplication, and iframes at scale …
Ever wondered how big engineering orgs actually scale UI development across dozens of teams — without breaking the product or each other’s deployments?
In the latest episode of Señors @ Scale, I sat down with Erik Grijzen, Principal Software Engineer at New Relic, to talk about how they built one of the earliest micro-frontend architectures — before the term even existed — and how observability became a key part of scaling both systems and teams.
We covered:
How New Relic unified 20+ SPAs into a single extensible platform
Why observability isn’t just about logs and metrics anymore — it’s a business reliability layer
How to organize frontend teams by domain, not feature
The hidden challenges of runtime composition, dependency duplication, and iframes at scale
Why writing RFCs and POCs before coding improves architecture quality
How senior engineers lead through influence instead of authority
Curious to hear from others working in large orgs — how are you handling observability or micro-frontends at scale? What’s worked (or gone horribly wrong)?