https://resgate.io/ Recent content on resgate.io Hugo en-us Wed, 03 Jul 2024 00:00:00 +0000 https://resgate.io/docs/specification/res-service-protocol/ Wed, 03 Jul 2024 00:00:00 +0000 https://resgate.io/docs/specification/res-service-protocol/ Introduction This document uses the definition of resource, model, collection, value, messaging system, service, client, and gateway as described in the RES Protocol specification. The RES-Service protocol is used in communication between the services and the gateways. Requests Services listens to requests published by the gateways and services over the messaging system. A request consists of a subject (also called topic) and a payload. Request subject A request subject is a string identifying the type of request, which resource it is made for, and in case of call and auth requests, which method is called. https://resgate.io/docs/specification/res-protocol/ Mon, 25 Nov 2019 00:00:00 +0000 https://resgate.io/docs/specification/res-protocol/ Introduction RES (REsource Subscription) is a protocol for creating scalable client-server Push APIs consisting of resources served from stateless services connected by a messaging system. Clients subscribe to resources, and call upon their methods, through an API agnostic gateway acting as a bridge between the services and clients. It is designed for creating modular cloud based applications where new services and functionality can be added without causing disruption to a running production environment. https://resgate.io/blog/dotnet-part-2-realtime-updates/ Wed, 20 Nov 2019 00:00:00 +0000 https://resgate.io/blog/dotnet-part-2-realtime-updates/ How to create a next generation API with .NET using Resgate: Part 2 - Updating data in real time. https://resgate.io/blog/dotnet-part-1-hello-world/ Wed, 23 Oct 2019 00:00:00 +0000 https://resgate.io/blog/dotnet-part-1-hello-world/ How to create a next generation API with .NET using Resgate: Part 1 - Writing a Hello World service. https://resgate.io/blog/the-event/ Tue, 11 Jun 2019 00:00:00 +0000 https://resgate.io/blog/the-event/ How you can write a backend services that can update the database, the cache, and all clients’ state, with a single event message. A practical example written in Go, using Resgate. https://resgate.io/blog/introducing-resgate/ Mon, 20 May 2019 00:00:00 +0000 https://resgate.io/blog/introducing-resgate/ A basic introduction to Resgate, and how it can be used to build REST and real-time APIs where all clients are reliably synchronized. https://resgate.io/docs/writing-services/07access-control/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/07access-control/ Resgate and the RES protocol allows full access control on all resources and their methods. Whenever a client wants to get a resource, or call a method, Resgate will first verify that the client is authorized to do so. Earlier in Chapter 3 - Serving Resources we saw how we could grant full access to all resources for a service. Now, let’s take a closer look at how to use access control. https://resgate.io/docs/writing-services/02basic-concepts/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/02basic-concepts/ Resources Resgate and the RES protocol is built around a concept of resources1, similar to the JSON data sent over REST APIs. There are two types of resources: Models Collections Models A model2 is unordered key/value data represented by a JSON object, and may look like this: { "id": 42, "name": "Jane Doe", "isAdmin": true } There are no restrictions on the property names (keys), but the values3 should be JSON primitives: https://resgate.io/docs/writing-services/05collection-events/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/05collection-events/ Just like with the model change events, services are required to send events whenever a value has been added or removed from a collection. Add event An add event1 is, as the name suggests, an event sent whenever a value is added to a collection. The subject has the following pattern: event.<resource>.add Where resource is the resource ID of the collection. The event message is a JSON object with the following properties: https://resgate.io/docs/get-started/configuration/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/get-started/configuration/ Command-line Usage Resgate can be started with optional flags. Command line options will override configuration file settings. resgate [options] Server options Option Description Default value -n, –nats <url> NATS Server URL nats://127.0.0.1:4222 -i, –addr <host> Bind to HOST address 0.0.0.0 -p, –port <port> HTTP port for client connections 8080 -w, –wspath <path> WebSocket path for clients / -a, –apipath <path> Web resource path for clients /api/ -r, –reqtimeout <seconds> Timeout duration for NATS requests 3000 -u, –headauth <method> Resource method for header authentication -t, –wsheadauth <method> Resource method for WebSocket header authentication -m, –metricsport <port> HTTP port for OpenMetrics connections 0 (disabled) –apiencoding <type> Encoding for web resources: json, jsonflat json –putmethod <methodName> Call method name mapped to HTTP PUT requests –deletemethod <methodName> Call method name mapped to HTTP DELETE requests –patchmethod <methodName> Call method name mapped to HTTP PATCH requests –wscompression Enable WebSocket per message compression –resetthrottle <limit> Limit on parallel requests sent on a system reset 0 (no limit) –referencethrottle <limit> Limit on parallel requests sent following references 0 (no limit) -c, –config <file> Configuration file in JSON format Security options Option Description Default value –tls Enable TLS for HTTP false –tlscert <file> HTTP server certificate file –tlskey <file> Private key for HTTP server certificate –creds <file> NATS User Credentials file –natscert <file> NATS Client certificate file –natskey <file> NATS Client certificate key file –natsrootca <file> NATS Root CA file(s) –alloworigin <origin> Allowed origin(s): *, or <scheme>://<hostname>[:<port>] * Logging options Option Description -D, –debug Enable debugging output -V, –trace Enable trace logging -DV Debug and trace Common options Option Description -h, –help Show usage message -v, –version Show version Configuration file The configuration file is a simple JSON file. https://resgate.io/docs/writing-services/10custom-events/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/10custom-events/ In some cases you might want to send events that are not about changing the state of a resource. It can be a notification that a new message has arrived, or that it is time to take a break. Whatever it is, you can do that with custom events. Custom events A custom event1 is like sending any other event. It has the following subject pattern: event.<resource>.<name> Where resource is the resource ID on which the event is sent, and name is your alphanumeric (no dots! https://resgate.io/docs/writing-services/01hello-world/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/01hello-world/ Note This guide describes the RES Protocol using raw JSON calls to NATS with NodeJS examples. For language specific service libraries, such as for .NET (dotnetcore) and Go (golang), visit those projects. A Hello World service written for Resgate, using NodeJS, could look like this: const nats = require('nats').connect('nats://localhost:4222'); nats.subscribe('get.example.model', (req, reply) => { nats.publish(reply, JSON.stringify({ result: { model: { message: "Hello, World!" }}})); }); nats.subscribe('access.example.model', (req, reply) => { nats. https://resgate.io/docs/get-started/installation/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/get-started/installation/ Install via Docker If you install Docker, it is easy to run both NATS server and Resgate as containers: docker network create res docker run -d --name nats -p 4222:4222 --net res nats docker run --name resgate -p 8080:8080 --net res resgateio/resgate --nats nats://nats:4222 Both images are small, less than 10 MB each. Install release binary Get the binary-zip file matching your architecture, either from the download page, or from the GitHub releases page. https://resgate.io/docs/get-started/introduction/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/get-started/introduction/ What is Resgate? Resgate is an open-source Realtime API Gateway. It is a simple server that lets you create REST, real time, and RPC APIs, where all your clients are synchronized seamlessly. Video capture from the Book Collection Example. Try out the Live demo version yourself. How does it work? Resgate handles all API requests from your clients, instead of directly exposing your micro-services (represented by NodeJS and Go1 below). Clients will connect to Resgate, using either HTTP or WebSocket, to make requests. https://resgate.io/docs/writing-services/06methods/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/06methods/ Each resource may have methods that can be called remotely through a call request1. It is in many ways similar to a HTTP POST request. Let’s have a look at it. Call requests To listen for call requests, the service subscribes to a subject with the following pattern: call.<resource>.<method> Where resource is the resource ID and method is the alphanumeric (no dots!) name you’ve given to the method. In code, listening to calls to method mymethod on resource example. https://resgate.io/docs/writing-services/04model-events/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/04model-events/ In order for Resgate to keep data synchronized across all clients, services are required to send a model change event1 whenever a model is updated. Note All events for a resource must be sent from the same service. This is needed for Resgate to be sure it applies each event in the right order. Change event When sending a change event, the subject of the message will have the following pattern: https://resgate.io/docs/writing-services/08nested-resources/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/08nested-resources/ In most cases we need to be able to create more complex data structures than flat objects and arrays. Let’s say we want a list of items, such as this: [ { "id": 1, "item": "foo" }, { "id": 2, "item": "bar" }, { "id": 3, "item": "baz" } ] Let’s take a look at how to build it. Resource references With Resgate and the RES protocol, the services only serves resources separately, linking them together with resource references1. https://resgate.io/docs/writing-services/09recovery/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/09recovery/ Resgate and the RES protocol has built in ways of ensuring that data is synchronized, as well as ways to recover from lost connections and server crashes. Whenever a microservice suspects that the resources stored in Resgate’s cache may no longer be up-to-date, the microservice must send a signal to Resgate, so that measures can be taken to resynchronize. This should be done in cases such as when: microservice is disconnected and reconnects to NATS microservice restarts from a crash resources are modified without the microservice being able to send proper events to describe the mutations The way to signal this is through a system reset event. https://resgate.io/docs/specification/res-client-protocol/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/specification/res-client-protocol/ Introduction This document uses the definition of resource, model, collection, value, service, client, and gateway as described in the RES Protocol specification. The RES-Client protocol is used in communication between the client and the gateway. Subscriptions A core concept in the RES-Client protocol is the subscriptions. A client may subscribe to resources by making subscribe requests with the unique resource ID, or by getting a resource response on a call request or auth request. https://resgate.io/docs/writing-services/03serving-resources/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/03serving-resources/ The Hello World example showed how to serve a simple model. Let’s learn how it works. Get requests A get request1 from Resgate is similar to a HTTP GET request. It differs that it is sent over NATS instead of HTTP, and that the response must be a JSON object with a certain structure. To listen for get requests, the service must subscribe to a subject with the pattern: get.<resource> https://resgate.io/docs/writing-services/11setting-http-headers/ Sun, 21 Oct 2018 00:00:00 +0000 https://resgate.io/docs/writing-services/11setting-http-headers/ When a new HTTP or WebSocket connection is made, you might want to set the HTTP status or HTTP headers, such as Set‑Cookie, in the response to the client. This can be done by including meta objects in the response to auth, access or call requests. Let’s learn how to do it! HTTP and WebSocket connection The payload for an auth request1, call request2, or access request3 may contain a parameter, isHttp, that can be set to true. https://resgate.io/books/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/books/ https://resgate.io/docs/advanced-topics/client-sessions/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/advanced-topics/client-sessions/ In Chapter 7 - Access control in the Writing services guide, we learn how to set a client’s access token. This token will be stored by Resgate for as long as the client’s WebSocket connection remains. If the connection is lost, even for a second, Resgate will discard the token, forcing the client to reauthenticate itself when it reconnects. While this is positive from a security perspective, it is rather inconvenient. https://resgate.io/docs/advanced-topics/connection-resources/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/advanced-topics/connection-resources/ In some cases you might want the client to get connection specific information, most commonly information on the user which the connection is logged in as. Since the connection’s access token is not available to the client, we need some other way to send the data to the client. In the Client Session example, we can see how this is done using connection resources. Let’s have a closer look at how it works! https://resgate.io/download/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/download/ Linux 64-bit Download (2.70 MB) Microsoft Windows 64-bit Download (2.76 MB) Apple macOS 64-bit Download (2.75 MB) Stable versions File name OS Arch Size resgate-v1.8.0-darwin-amd64.zip macOS x64 2.75 MB resgate-v1.8.0-darwin-arm64.zip macOS ARM64 2.59 MB resgate-v1.8.0-linux-386.zip Linux x86 2.53 MB resgate-v1.8.0-linux-amd64.zip Linux x64 2.70 MB resgate-v1.8.0-linux-arm6.zip Linux ARMv6 2.51 MB resgate-v1.8.0-linux-arm7.zip Linux ARMv7 2.51 MB resgate-v1.8.0-linux-arm64.zip Linux ARM64 2.48 MB resgate-v1.8.0-windows-386.zip Windows x86 2.63 MB resgate-v1.8.0-windows-amd64.zip Windows x64 2.76 MB Tip Resgate can also be easily installed via Docker. https://resgate.io/docs/get-started/examples/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/get-started/examples/ Note In order to run the examples, you must have installed NATS Server and Resgate, listening on their default ports. All examples are complete with both service and client. NodeJS The resgate repository contains examples written for NodeJS. These examples use the nats client directly, without the use of any extra library. That makes them perfect to use in combination with the Writing Services guide. Running an example Run the following commands, but change hello-world to the example you wish to try: https://resgate.io/docs/advanced-topics/extend-timeout/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/advanced-topics/extend-timeout/ Resgate will send requests blindly onto NATS, waiting for a microservice to respond. If no response is received within a set amount of time (defaults to 3 seconds), Resgate will discard the request and send a system.timeout1 error to the client. In some cases, a microservice may knowingly take longer time to process a request. Fortunately, the RES protocol provides a way for the microservice to extend the timeout for individual requests. https://resgate.io/docs/get-started/faq/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/get-started/faq/ Is Resgate free to use? Yes, completely. Resgate is released under the permissive MIT license. What does RES stand for? RES as in Resgate stands for REsource Subscription. What language is Resgate written in? Go. The same goes for NATS Server, which is used in conjunction with Resgate. Can Resgate turn my existing REST protocol into a realtime API? Not just like that. You may use a service, such as rest2res, to turn your legacy API into a live API, accessible through Resgate. https://resgate.io/demo/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/demo/ Hello World Demo Fetching resources served with Resgate can either be done through HTTP(s): https://api.resgate.io/api/example/model Or by using ResClient, a javascript library that gets both data and updates through WebSocket: <pre id="output"></pre> const ResClient = resclient.default; // Creating a client instance. let client = new ResClient('wss://api.resgate.io'); // Get the resource from the service. // Try changing 'example.model' to 'example.users'. client.get('example.model').then(data => { let json = JSON.stringify(data, null, 2); output.textContent = json; }). https://resgate.io/docs/advanced-topics/query-resources/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/advanced-topics/query-resources/ One of the more complex issues when it comes to real time updates, are queries. Let’s say we have an inventory database which we wish to make searchable. We want to be able to filter the search by fields such as category, stock status, and created date. In case the search result might be large, we also wish to limit how many items we return, letting the user browse through pagination. https://resgate.io/docs/writing-clients/resclient/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/writing-clients/resclient/ All resources and methods can be accessed using ordinary HTTP requests. But to get realtime updates from Resgate, you should be using ResClient instead. What is ResClient? ResClient1 is a javascript client library that uses WebSocket and the RES-client protocol2 to communicate with Resgate. It can be installed with npm: npm install resclient --save Or with yarn: yarn add resclient Or by downloading it from a CDN: <script src="https://cdn.jsdelivr.net/npm/resclient@latest/dist/resclient.min.js"></script> Basic usage Connect ResClient need no prior knowledge about the API it connects to. https://resgate.io/viewer/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/viewer/ https://resgate.io/docs/get-started/resources/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/get-started/resources/ Tip Do you miss a service library or utility? Be the first one to write it, and have it added here! Service libraries It is not required to use a service library for building services, as the protocol is simple enough. But sure, it helps. Name Description Language Developer go-res Go package for writing RES services Go Samuel Jirénius ResgateIO.Service .NET Core library for writing RES services C# Samuel Jirénius Client libraries To connect to Resgate via WebSocket, a RES client library is needed. https://resgate.io/docs/about/roadmap/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/about/roadmap/ The roadmap represents coming features lined up for the future of Resgate and its ecosystem. Its purpose is to give insight into the major features that will be implemented in the near future. This is a living document where priorities may be re-evaluated based on the valuable input from the Resgate community. Please contact us through the forum with any questions, comments, or requests. 2020 - Q3 .NET service library database interface 1 RES protocol resource reset event 2 RES protocol stream resource type 3 2020 - Q4 Resgate syslog support 4 Resgate monitoring feature 5 . https://resgate.io/docs/advanced-topics/scaling/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/advanced-topics/scaling/ Resgate and the RES protocol has been developed with scaling in mind. There are many dimensions in which a system might grow, and different types of growth might require different solutions. In this document, we will be looking at different ways infrastructures using Resgate may be built to scale. Client connections There are limits on how many concurrent connections a single server can handle. As the user base grows, the capacity to accommodate the increasing number of connections must grow with it. https://resgate.io/support/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/support/ Resgate is an MIT licensed open source project and completely free to use, together with all its surrounding libraries. Has Resgate helped you in your work? Does your company use it as a part of their product? Do you wish for it to stay healthy and actively developed? Now you can sponsor it! :) Note All donations goes directly to support the continued development of Resgate. One time donations One-time donation can be made via Paypal: https://resgate.io/docs/advanced-topics/token-update/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/advanced-topics/token-update/ The token that is issued in a connection token event1 helps services to determine what resources the connection should have access to. But sometimes a user’s access may change as they are granted new, or denied previous, permissions. Or maybe the user is kicked out, and should have their access revoked all together. In order to update or revoke tokens, the RES protocol provides a way to identify tokens, and request for them to be updated. https://resgate.io/docs/writing-clients/using-modapp/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/writing-clients/using-modapp/ We will base this guide on Book Collection example, which shows an editable list of books, with their titles and authors. To try out the example, visit the link and follow the instructions. Before we go into the code on how to use ResClient together with Modapp components, we need to have a look at what Modapp is. What is Modapp? Modapp1 is a framework developed by Samuel Jirénius, creator of Resgate, and is described as: https://resgate.io/docs/writing-clients/using-react/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/writing-clients/using-react/ We will base this guide on Book Collection example - React, which shows an editable list of books, with their titles and authors. To try out the example, visit the link and follow the instructions. Before we go into the code on how to use ResClient together with React, we need to have a look at how ResClient handles state. State ResClient stores and manages the state in model and collection objects, which represents the state as it is on the backend. https://resgate.io/docs/writing-clients/using-vuejs/ Mon, 01 Jan 0001 00:00:00 +0000 https://resgate.io/docs/writing-clients/using-vuejs/ We will base this guide on Book Collection example - Vue.js, which shows an editable list of books, with their titles and authors. To try out the example, visit the link and follow the instructions. Before we go into the code on how to use ResClient together with Vue.js, we need to have a look at how ResClient handles state. State ResClient stores and manages the state in model and collection objects, which represents the state as it is on the backend.