Ng-News 26/04: Micro Frontends at Google

Doug Parker of the Angular team discussed Micro Frontends at Google, focusing on isolation, Protocol Buffers, and scenarios where the pattern should be avoided. The same episode also touches on the ongoing TypeScript-to-Go migration and recent advancements in the Angular DevTools Signal Graph.

Micro Frontends at Google

Doug Parker appeared as a guest on the Angular Meetup Graz, which took on a podcast-like format this time. As a member of the Angular team with a focus on the CLI, Parker discussed the topic of Micro Frontends at Google.

To set the stage: Google operates a monorepo, where all applications reside in a single repository. That doesn’t necessarily lead to a Micro Frontend architecture. There has been previous coverage, including on ng-news, of Google’s Cloud Console approach, which relied on a massive micro frontend system built around an iFrame strategy that has since been retired.

The updated strategy now involves running Micro Frontends with full independence. To prevent any version conflicts from shared dependencies, Google takes a cautious route—they avoid sharing entirely. This results in a highly self-contained setup. For shared logic, they leverage Protocol Buffers, but even then, a service isn’t directly shared among micro frontends; it functions more like a messaging backbone instead. Additionally, they must be able to integrate portions of different frameworks together in one environment.

Parker’s perspective frames Micro Frontends as defining a clear contract between separate applications. Ultimately, there’s an interface that must be satisfied, and the underlying infrastructure manages the glue work for integration.

There’s currently no intention to release the solution as open source once it matures.

As for when to adopt Micro Frontends: anytime an alternative strategy can solve the core issue, it’s worth exploring that first. For instance, if reducing build times is the main driver, there are other pathways to tackle that outside of a micro frontend setup.

When there are strict UX guidelines in place, implementing a micro-frontend style could prove challenging.

Additionally, Micro Frontends are frequently adopted as a way to minimize cross-team collaboration. The question that should come first is whether that’s actually the intended outcome, or if fostering more communication between teams—the opposite direction—is what’s truly needed.

Status Update on Go Rewrite of TypeScript

A year ago, the TypeScript team shared plans to rebuild the compiler using Go, aiming for performance gains that could hit roughly tenfold, an order of magnitude leap.

Such a massive project eats up significant time and, naturally, all of the team's focus. Push-based provided a recent update on where things stand. Progress is steady, and the forthcoming TypeScript 6.0 release is set to be the final one built with TypeScript itself.

Meanwhile, the Angular team is already aligning their own codebase in preparation for v6.

LinkedIn post by push-based

Angular PR #66578

Miscellaneous

A visualization of the Signal Graph is offered by the Angular DevTools. With the newest release, this tool was enhanced, providing a clearer picture of the resource, which essentially constitutes a collection of Signals that are interconnected.

New Conferences

Wrapping things up, registration is now live for Ng-India, the biggest Angular event in India.

FOREM_LTAG_END:{"tag":"open_graph","url":"https://www.ng-ind.com","options":"https://www.ng-ind.com"}

Once more, if you’re running a conference, don’t hesitate to get in touch with us—we’d love to feature it here.