Keeping Sane with React Micro-Frontends in Production by Applying Observability

Rate this content
Bookmark

Teams are getting bigger by applying micro-frontends using React, but complexity tracking production issues can become extremely confusing when no clear responsibilities are met. That’s when observability for teams and applications on a scale becomes even more important, in order to be able to identify potential issues in production, separate the concerns and the responsibilities among them. In this presentation we’ll learn how we can achieve this.

7 min
17 Jun, 2022

AI Generated Video Summary

Observability for microfrontends involves defining clear separation of concerns between teams and tracking errors in production with structured events. By using React boundaries, failures can be isolated and high observability can be achieved. Logging errors with metadata allows for querying specific error types and receiving notifications. Automating the process with Terraform simplifies observability for microfrontends.

1. Introduction to Observability for Microfrontends

Short description:

Hello, everyone. My name is Konstantinos. I'm a software engineer working for DAZN, where we're building a live and on-demand streaming service for sport events. We're going to explore observability for microfrontends, which have become a paradigm for microservices. While they help separate frontend monoliths into smaller applications, there can be challenges in defining clear separation of concerns between teams. We'll also discuss logging around time errors and the limitations of error decoders and source maps.

[♪ Music ♪ and applause ♪ Hello, everyone. Can you hear me all right? Are you excited to be in the React Summit today with me? Yeah! Woo! So, hello, everyone. My name is Konstantinos. I'm coming from London. I'm a software engineer, where I'm actually working there for DAZN. And we're actually building a live and on-demand streaming service for sport events. We plan to become the home of all sports, and this is going to be in a while. But for the time being, we're going to see what about observability for microfrontends.

So how many of you have already used or plan to use microfrontends? Okay. And how many of you, have you been building already in production using microfrontends? Okay. That's much better than expected. That's great. So microfrontends have actually become like a paradigm for microservices. They come here in order to separate the frontend monoliths and split it to separate smaller applications. That's why we end up having end-to-end teams responsible for a specific business domain. And they're able to have a specific mission. That's how we have frontend, backend, and database teams focused on a specific mission of a business domain. But the teams are, as you can see here, they are really pretty well-defined until when if we zoom in, in some of these cases, they're not actually that clear separation of concerns. So, for example, we might have a team A responsible for the header and footer, but we might have a team B responsible for the account details. We need to find out ways to separate these kind of modules and better ways to observe them in production.

I don't know about you, so in design, we're actually using New Relic for logging around time errors. You might be using, like, a similar tool. So I'm going to New Relic dashboard and I usually see this kind of error. This is, of course, because React in production minifies the code base and avoids sending down the full error. How many of you have seen this kind of error before in production? Are you logging around time errors? How many of you are logging around time errors in production? Okay. So what we're doing, we're going to visit the React docs and we're going to see this error decoder. The information that we get from there is really valuable. But it doesn't help us identify the issue down to the root of it. So what we're going to do here, source maps won't help because they're not aware of the internal modules. And what we need to do is, we need to take a step back and check the principles from micro front ends.

2. Observability for Micro Frontends

Short description:

Micro frontends require clear boundaries to isolate failures and achieve high observability. By using React boundaries, we can wrap container and module components to create scope around errors. The first step to observability is tracking errors in production with structured events. This allows us to log errors and define metadata such as module name and version. With this data, we can query specific error types and receive notifications via email or integration with support systems like PagerDuty. Automating this process with Terraform makes it even easier.

What I want to focus on is on micro front ends that need to isolate the failure and be high observable systems. It's easier to observe a single system, but it's a bit difficult to observe a system split into multiple modules.

So here, for example, we have my account, which is the container application. And we are also having menu, which is a specific module. Footer, which is another module. And profile, which is another one. So how we're going to solve this problem. We're going to need clear boundaries. And the way that we're going to do that is by using React boundaries. This is like a solution for quite some time now. So we're going to wrap our container components and the module components using the boundaries. And that way, we're actually able to create some scope around these errors.

Another thing, and the very first step to observability, is to be able to track the error in production with structured events. What this means is that by using the error boundaries, we're able to track on the New Relic system or any other of your tools that you're using. We're able to log the error and we're also able to define some metadata about these errors. And this is about, for example, module name, module version, or whatever else we want to create some context about. This is what we're going to do for the module error boundary as well.

And finally, now that we're tracking all this data on New Relic, we're able to start querying this data from the New Relic tables. This is how New Relic query language would work. And we are able to query down to very, very specific error types and define it in the component source based on the context that we define from the metadata from the error tracking before. And we're also able to get notified from them in the simplest form with an email, or otherwise integrating with a online or on-call support system like PagerDuty. So you can actually do this, actually, also with Terraform, you can automate all the stuff and it's much, much easier.

And yeah, that's pretty much all for now. A really short introduction on the journey to observability for micro frontends. Thank you very much. If you have any questions, I'll be around after this talk. I'm on Discord and Twitter with this handle. Thank you very much.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

React Advanced Conference 2022React Advanced Conference 2022
25 min
A Guide to React Rendering Behavior
React is a library for "rendering" UI from components, but many users find themselves confused about how React rendering actually works. What do terms like "rendering", "reconciliation", "Fibers", and "committing" actually mean? When do renders happen? How does Context affect rendering, and how do libraries like Redux cause updates? In this talk, we'll clear up the confusion and provide a solid foundation for understanding when, why, and how React renders. We'll look at: - What "rendering" actually is - How React queues renders and the standard rendering behavior - How keys and component types are used in rendering - Techniques for optimizing render performance - How context usage affects rendering behavior| - How external libraries tie into React rendering
React Summit Remote Edition 2021React Summit Remote Edition 2021
33 min
Building Better Websites with Remix
Remix is a new web framework from the creators of React Router that helps you build better, faster websites through a solid understanding of web fundamentals. Remix takes care of the heavy lifting like server rendering, code splitting, prefetching, and navigation and leaves you with the fun part: building something awesome!
Remix Conf Europe 2022Remix Conf Europe 2022
23 min
Scaling Up with Remix and Micro Frontends
Do you have a large product built by many teams? Are you struggling to release often? Did your frontend turn into a massive unmaintainable monolith? If, like me, you’ve answered yes to any of those questions, this talk is for you! I’ll show you exactly how you can build a micro frontend architecture with Remix to solve those challenges.
React Advanced Conference 2022React Advanced Conference 2022
30 min
Using useEffect Effectively
Can useEffect affect your codebase negatively? From fetching data to fighting with imperative APIs, side effects are one of the biggest sources of frustration in web app development. And let’s be honest, putting everything in useEffect hooks doesn’t help much. In this talk, we'll demystify the useEffect hook and get a better understanding of when (and when not) to use it, as well as discover how declarative effects can make effect management more maintainable in even the most complex React apps.
React Summit 2022React Summit 2022
20 min
Routing in React 18 and Beyond
Concurrent React and Server Components are changing the way we think about routing, rendering, and fetching in web applications. Next.js recently shared part of its vision to help developers adopt these new React features and take advantage of the benefits they unlock.In this talk, we’ll explore the past, present and future of routing in front-end applications and discuss how new features in React and Next.js can help us architect more performant and feature-rich applications.

Workshops on related topic

React Summit 2023React Summit 2023
170 min
React Performance Debugging Masterclass
Featured WorkshopFree
Ivan’s first attempts at performance debugging were chaotic. He would see a slow interaction, try a random optimization, see that it didn't help, and keep trying other optimizations until he found the right one (or gave up).
Back then, Ivan didn’t know how to use performance devtools well. He would do a recording in Chrome DevTools or React Profiler, poke around it, try clicking random things, and then close it in frustration a few minutes later. Now, Ivan knows exactly where and what to look for. And in this workshop, Ivan will teach you that too.
Here’s how this is going to work. We’ll take a slow app → debug it (using tools like Chrome DevTools, React Profiler, and why-did-you-render) → pinpoint the bottleneck → and then repeat, several times more. We won’t talk about the solutions (in 90% of the cases, it’s just the ol’ regular useMemo() or memo()). But we’ll talk about everything that comes before – and learn how to analyze any React performance problem, step by step.
(Note: This workshop is best suited for engineers who are already familiar with how useMemo() and memo() work – but want to get better at using the performance tools around React. Also, we’ll be covering interaction performance, not load speed, so you won’t hear a word about Lighthouse 🤐)
React Advanced Conference 2021React Advanced Conference 2021
132 min
Concurrent Rendering Adventures in React 18
Featured WorkshopFree
With the release of React 18 we finally get the long awaited concurrent rendering. But how is that going to affect your application? What are the benefits of concurrent rendering in React? What do you need to do to switch to concurrent rendering when you upgrade to React 18? And what if you don’t want or can’t use concurrent rendering yet?

There are some behavior changes you need to be aware of! In this workshop we will cover all of those subjects and more.

Join me with your laptop in this interactive workshop. You will see how easy it is to switch to concurrent rendering in your React application. You will learn all about concurrent rendering, SuspenseList, the startTransition API and more.
React Summit Remote Edition 2021React Summit Remote Edition 2021
177 min
React Hooks Tips Only the Pros Know
Featured Workshop
The addition of the hooks API to React was quite a major change. Before hooks most components had to be class based. Now, with hooks, these are often much simpler functional components. Hooks can be really simple to use. Almost deceptively simple. Because there are still plenty of ways you can mess up with hooks. And it often turns out there are many ways where you can improve your components a better understanding of how each React hook can be used.You will learn all about the pros and cons of the various hooks. You will learn when to use useState() versus useReducer(). We will look at using useContext() efficiently. You will see when to use useLayoutEffect() and when useEffect() is better.
React Advanced Conference 2021React Advanced Conference 2021
174 min
React, TypeScript, and TDD
Featured WorkshopFree
ReactJS is wildly popular and thus wildly supported. TypeScript is increasingly popular, and thus increasingly supported.

The two together? Not as much. Given that they both change quickly, it's hard to find accurate learning materials.

React+TypeScript, with JetBrains IDEs? That three-part combination is the topic of this series. We'll show a little about a lot. Meaning, the key steps to getting productive, in the IDE, for React projects using TypeScript. Along the way we'll show test-driven development and emphasize tips-and-tricks in the IDE.
React Advanced Conference 2021React Advanced Conference 2021
145 min
Web3 Workshop - Building Your First Dapp
Featured WorkshopFree
In this workshop, you'll learn how to build your first full stack dapp on the Ethereum blockchain, reading and writing data to the network, and connecting a front end application to the contract you've deployed. By the end of the workshop, you'll understand how to set up a full stack development environment, run a local node, and interact with any smart contract using React, HardHat, and Ethers.js.
React Summit 2023React Summit 2023
151 min
Designing Effective Tests With React Testing Library
Featured Workshop
React Testing Library is a great framework for React component tests because there are a lot of questions it answers for you, so you don’t need to worry about those questions. But that doesn’t mean testing is easy. There are still a lot of questions you have to figure out for yourself: How many component tests should you write vs end-to-end tests or lower-level unit tests? How can you test a certain line of code that is tricky to test? And what in the world are you supposed to do about that persistent act() warning?
In this three-hour workshop we’ll introduce React Testing Library along with a mental model for how to think about designing your component tests. This mental model will help you see how to test each bit of logic, whether or not to mock dependencies, and will help improve the design of your components. You’ll walk away with the tools, techniques, and principles you need to implement low-cost, high-value component tests.
Table of contents- The different kinds of React application tests, and where component tests fit in- A mental model for thinking about the inputs and outputs of the components you test- Options for selecting DOM elements to verify and interact with them- The value of mocks and why they shouldn’t be avoided- The challenges with asynchrony in RTL tests and how to handle them
Prerequisites- Familiarity with building applications with React- Basic experience writing automated tests with Jest or another unit testing framework- You do not need any experience with React Testing Library- Machine setup: Node LTS, Yarn