1. Vonage Learn
  2. Blog
  3. 2021
  4. 05
  5. 05
  6. Introducing Rxzu an Engine for Intuitive Graphs 1
Introducing RxZu, an Engine for Intuitive Graphs

< Engineering />

Introducing RxZu, an Engine for Intuitive Graphs

In the beginning, all was linear.

We had in our hands an interface that allowed users to design conversations, entirely based on graphs. This was part of the Vonage AI studio, where anyone can create it's own intelligent virtual assistant. The kicker? It was entirely based on forms.

But AI was the future, and forms, which our clients found unusable, most definitely were not.

The Search for a Graphs Library

We realized we needed a visual approach to simplify the already complex world of conversation design. Something clever, snazzy, intuitive. And for that, we needed a graphs library that would satisfy some requirements:

  1. Angular support
  2. Lightweight
  3. Extendable and customizable
  4. Extensive support and community

And what do you know? Our search yielded zero results. The libraries we found were extremely heavy, and included outdated dependencies such as Lodash and Backbone. The options we looked into were not open-sourced and lacked a community. The implementations we found were outdated, lacking Typings, unfitting for Angular environment, and introduced endless complexity for the simplest use case.

Enter RxZu

So we created RxZu, named for Reactive Extensions (RxJS) and Zu, the Japanese word for illustration.

RxZu is a diagrams engine system, built on top of RxJS, that takes the graphic visualization to the next level in terms of performance, optimization, and customizability.

RxZu is composed of multiple parts: the core engine, which is in charge of handling the synchronization between models, and the rendering engine that is based on the framework utilizing the core engine.

Some of the leading guidelines in the project are minimal. They are about clean code and the ability for customizations and extendibility of the engine entities. These entities are made up of:

  • Nodes: the main building block of any graph; the visual representation of data convergence
  • Ports: the starting points for the links
  • Links: a line between two ports, representing connectivity and continuity
  • Labels: the name or description of an entity
  • Custom: the ability to create a custom entity, for example, a sticky note

Alt Text

Let's See the Code

Note that RxZu currently only implements Angular as a rendering engine, which means all code examples are for Angular

We'll begin by creating a new Angular application that will display a graph with a drag and drop interface to add more nodes:

ng new rxzu-angular
# wait for angular installation to finish
cd rxzu-angular

Install @rxzu/angular:

npm i @rxzu/angular

Run the application:

ng s

Let's enable production mode for RxZu in main.ts

import { enableProdMode } from '@angular/core';
import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';

import { AppModule } from './app/app.module';
import { environment } from './environments/environment';
import { enableDiagramProdMode } from '@rxzu/angular';

if (environment.production) {

  .catch((err) => console.error(err));

Add to app.module.ts RxZu module along with all the default component:

import { CommonModule } from '@angular/common';
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import {
} from '@rxzu/angular';

import { AppComponent } from './app.component';

const DEFAULTS: ComponentProviderOptions[] = [
    type: 'node',
    component: DefaultNodeComponent,
    type: 'port',
    component: DefaultPortComponent,
    type: 'link',
    component: DefaultLinkComponent,
    type: 'label',
    component: DefaultLabelComponent,

  declarations: [AppComponent],
  imports: [BrowserModule, CommonModule, RxZuModule.withComponents(DEFAULTS)],
  providers: [],
  bootstrap: [AppComponent],
export class AppModule {}

RxZu module withComponents method accepts an array of components and their type. This way the library can resolve and paint the different components when added to the diagram model, which we'll create below.

Now let's create a cool grid as our background, the draggable nodes, and our action bar container:


.demo-diagram {
  display: flex;
  height: 100%;
  min-height: 100vh;
  background-color: #3c3c3c;
  background-image: linear-gradient(
      transparent 24%,
      rgba(255, 255, 255, 0.05) 25%,
      rgba(255, 255, 255, 0.05) 26%,
      transparent 27%,
      transparent 74%,
      rgba(255, 255, 255, 0.05) 75%,
      rgba(255, 255, 255, 0.05) 76%,
      transparent 77%,
      transparent 24%,
      rgba(255, 255, 255, 0.05) 25%,
      rgba(255, 255, 255, 0.05) 26%,
      transparent 27%,
      transparent 74%,
      rgba(255, 255, 255, 0.05) 75%,
      rgba(255, 255, 255, 0.05) 76%,
      transparent 77%,
  background-size: 50px 50px;

.node-drag {
  display: block;
  cursor: grab;
  background-color: white;
  border-radius: 30px;
  padding: 5px 15px;

.action-bar {
  position: fixed;
  width: 100%;
  height: 40px;
  z-index: 2000;
  background-color: rgba(255, 255, 255, 0.4);
  display: flex;
  align-items: center;

  * {
    margin: 0 10px;

Then, our html template with the actions bar and the diagram itself:


<div class="action-bar">
    *ngFor="let node of nodesLibrary"
    [ngStyle]="{ 'background-color': node.color }"
    {{ node.name }}


And for the last piece in the puzzle, create some nodes and ports, and link them up. Then render it all.


import { AfterViewInit, Component, ViewChild } from '@angular/core';
import {
} from '@rxzu/angular';

  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss'],
export class AppComponent implements AfterViewInit {
  diagramModel: DiagramModel;
  nodesLibrary = [
    { color: '#AFF8D8', name: 'default' },
    { color: '#FFB5E8', name: 'default' },
    { color: '#85E3FF', name: 'default' },
  @ViewChild(RxZuDiagramComponent, { static: true })
  diagram?: RxZuDiagramComponent;

  constructor() {
    this.diagramModel = new DiagramModel();

  ngAfterViewInit() {

  createNode(type: string) {
    const nodeData = this.nodesLibrary.find((nodeLib) => nodeLib.name === type);
    if (nodeData) {
      const node = new NodeModel();
      const port = new PortModel();

      return node;

    return null;

   * On drag start, assign the desired properties to the dataTransfer
  onBlockDrag(e: DragEvent) {
    const type = (e.target as HTMLElement).getAttribute('data-type');
    if (e.dataTransfer && type) {
      e.dataTransfer.setData('type', type);

   * on block dropped, create new intent with the empty data of the selected block type
  onBlockDropped(e: DragEvent): void | undefined {
    if (e.dataTransfer) {
      const nodeType = e.dataTransfer.getData('type');
      const node = this.createNode(nodeType);
      const canvasManager = this.diagram?.diagramEngine.getCanvasManager();
      if (canvasManager) {
        const droppedPoint = canvasManager.getZoomAwareRelativePoint(e);
        const width = node?.getWidth() ?? 1;
        const height = node?.getHeight() ?? 1;
        const coords = {
          x: droppedPoint.x - width / 2,
          y: droppedPoint.y - height / 2,

        if (node) {


Some things to note:

The diagramModel is the most important part. It holds the entire diagram model, and gives us the ability to add or remove elements from the diagram.


Some entities are children of others, such as ports (which are child nodes). They can be added by directly attaching them to their parent.

const port = new PortModel();

In the next tutorial you'll learn how to create customized nodes that utilize any extra information they receive.

Until then, you can find many more examples in our Storybook, and the source code in our GitHub repo.

Where do we go from here?

The most important task on our roadmap is about building better performance in the core. And also:

  • Adding support for React, Vue, and more...
  • Smarter links with obstacle awareness
  • Rendering only elements in the view port to support gigantic diagrams (thousands of entities)
Comments currently disabled.