reactive-interaction-gateway

by Accenture

Create low-latency, interactive user experiences for stateless microservices.

430 Stars 51 Forks Last release: 5 months ago (2.4.0) Apache License 2.0 1.3K Commits 13 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Logo

RIG - Reactive Interaction Gateway

Create low-latency, interactive user experiences for stateless microservices.

Build Status DockerHub Slack

Take a look at the documentation and get in touch with us on Slack!

About

How RIG makes asynchronous backend<->frontend communication easier:

  • RIG takes care of client connection state so you don't have to.
  • RIG picks up back-end events and forwards them to clients based on subscriptions.
  • RIG forwards client requests to backend services either synchronously or asynchronously.

Built on open standards, RIG is very easy to integrate – and easy to replace – which means low-cost, low-risk adoption. Unlike other solutions, RIG does not leak into your application – no libraries or SDKs required.

Features:

  • Easy to use and scalable by design:
    • Supports tens of thousands stable connections per node even on low-end machines.
    • Easy to add additional nodes.
    • Built on the battle-proven Erlang/OTP distribution model.
    • Only uses in-memory data structures - no external dependencies to configure or scale.
  • Connect using standard protocols:
    • Firewall friendly and future proof using Server-Sent Events (SSE)
    • HTML5 standard.
    • Regular HTTP requests, so no issues with proxy servers or firewalls.
    • Connection multiplexing with HTTP/2 out of the box.
    • SSE implementation (browser) keeps track of connection drops and restores the connection automatically.
    • Polyfills available for older browsers.
    • WebSocket connections are supported, too.
    • HTTP long polling for situations where SSE and WS are not supported.
  • Publish events from various sources:
    • Kafka
    • NATS
    • Amazon Kinesis
    • or publish via HTTP
  • Convert a HTTP request to a message for asynchronous processing:
    • produce to Kafka topic, optionally wait for the result on another Kafka topic
    • produce to a NATS topic, optionally using NATS request-response to wait for the result
    • produce to Amazon Kinesis
  • Uses the CNCF CloudEvents specification.
  • Flexible event subscription model based on event types.
  • Use existing services for authentication and authorization of users and subscriptions.
  • JWT signature verification for APIs as a simple authentication check.
  • Session blacklist with immediate session invalidation.

For more details take a look at the documentation.

Getting Started

Take a look at the getting-started tutorial.

API Documentation

RIG exposes its API documentation on its API endpoint under /swagger-ui. For integration into an existing swagger UI, the related JSON document can either be retrieved at runtime or found on disk after compiling RIG at least once.

Metrics

RIG exposes Metrics in Prometheus format on its API endpoint under /metrics

Contribute

  • Use issues for everything.
  • For a small change, just send a PR.
  • For bigger changes open an issue for discussion before sending a PR.
  • PR should have:
    • Test case
    • Documentation (e.g., moduledoc, developer's guide, operator's guide)
    • Changelog entry
  • You can also contribute by:
    • Reporting issues
    • Suggesting new features or enhancements
    • Improve/fix documentation

See the developer's guide and CONTRIBUTING.md for details.

License

The Reactive Interaction Gateway (patent: granted) is licensed under the Apache License 2.0 - see LICENSE for details.

Acknowledgments

The Reactive Interaction Gateway is sponsored and maintained by Accenture.

Kudos to these awesome projects:

  • Elixir
  • Erlang/OTP
  • Phoenix Framework
  • Brod
  • Distillery

.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.