Memgraph logo
Back to blog
Real-Time Visualization With React and D3.js

Real-Time Visualization With React and D3.js

By Katarina Supe
14 min readJanuary 4, 2022


This blog post will teach you how to create a React app and WebSocket that connects to the Flask server and visualize streaming data in real-time using D3.js. I decided to write it as a part of my learning path, and I hope to help anyone struggling with the same problems while trying to implement something similar. I decided to tackle the frontend implementation by visualizing Twitter users who retweeted something with the hashtag #christmas. Each community of users is presented with a different color which allowed me to notice the important communities in the Twitter network.

The frontend service is a part of a web application that you can find in the GitHub repository. Besides that, the repository also holds a visualization that discovers the most Christmassy person on Twitter using the dynamic PageRank algorithm.

Prerequisites and app architecture

If you are using Windows, you need to install Windows Subsystem for Linux (WSL) and then Docker Desktop. On the other hand, if you are a Linux user, just install Docker and Docker Compose.

The app is dockerized and it consists of five services:

  1. stream: A Python script collects new retweets with the hashtag #christmas and sends them to a Kafka cluster.
  2. kafka: A Kafka cluster consisting of one topic named retweets.
  3. memgraph-mage: The graph analytics platform where we store the incoming Twitter data from Kafka and perform dynamic PageRank and dynamic community detection on all Twitter users.
  4. backend-app: A Flask server that sends all the data we query from memgraph-mage to the frontend-app. It also consumes the Kafka stream and sends it to the frontend-app.
  5. frontend-app: A React app that visualizes the Twitter network using the D3.js library.


Project structure

You can see the whole project structure in the GitHub repository. The blog post focuses on the frontend service and explains how the visualization was created.

|   docker-compose.yml
|       Dockerfile
|   +---server
|   +---tests
|   |   .dockerignore
|   |   Dockerfile
|   |   package.json
|   |   package-lock.json
|   +---node_modules
|   +---public
|   +---src
|   |   Dockerfile
|   |   requirements.txt
|   +---procedures
|   +---transformations
|   |   Dockerfile
|   |
|   |
|   |   requirements.txt
|   +---data

The frontend folder was created using the create-react-app npm package. If you are starting from scratch and want to create a React app follow these steps:

  1. Place yourself in the root folder of your project.
  2. Run npm install -g create-react-app (if you don't want to install the latest version, you can specify the version of the create-react-app, for example, create-react-app@5.0.0).
  3. Next, run npm init react-app frontend --use-npm, which will initialize the react-app package in the frontend folder.
  4. In the end, place yourself in the frontend folder by running cd frontend and start the app with npm start.

Even a simpler way of creating a React app is by using npx - a package runner tool that comes with npm 5.2+. Then you just have to run:

npx create-react-app frontend
cd frontend
npm start

Socket.IO library

I have used since I had issues with the latest version. I am going to explain the process on the CommunityDetection component, since it's very similar to the PageRank component. If you are running the frontend application locally, and not using the provided dockerized application, make sure to install the library by running:

npm install

Don't forget that Node.js is a prerequisite for using npm.

First, I imported the socket I'm using on the client side. Backend is implemented with Flask.

import io from ""

After that, I initialized the socket.

 const socket = io("http://localhost:5000/", { transports: ["websocket"] })

I set the socket to listen to the server running at http://localhost:5000/. Then I established the connection to the server with the websocket. When the connection is established, the socket emits the consumer signal. This signal is also emitted on the server side, whenever a new message is sent. This configuration allows the socket to receive all messages related to the consumer signal.

socket.on("connect", () => {
    console.log("Connected to socket ",

socket.on("connect_error", (err) => {
    // try reconnecting

socket.on("disconnect", () => {
    console.log("Disconnected from socket.")

socket.on("consumer", (msg) => {
    console.log('Received a message from the WebSocket service: ',;

React.Component lifecycle


Image by Wojciech Maj from React Lifecycle Methods diagram

You may ask yourself where to place all this code within a React component. First, I initialized the socket in the App component that is the parent component of PageRank and CommunityDetection components. After that, I placed the socket events in componentDidMount() lifecycle method of the child components. This part of the React.Component lifecyle is invoked once, immediately after a component is mounted. If you need to load data from a remote endpoint, this is a good place to instantiate the network request. This method is also a good place to set up any subscriptions. That's why I have decided to place all socket events there. On each consumer emit, the state of the component will be updated and that will trigger an extra rendering which will happen before the browser updates the screen, so the user won't see the intermediate state. Before I set up the socket, at the beginning of the componentDidMount(), I made a simple HTTP request that will trigger the backend to start producing the needed data.

async firstRequest() {
    let response = await fetch("http://localhost:5000/health")

    if (!response.ok){
        throw new Error(`HTTP error! status: ${response.status}`);

After that, I initialized everything that was necessary for drawing using D3.js in the initializeGraph() method. By setting a new state of nodes and links with setState() on each consumer emit, componentDidUpdate() lifecycle method will be called. I am updating the graph by drawing new incoming nodes and links in that method. This lifecycle method is not called for the initial render, and that's why I initialized everything in the initializeGraph() method.

At the end, when the component unmounts, the componentWillUnmount() lifecycle method is called, and the client disconnects from the server.

componentWillUnmount() {

If you want to learn more about React.Component lifecycle methods, check out the React official docs.

Visualizing with D3.js

I wanted to draw the graph on svg using D3.js within the class component. You can do that by creating a reference in the component constructor that will be attached to the svg via the ref attribute. In constructor createRef() method is used.

constructor(props) {
    this.myReference = React.createRef();
    this.state = {
        nodes: [],
        links: []
    this.socket = this.props.socket

Then, in the component's render() method I added the ref attribute with value this.myReference to the svg.

render() {
    return (<div className="CommunityDetectionDiv">
        <h1>Community Detection</h1>
        <svg className="CommunityDetectionSvg" ref={this.myReference}
                height: 700,
                width: 1000,
                marginRight: "0px",
                marginLeft: "0px",
                background: "white"

Now, by selecting the current attribute of the reference, it's easy to get the svg on which the graph is drawn.

var svg =;

If you want to know how to use D3.js within function component, check out one of my previous blog posts - Twitch Streaming Graph Analysis - Part 2.

In the updateGraph() method I drew the nodes and relationships using D3.js, where nodes are colored depending on the community they belong to. The community information is being received through each node's cluster property.

// Remove old nodes

// Give attributes to all nodes that enter -> new ones + merge - update the existing DOM elements
node =, (d) =>;
node = node
    .attr("r", function (d) {
        return 7;
    .attr('fill', function (d) {
        let cluster = d.cluster
        let key = cluster.toString()
        if (!(key in clusterColors)) {
            clusterColors[key] = "#" + Math.floor(Math.random() * 16777215).toString(16)
        return clusterColors[key]
    .on("mouseover", function (d) {
        tooltip.text(d.srcElement["__data__"]["username"])"visibility", "visible")
    .on("mousemove", function (event, d) { return"top", (event.y - 10) + "px").style("left", (event.x + 10) + "px"); })
    .on("mouseout", function (event, d) { return"visibility", "hidden"); })

First, the old nodes are being removed, and the node value is set to the new nodes' data. With the enter() method, attributes of the incoming nodes are set. With merge() method the existing DOM elements are updated. The color of the node is being updated depending on the cluster it belongs to. I have previously created a map of colors called clusterColors. When a new cluster appears, a new key-value pair is created in the map, where the key is the cluster number and the value is a randomly generated color. If the cluster of the node already exists, then the color of the node will be the value of that cluster key in the clusterColors map. I added the links between the nodes similarly. All that's left to do is to create the simulation on new nodes and links.

// Set up simulation on new nodes and links
try {
} catch (err) {
    console.log('err', err);

Simulation has been initialized in the initializeGraph() method:

// set up simulation
simulation = d3
    .force('link', forceLink)
            .radius(function (d) {
                return 20;
    .force("center", d3.forceCenter(width / 2, height / 2))

simulation.on("tick", () => {
    node.attr("cx", (d) => d.x).attr("cy", (d) => d.y);
        .attr('x1', (d) => d.source.x)
        .attr('y1', (d) => d.source.y)
        .attr('x2', (d) =>
        .attr('y2', (d) =>;

I've created the force between the nodes and links, where each link has an unique id which we created by adding the attribute id .attr('id', (d) => + '-' + to each link. That id is created from the ids of the nodes the certain link is connecting. Collide force is there so that the nodes are not overlapping, considering the size of their radius. Here we have set the radius to size 20, which is larger than 7 - the radius of the nodes. There is also a center force forcing the nodes and links to appear at the middle of the svg.

And how this looks? Check out the GIF below for the preview, and if you want to start the app all by yourself, follow the instructions at the README in the repository.

The PageRank visualization code is similar. The notable difference is in the radius of each node and the color of the nodes.

 node = node
    .merge(node) //returns a brand new selection that contains both enter and update selection
    .attr("r", function (d) {
        return d.rank * 700;
    .attr('fill', 'url(#gradient)')
    .on("mouseover", function (d) {
        tooltip.text(d.srcElement["__data__"]["username"])"visibility", "visible")
    .on("mousemove", function (event, d) { return"top", (event.y - 15) + "px").style("left", (event.x + 15) + "px"); })
    .on("mouseout", function (event, d) { return"visibility", "hidden"); })

You can see that the attribute r is proportional to rank (calculated PageRank of each node). Also, the fill attribute is determined by the gradient created in the defineGradient() method.


There is still a lot left to learn regarding the React, D3.js and WebSocket, but creating this demo application gave me a pretty good insight into the real-time visualization. It was fun playing with it, and I'm looking forward to learning more in the future. Also, I would like to emphasize that Reddit network explorer application, developed by my colleagues Ivan, David and Antonio, helped me a lot. There, you can find real-time visualization with frontend in Angular. For any feedback or questions ping me or Memgraph team at our Discord server.

Join us on Discord!
Find other developers performing graph analytics in real time with Memgraph.
© 2024 Memgraph Ltd. All rights reserved.