awesome-repositories.com
Blog
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
deepstreamIO avatar

deepstreamIO/deepstream.io

0
View on GitHub↗
7,183 estrellas·384 forks·TypeScript·MIT·5 vistasdeepstreamio.github.io↗

Deepstream.io

deepstream.io is an open-source realtime server that synchronizes JSON records, events, and remote procedure calls across clients and backend services. It functions as a realtime data sync server, event pub/sub server, record database server, and RPC server, all within a single platform. The server authenticates and authorizes every message using multiple strategies including JWT, HTTP, and file-based credentials, with a declarative permission language controlling access to records, events, and RPCs at a granular level.

The platform distinguishes itself through its combination of realtime data synchronization, topic-based pub/sub messaging, and remote procedure call orchestration in one integrated system. It supports atomic multi-path updates on JSON records, cross-client data sync, and a listen pattern that notifies backend services when clients subscribe to topics. The server runs on a single-threaded horizontal scaling model, allowing multiple independent nodes to distribute load across cloud instances, and supports plugin-based storage architecture for connecting to external databases and caches.

Beyond its core capabilities, deepstream.io provides online user presence tracking, connected client queries, and RPC request load balancing across multiple registered providers. It offers command-line configuration overrides and supports YAML or JSON configuration files. The server can be registered as a system service on init.d or systemd systems, and supports running multiple server instances on one machine with separate configurations.

Features

  • General-Purpose Realtime Servers - Synchronizes JSON records, events, and remote procedure calls across clients and backend services in real time.
  • Cross-Client Synchronization - Keeps shared data records synchronized in real time across all connected clients.
  • Realtime Document Synchronization - Keeps JSON records synchronized across all connected clients and backend services in real time.
  • Realtime Synchronizations - Synchronizes editable JSON records across all connected clients with caching and storage.
  • Realtime Synchronizations - Propagates partial or full JSON changes instantly to keep all clients consistent.
  • Realtime Synchronization - Keeps JSON records and state synchronized across all connected clients and backend services in real time.
  • Realtime Document Database Servers - Persists and synchronizes JSON documents across connected clients with caching, storage, and atomic updates.
  • Nested Path Reads and Writes - Sets, gets, and subscribes to changes on full records or specific nested JSON paths.
  • Realtime List Synchronizations - Synchronizes data across all connected clients and backend services as changes occur in real time.
  • Realtime Client Connections - Ships a client library for authenticating browser-based connections to the realtime server.
  • Publish-Subscribe Messaging - Routes topic-based messages from any sender to all subscribers with automatic data serialization.
  • Realtime Messaging Providers - Delivers messages instantly between clients and servers without polling for live communication.
  • Pub-Sub Messaging - Routes topic-based messages from any sender to all subscribers with automatic serialization.
  • General-Purpose Pub/Sub Servers - Routes topic-based messages from any publisher to all subscribers with automatic serialization and delivery.
  • Remote Procedure Calls - Invokes named functions on remote clients or servers and returns results to coordinate distributed actions.
  • RPC Servers - Routes remote procedure calls between clients and backend processes for request/response workflows.
  • Authentication and Authorization - Combines multiple authentication mechanisms with a declarative permission language for granular access control.
  • Per-Message Authorizations - Validates user identity and permissions on each individual message, from the connection down to the data payload.
  • Credential Authentication - Validates client credentials against one of several configurable authentication strategies before granting access.
  • Authentication Gateways - Authenticates and authorizes every message using multiple strategies including JWT, HTTP, and file-based credentials.
  • RPC - Routes function invocations from requesting clients to registered provider processes and returns results.
  • Action-Based Access Restrictions - Controls which users can create, read, write, delete, or listen to specific records based on user attributes.
  • Declarative Permission Modelers - Uses a declarative permission language to control access to records, events, and RPCs.
  • Granular Permission Systems - Uses a declarative permission language to control which user can read, write, or invoke each record, event, or RPC.
  • Authentication Strategies - Validates incoming connections against one or more authentication mechanisms in declared order until one succeeds.
  • Authentication Pipelines - Validates client credentials against multiple configurable authentication mechanisms in declared order.
  • Event Driven Messaging - Routes topic-based messages from any sender to all subscribers with automatic serialization.
  • Remote Procedure Calls - Provides a remote procedure call mechanism for invoking backend functions from clients.
  • Atomic Multi-Path Updates - Applies several changes to different parts of a record in a single atomic operation.
  • External Storage Integrations - Connects to external databases and caches for persistent storage and fast short-term data access.
  • Database Backend Integration - Connects to external databases for persistent storage and querying of records.
  • Single-Threaded - Runs multiple independent single-threaded nodes that distribute load across cloud instances.
  • Horizontal Scaling Deployments - Runs multiple single-threaded server nodes that distribute load across cloud instances.
  • Application-Level Request Distributors - Balances RPC invocations across multiple registered providers with automatic failover to alternatives.
  • Subscription Listeners - Implements a listen pattern that notifies backend services when clients subscribe to topics.
  • Subscription-Activated Data Streams - Notifies backend services when clients subscribe to topics to start streaming live data.
  • JSON Web Tokens - Verifies client identity by decoding and validating a signed JWT presented at connection time.
  • TLS Traffic Encryption - Secures all traffic between clients and the server using TLS/SSL encryption.
  • Pluggable Storage Backends - Supports plugin-based storage architecture for connecting to external databases and caches.
  • Data Validation - Checks new or modified data against user-defined expressions before allowing a write operation to proceed.

Historial de estrellas

Gráfico del historial de estrellas de deepstreamio/deepstream.ioGráfico del historial de estrellas de deepstreamio/deepstream.io

Búsqueda con IA

Explora más repositorios increíbles

Describe lo que necesitas en lenguaje sencillo: la IA clasifica miles de proyectos open-source curados por relevancia.

Start searching with AI

Preguntas frecuentes

¿Qué hace deepstreamio/deepstream.io?

deepstream.io is an open-source realtime server that synchronizes JSON records, events, and remote procedure calls across clients and backend services. It functions as a realtime data sync server, event pub/sub server, record database server, and RPC server, all within a single platform. The server authenticates and authorizes every message using multiple strategies including JWT, HTTP, and file-based credentials, with a declarative permission language controlling access to…

¿Cuáles son las características principales de deepstreamio/deepstream.io?

Las características principales de deepstreamio/deepstream.io son: General-Purpose Realtime Servers, Cross-Client Synchronization, Realtime Document Synchronization, Realtime Synchronizations, Realtime Synchronization, Realtime Document Database Servers, Nested Path Reads and Writes, Realtime List Synchronizations.

¿Qué alternativas de código abierto existen para deepstreamio/deepstream.io?

Las alternativas de código abierto para deepstreamio/deepstream.io incluyen: deployd/deployd — deployd is a realtime API framework and MongoDB backend as a service that allows for the creation of networked… socketcluster/socketcluster — Highly scalable realtime pub/sub and RPC framework. faye/faye — Faye is a real-time messaging middleware and WebSocket publish-subscribe server. It functions as a communication layer… nats-io/nats.go — This is a Golang client library for interacting with a cloud native distributed messaging system. It provides the… neuecc/magiconion — MagicOnion is a remote procedure call framework for the .NET platform and Unity. It functions as a binary API protocol… qicosmos/rest_rpc — Rest_rpc is a C++20 remote procedure call framework designed for building distributed services. It provides an…

Alternativas open-source a Deepstream.io

Proyectos open-source similares, clasificados según cuántas características comparten con Deepstream.io.
  • deployd/deploydAvatar de deployd

    deployd/deployd

    4,942Ver en GitHub↗

    deployd is a realtime API framework and MongoDB backend as a service that allows for the creation of networked interfaces synchronizing data and events between clients and servers. It functions as a JavaScript API middleware that can be integrated with HTTP servers to provide authentication, request interceptors, and realtime capabilities. The project features a self-hosted API management dashboard for configuring resource settings, managing data collections, and monitoring server status through a web-based interface. It includes a realtime data synchronization engine that pushes live databas

    JavaScript
    Ver en GitHub↗4,942
  • socketcluster/socketclusterAvatar de SocketCluster

    SocketCluster/socketcluster

    6,197Ver en GitHub↗

    Highly scalable realtime pub/sub and RPC framework

    JavaScriptdockerframeworkjavascript
    Ver en GitHub↗6,197
  • faye/fayeAvatar de faye

    faye/faye

    4,386Ver en GitHub↗

    Faye is a real-time messaging middleware and WebSocket publish-subscribe server. It functions as a communication layer that routes messages between clients and manages channel subscriptions to enable data synchronization across the web. The project provides a cross-domain communication gateway, allowing web clients on different domains to communicate with a central server. It is built as a clustered messaging backend that can share state across multiple instances using external storage to handle high volumes of persistent network connections. Its capability surface includes pub-sub logic for

    JavaScript
    Ver en GitHub↗4,386
  • nats-io/nats.goAvatar de nats-io

    nats-io/nats.go

    6,657Ver en GitHub↗

    This is a Golang client library for interacting with a cloud native distributed messaging system. It provides the necessary tools for Go applications to exchange messages using publish-subscribe and request-reply patterns, as well as specialized clients for managing persistent streams and distributed storage. The library includes a JetStream client for durable message streaming and replay, a Key-Value store client for managing distributed state with versioning and watchers, and an Object Store client for the storage and retrieval of large binary files via chunked delivery. The implementation

    Gocloud-nativecloud-native-architecturescloud-native-microservices
    Ver en GitHub↗6,657
Ver las 30 alternativas a Deepstream.io→