Skip to content
A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.
Branch: master
Clone or download
Latest commit 8196f0c May 14, 2019

Resgate logo

Realtime API Gateway
Synchronize Your Clients

License Report Card Build Status Coverage

Visit for guides, live demos, and resources.

Resgate is a Go project implementing a realtime API gateway for the RES protocol with NATS server as messaging system.

It is a simple server that lets you create REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.

Used for building new REST APIs with real-time functionality, or when creating single page applications using reactive frameworks such as React, Vue.js, or Modapp.

Book Collection Animation
Screen capture from the Book Collection Example. Try out the Live demo version yourself.

How it works

Resgate handles all API requests from your clients, instead of directly exposing your micro-services (represented by Node.js and Java below). Clients will connect to Resgate, using either HTTP or WebSocket, to make requests. These requests are sent to the micro-services over NATS server, and Resgate will keep track on which resource each client has requested.

Whenever there is a change to the data, the responsible micro-service sends an event. Resgate will use this event to both update its own cache, and make sure each subscribing client is kept up-to-date.

RES network diagram



The recommended way to install Resgate and NATS Server is to download one of the pre-built binaries:


If you wish to build your own binaries, first make sure you have:

Install and run NATS server and Resgate:

go get
go get


While Resgate may be used with any language, the examples are written in Javascript for Node.js.

Example Description
Hello World Simple service serving a static message.
Edit Text Text field that can be edited by multiple clients concurrently.
Book Collection List of book titles & authors that can be edited by many.
JWT Authentication Showing how JWT tokens can be used for authentication.
Password Authentication Showing authentication with user and password credentials.
Client Session Creating client sessions that survive reloads and reconnects.


All examples are complete with both service and client.

Protocol Specification

For more in depth information on the protocol:


resgate [options]
Option Description
-n, --nats <url> NATS Server URL
-i, --addr <host> Bind to HOST address
-p, --port <port> Use port for clients
-w, --wspath <path> Path to WebSocket
-a, --apipath <path> Path to web resources
-r, --reqtimeout <milliseconds> Timeout duration for NATS requests
-u, --headauth <method> Resource method for header authentication
--tls Enable TLS
--tlscert <file> Server certificate file
--tlskey <file> Private key for server certificate
--apiencoding <type> Encoding for web resources: json, jsonflat
-c, --config <file> Configuration file
-h, --help Show usage message


Configuration is a JSON encoded file. If no config file is found at the given path, a new file will be created with default values as follows.


	// URL to the NATS server
	"natsUrl": "nats://",
	// Timeout in milliseconds for NATS requests
	"requestTimeout": 3000,
	// Bind to HOST IPv4 or IPv6 address
	// Empty string ("") means all IPv4 and IPv6 addresses.
	// Invalid or missing IP address defaults to
	"addr": "",
	// Port for the http server to listen on.
	// If the port value is missing or 0, standard http(s) port is used.
	"port": 8080,
	// Path for accessing the RES API WebSocket
	"wsPath": "/",
	// Path for accessing web resources
	"apiPath": "/api",
	// Encoding for web resources.
	// Available encodings are:
	// * json - JSON encoding with resource reference meta data
	// * jsonflat - JSON encoding without resource reference meta data
	"apiEncoding": "json",
	// Header authentication resource method for web resources.
	// Prior to accessing the resource, this resource method will be
	// called, allowing an auth service to set a token using
	// information such as the request headers.
	// Missing value or null will disable header authentication.
	// Eg. "authService.headerLogin"
	"headerAuth": null,
	// Flag telling if tls encryption is enabled
	"tls": false,
	// Certificate file path for tls encryption
	"tlsCert": "",
	// Key file path for tls encryption
	"tlsKey": ""

Running Resgate

By design, Resgate will exit if it fails to connect to the NATS server, or if it loses the connection. This is to allow clients to try to reconnect to another Resgate instance and resume from there, and to give Resgate a fresh new start if something went wrong.

A simple bash script can keep it running:

until ./resgate; do
    echo "Resgate exited with code $?.  Restarting.." >&2
    sleep 2


Visit for documentation and resources.

It has guides on installation, configuration, writing services, scaling, queries, and other useful things. It also contains guides for ResClient when working with frameworks such as React, Vue.js, and Modapp.

Support Resgate

Resgate is an MIT-licensed open source project where development is made possible through community support.

If you'd like help out, please consider:


Any feedback on the protocol and its implementation is highly appreciated!

If you find any issues with the protocol or the gateway, feel free to report them.

If you have created a service library, a client library, or some other tool or utility, please contact me to have it added to the list of resources.

You can’t perform that action at this time.