Choosing a realtime collaboration library

Choosing a realtime collaboration library

Last updated May 2018

Here at Convergence Labs, we’re excited to witness the increased adoption of realtime collaboration in software across the entire industry. This has given rise to a whole suite of technology solutions to help developers get their needs met, no matter the size and scale of their applications.

Of course, Convergence is one of those technology solutions, but this post is not about selling you on Convergence. We think it can provide a massive amount of value to a large set of people, but it’s certainly not the best fit for everyone. So let’s dive into your project requirements so you’re able to make good technology decisions.

High-level Considerations

There are a ton of factors to consider when planning a software project. Some, like the open-source vs commercial question, are common, but many are specific to realtime collaborative software. We’ll mainly focus on the latter.

Do you actually need realtime collaboration?

The standard definition of realtime collaboration is the ability for multiple people to be able to work on the same piece of data at the same time. This could be a rich text document, a presentation, or maybe just some text describing a task. However, most applications don’t actually have this requirement. For example, an application that merely pulls and aggregates data in real-time (think a real-time dashboard) doesn’t fit our definition, because there’s no data being written. Even a lot of apps that are heavily write-intensive don’t fit this definition, if they have been designed to allow only a single user at a time or implement “locks” or other measures to avoid conflicts.

Conversely, there are collaborative applications that are not real-time. Git, for example, is the industry standard for collaborating on source code, but it is by no means a real-time solution. Two team members can’t really be working on the same piece of code at once because they don’t have the context to see what the other is doing at that moment.

This distinction is critical when evaluating third-party libraries. If you spend six months architecting your backend on a certain platform, but neglect considering that small co-editing feature of your app, you will be very disappointed when that feature’s implementation begins and your chosen platform doesn’t support it. You’ll have to pull in something else, or try and roll your own, which is exceptionally difficult.

Unique constraints for realtime collaboration

So you’ve determined that true real-time collaboration is a requirement for your application. Congratulations – you’re ahead of the curve already! RTC is still an emerging space, so let’s address a few unique constraints that you may not have had to consider before:

  • Data models. The shape of your data heavily affects the difficulty of managing state between multiple users. For example, one of the most common types of data, rich text, has yet to see a RTC implementation that supports a wide variety of off-the-shelf rich text editors. A lot of libraries have focused on supporting data that can be represented by JSON, but make sure you read the documentation closely to make sure it will support the data constructs your app will require.
  • Networking infrastructure. By definition, RTC requires communication between multiple remote machines. This doesn’t have to follow a client-server pattern, but from the very beginning you’ll have to worry about things like data security, guaranteed uptime, and scalability.

Supported platforms

This article will be primarily focused on web-compatible solutions, for a variety of reasons:

  • We know it well and it has by far the most options
  • It is the most ubiquitous application delivery platform on the planet
  • Everybody has a web browser in their pocket and can thus be a potential user

Please contact us if you’re interested in hearing about other real-time collaboration solutions available for other platforms and programming languages.

Types of projects

What exactly are you building? Will it actually have users? How many? The bigger and longer-term the project, the more important the choice of underlying technology.

Trial/experimental

Engineers love playing around with new technology. To that end, the goal of these toy projects is intellectual curiosity. This is one reason why open source has been so successful: If something doesn’t work as it appears, you can read the source! Documentation missing? Read the source! You can see what you are getting, and probably learn a thing or two from the source.

For curiosity-driven projects, check out Automerge or Yjs for a CRDT or OT-based open source RTC solution, respectively. The underlying algorithms are quite interesting, and you can get a simple app up and running quickly.

Startup MVPs

Startups live and die by their speed of execution. Yet MVPs are typically developed on a shoestring budget. Technical founders need to be able to leverage existing technology, with a balance between off-the-shelf utility and speed of integration. Cost is another critical concern.

We’ve directly worked with two types of startups in this space: those with real-time collaboration as a core feature, and those treating it as an add-on differentiator.

RTC as a core product capability

If your product was originally designed with realtime collaboration at its core, you’ll have a more difficult decision as the stakes are high. Poor technology choices can massively delay shipping, limit long-term feature possibilities, or both. Here are some of the options:

  • Roll your own. Ten years ago, this would be the norm, but with more and more off-the-shelf proprietary and open-source API providers emerging and gaining market share, this is becoming an increasingly difficult decision. There could be a strong argument towards needing to gain deep domain knowledge in order to make long-term architecture decisions, and building your own system would force you and your team to gain this knowledge. That road is long, expensive and fraught with mistakes, but with the right combination of talent and perseverance it would be the right call.
  • Build on top of open source. This has become the default decision for many projects, and for good reason. It’s a tough call here, though: if RTC is a core feature requirement, the technology implementing it necessarily permeates all levels of your software stack: from the front-end all the way to your database. For this reason, switching RTC providers further down the road is likely to be cost-prohibitive.
  • Buy. In cases where a superlative UX or getting to market quickly are paramount, it’s hard to argue against using an off-the-shelf solution. If you find product/market fit, you may be able to afford to revisit the decision, but maybe not.

Regardless of your leanings, we’d recommend consulting with an expert in the space.

RTC as a differentiating feature

For a lot of companies, RTC support could be added to certain aspects of their products where users are most often working on the same data at the same time. It’s not a mission-critical feature but mainly a differentiator from competitor products.

Here are the common options for implementing these RTC features:

  • Roll your own. It’s hard to argue in favor of this decision in this case. Unless you’re a very large organization with deep pockets, rolling your own RTC will almost certainly be prohibitively expensive.
  • Build on top of open source. See the next section concerning commercial vs open source.
  • Buy. The cost to build RTC into your app with an off-the-shelf solution will be the lowest possible. You can keep more of your developer cycles working on your core product rather than researching the ins and outs of data synchronization algorithms.

If you do decide to buy or leverage open source, design your architecture such that a user’s experience is minimally impacted by the failure of your RTC technology. This means keeping the RTC data flow separate from the core application’s. If there is downtime or a disconnection, you can just display a warning message and switch over to the default single-user mode.

Commercial vs open source

While having access to the code is undeniably valuable, open-source solutions tend to run into the same common problems as projects mature and their requirements change. Any experienced software architect is already aware of these tradeoffs, but here they are:

  • The “Tip of the Iceberg” Effect: Home-grown, single-maintainer projects tend to put the vast majority of documentation on getting developers started, and that’s it. You can get a nice whiz-bang demo running with the simplest possible use case, but it doesn’t take long until you’re running into problems that weren’t anticipated by the original author(s). A few months later, and you’re as much of an expert on the codebase as the original author, and you’ve accidentally inherited a codebase that you now realize only addresses 20% of your project’s needs 1.
  • Scalability and Growth: Web-based software is getting increasingly complex, and many OSS solutions weren’t designed to accommodate the demands of modern web applications: Multiple integrated third-party and home-rolled systems, robust security, rapid scaling, etc. Especially in the RTC space, a lot of solutions have come out of academia and haven’t seen much exposure in real-world, commercial settings. Even with the recent renaissance of auto-scaling DevOps infrastructure, designing scalable software is still extremely difficult.
  • Lock-in effects: If you buy, who’s to say that company will still be around in two years? Committing a critical piece of your application infrastructure to a third party is not a decision to be taken lightly. Switching providers in the future will certainly be expensive, potentially prohibitively so. However, this would almost certainly be the case for open-source as well.
  • Support: Commercial products almost always come with built-in, dedicated support. Open source projects run the gamut as far as support is concerned: there may be a dedicated, active community around the project, or it may be completely lifeless. The bigger your project, the more important support is.

Solution RoundUp

We’ve attempted to categorize each library/framework to indicate their optimal use case.

Open source libraries

These libraries tend to focus entirely on the data synchronization piece of realtime collaboration. They are small and do the data sync well, but you are on your own for additional concerns like authentication, access control, and collaborative UX support.

Automerge

Automerge provides automatic syncing and merging for a small set of data types. Object, arrays, and strings are all supported. Doesn’t dictate the transport layer. Uses CRDTs under the hood.

Pros

  • Peer-to-peer, decentralized support with the MPL (Magic Persistence Layer) library
  • Change history
  • Offline support

Cons

  • No rich text support
  • No authentication or authorization support
  • Lack of integrity checking may lead to unchecked, corrupted edits
License Popularity
MIT 5172 stars

Yjs

Yjs is a framework for shared editing. It is structured to allow customization of storage and transports. It uses CRDTs behind the scenes and supports a fixed set of types out of the box.

Pros

  • Support for decentralized, peer-to-peer shared data editing
  • Fairly rich set of supported types: Maps/arrays, text, and rich text (Quill only)
  • Out of the box support for a variety of common UI libraries (Ace, Quill, CodeMirror, etc)
  • Offline support

Cons

  • Relatively untested2 in production settings
  • No support for collaborative cues
  • No authentication or authorization support
License Popularity
MIT 587 stars

Specialty solutions

These are categorized separately as they take a unique approach to the problem. The first two do DOM-level synchronization, while Flip was designed for complex use cases.

TogetherJS

TogetherJS was a Mozilla Labs project aiming to make it “surprisingly easy” to add realtime collaboration to a website. Essentially, it synchronizes DOM state between multiple browsers (See Webstrates below for some pitfalls of this approach). It is open source and provides a UI widget with text chat and rudimentary audio chat to get developers going quickly.

It has a few rather large users including JSFiddle and .NET Fiddle.

The original creator of TogetherJS, Mozilla Labs, is unfortunately no longer active, and the project is in need of a maintainer.

License Popularity
Mozilla Public License, Version 2.0 6k stars

Webstrates

Similar to TogetherJS, Webstrates does DOM-level synchronization. It also includes a general purpose messaging framework between connected clients. The actual data synchronization is performed behind the scenes by ShareDB.

DOM syncing is a fairly straightforward approach towards providing a feel of realtime collaboration. However, web developers have for a long time been aware of the drawbacks of basing their applications on the DOM rather than a domain-specific javascript model.

License Popularity
Apache 2.0 73 stars

Flip

The Flip framework was extracted from Ohm Studio, a richly featured digital audio workstation with realtime collaboration at its core. It is attacking the problem from a depth-first perspective, with heavy use of system invariants and a focus on guaranteed resolution for complex data types.

There curently isn’t a lot of public information about the framework.

License
Proprietary

General-purpose solutions

These frameworks provide the majority of what most applications would need out of the box. Convergence is the most full-featured, while ShareDB has been around for a long time and is thus fairly well-proven.

ShareDB (formerly ShareJS)

ShareDB is an open-source realtime backend. It uses OT to synchronize data. [This repository] contains the types supported by ShareDB: JSON, plain text, and rich-text (scoped to work with Quill).

Pros

  • Used in several production systems
  • Extensible via middleware with community-provided modules for authorization, etc.
  • Flexible storage options
  • Offline support

Cons

  • Supporting other data types requires writing transforms from scratch, which is extremely time-intensive and error-prone
  • No support for collaborative cues
License Popularity
MIT 1.7k stars

SwellRT

SwellRT is an open source backend-as-a-service designed to ease building realtime collaborative applications. It is a fork of the now-defunct Apache Wave project, which was originally open-sourced when Google Wave shut down.

SwellRT is OT-based, and thus requires a master node to preserve a global order of operations. It claims to be decentralized but it has yet to be proven.

SwellRT is also the technology powering Jetpad, a realtime collaborative rich text editor. Unfortunately the UI appears to be tightly tied to the backend implementation.

Pros

  • Built-in user management and authentication
  • Included storage with MongoDB

Cons

License Popularity
Apache 2.0 125 stars

Convergence

We of course couldn’t write this article without mentioning our own horse! Convergence is the first and only all-in-one turnkey solution for adding realtime collaboration to web applications. After designing and implementing many realtime collaborative applications, Convergence was built to deliver the functionality that every RTC app needs.

Collaborative Cues

Where every library in this list only addresses the data synchronization problem, Convergence goes beyond, providing APIs for building collaboration awareness, presence, and chat. Any usable multi-user application will need some sort of collaborative cueing to help users avoid conflicts, and Convergence provides APIs for references and activities.

Pros and Cons

The primary advantage to Convergence is that it is a full-fledged backend-as-as-service, so you get storage, user management, and authentication/authorization a la Firebase. The primary disadvantage is that it is closed-source, though guaranteed support is included in most plans. Some folks don’t want to trust their backend to a for-profit company, and we respect that. That’s why this guide exists.

License
Proprietary

So far we’ve focused on general-purpose RTC solutions that can be both be easily plugged into an existing codebase and support a relatively wide variety of data. However, there are a few related projects out there that may fit some people’s needs:

Integrated RTC web components

There are a number of UI components out there that provide both the view layer and an integrated data synchronization backend. If you have a very specific use case (say, you just need a RTC rich text editor to drop into your app) one of these may fit the bill:

  • CKEditor 5 is an open source rich text editor that supports RTC out of the box. Still in alpha.
  • Firepad is an open source code and text editor that combines a RTC adaptor with Firebase for data storage and synchronization. Requires a Firebase account.

End-user applications

  • Etherpad is an end-user application (Mac and Windows) that is essentially a RTC document editor.
  • Codox Wave takes an interesting approach to end-user collaboration. It provides a browser extension to enhance some of the most popular web-based software such as WordPress, Gmail, Evernote, and Zendesk with RTC functionality.

Dead/retired projects

These projects had their time in the sun but have since been abandoned or cancelled.

Footnotes

  1. The pace of innovation in the software industry wouldn’t be what it is without open source, and we are hugely indebted to the OSS we use on a daily basis. There is merit to contributing to and growing an open source codebase, but the vast majority of open source development is still funded through for-profit software companies. We just want to remind people of what they may be getting into. 

  2. Get in touch if you’ve built something significant and we’ll update this!