For solo engineers, but not only.

Leveraging RxJS for Seamless Communication Between Components in Different Layouts in Next.js

August 7, 2023Lev Gelfenbuim9 min. read

In Next.js, a popular React framework for building web applications, one of the challenges developers often face is efficiently communicating between components residing in different layouts. While Next.js provides a well-organized structure for managing components within layouts, it doesn’t inherently offer a direct communication mechanism between them. In this blog post, we’ll explore how to address this issue using RxJS, a powerful library for reactive programming, to establish seamless communication between components from different layouts in Next.js.

Understanding RxJS

RxJS (Reactive Extensions for JavaScript) is a library for composing asynchronous and event-based programs using observable sequences. It enables the creation and manipulation of observables, which are sequences of data or events over time. Observables can be used to handle events, manage asynchronous operations, and streamline communication between different parts of your application.

In Angular, RxJS plays a crucial role in handling asynchronous operations, managing data streams, and facilitating communication between different parts of the application. It provides powerful tools such as observables, operators, and subjects that enable developers to work with reactive programming paradigms seamlessly.

Here are the key points to consider regarding RxJS:

  1. Observables: RxJS revolves around the concept of Observables, which are streams of data or events over time. Observables can represent a single value, multiple values, or even asynchronous data streams. They provide a powerful foundation for handling asynchronous operations and data manipulation.
  2. Operators: RxJS offers a rich set of operators that enable developers to transform, filter, combine, and manipulate data streams efficiently. These operators allow for the implementation of complex asynchronous workflows with concise and readable code.
  3. Reactive Programming: RxJS embraces reactive programming principles, where applications respond to changes and events as they occur, rather than waiting for explicit calls or updates. This approach leads to more responsive and interactive applications.
  4. Event Handling: RxJS provides a streamlined approach to handle various events, whether they are user interactions, API responses, or other asynchronous operations. Observables can be used to manage events and react accordingly, simplifying event-driven programming.
  5. Data Management: With RxJS, developers can easily manage data flows within their applications. It offers a standardized way to handle data from various sources and provides a unified mechanism for data transformation and synchronization.
  6. Error Handling: RxJS provides error handling mechanisms that allow developers to handle errors gracefully within observable streams. This ensures that errors are properly managed without causing application crashes.
  7. Backpressure and Memory Management: RxJS includes backpressure and memory management strategies to handle scenarios where the rate of data production exceeds the rate of data consumption. This helps prevent memory leaks and ensures optimal performance.
  8. Multicasting: RxJS supports multicasting, which allows multiple subscribers to share a single source of data. This is particularly useful when dealing with shared resources or when you want to optimize data processing.
  9. Testing: RxJS code is highly testable due to its functional and declarative nature. Testing observables and operators is straightforward, making it easier to create robust and reliable unit tests.
  10. Cross-Framework Compatibility: RxJS is not limited to a specific framework and can be used in various environments, including Angular, React, Vue.js, Node.js, and more. This makes it a versatile tool for handling reactive programming in different projects.

RxJS is just one of the many solutions available for handling asynchronous and event-based programming. Depending on the specific use case and project requirements, developers may consider alternative libraries and tools. Here are some examples of other solutions available:

  1. Redux and Redux-Observable: Redux is a predictable state management library commonly used with React applications. It helps manage the state of an application in a single, centralized store, making it easier to track changes and maintain a unidirectional data flow. Redux-Observable is an extension to Redux that leverages RxJS to handle asynchronous side effects and manage complex data flows. It allows developers to express side effects as observable streams, enabling seamless integration with Redux.
  2. React’s Context API and useContext Hook: React’s Context API provides a way to pass data through the component tree without having to pass props down manually at every level. It enables components to subscribe to changes in the context and react accordingly when the data changes. The useContext hook allows functional components to consume context values directly without using higher-order components or render props.
  3. EventEmitter: EventEmitter is a core module in Node.js that provides an implementation of the Observer pattern. It allows developers to create custom event emitters and listeners to facilitate communication between different parts of a Node.js application.
  4. Pub-Sub Libraries: There are various pub-sub libraries available, such as PubSubJS and nano-pubsub, which implement the Publish-Subscribe pattern. These libraries allow components or modules to publish messages (events) to specific channels, and other components can subscribe to those channels to receive the messages.
  5. MobX: MobX is another state management library that follows the reactive programming paradigm. It automatically tracks observable data and updates components that depend on it, making it a suitable choice for handling reactivity and data synchronization.

Consider a typical scenario in Next.js where you have two components, ComponentA and ComponentB, residing in separate layouts, say LayoutA and LayoutB. The goal is to enable ComponentA to communicate with ComponentB, even though they are in different layouts.

Setting Up the Project

Before diving into the implementation, ensure you have a Next.js project set up. If you haven’t done that, follow these steps:

  1. Install Next.js globally: npm install -g create-next-app
  2. Create a new Next.js project: npx create-next-app my-nextjs-app
  3. Navigate to the project directory: cd my-nextjs-app
Implementing Communication with RxJS

Step 1: Install RxJS in your project:

1npm install rxjs

Step 2: Create a custom event bus using RxJS in a new file, eventBus.js:

1import { Subject } from 'rxjs';
3const eventBus = new Subject();
5export default eventBus;

Step 3: In ComponentA, publish an event using the eventBus when a specific action occurs:

1import React from 'react';
2import eventBus from '../path/to/eventBus';
4const ComponentA = () => {
5  const handleClick = () => {
6{ type: 'ACTION_FROM_COMPONENT_A', data: 'Hello from Component A!' });
7  };
9  return (
10    <div>
11      <button onClick={handleClick}>Trigger Action</button>
12    </div>
13  );
16export default ComponentA;

Step 4: In ComponentB, subscribe to the eventBus and handle the event accordingly:

1import React, { useEffect, useState } from 'react';
2import eventBus from '../path/to/eventBus';
4const ComponentB = () => {
5  const [message, setMessage] = useState('');
7  useEffect(() => {
8    const subscription = eventBus.subscribe((event) => {
9      if (event.type === 'ACTION_FROM_COMPONENT_A') {
10        setMessage(;
11      }
12    });
14    return () => {
15      subscription.unsubscribe();
16    };
17  }, []);
19  return (
20    <div>
21      <p>Received message: {message}</p>
22    </div>
23  );
26export default ComponentB;

Step 5: Include ComponentA in LayoutA and ComponentB in LayoutB. Then, utilize the layouts in your system as needed.


By using RxJS as an event bus, we’ve successfully established communication between ComponentA and ComponentB, even though they reside in different layouts within our Next.js application. RxJS's reactive nature allows us to handle events seamlessly and makes our application more organized and maintainable.

Remember to handle memory management properly by unsubscribing from subscriptions when components are unmounted to prevent memory leaks. With this approach, you can extend communication across multiple components and layouts efficiently, providing a smooth and interactive user experience in your Next.js applications.

While RxJS is a powerful and widely-used solution for reactive programming and asynchronous data handling, developers have a range of other options available to address specific needs in their projects. Choosing the right solution depends on factors such as the project’s complexity, the framework being used, and the specific requirements for data synchronization and event handling. By exploring various libraries and tools, developers can find the best fit for their applications and deliver efficient and responsive user experiences.

Happy coding!

Article last update: February 10, 2024