deepstream.io

Release description

[5.0.1] - 2019.11.02

Features

• Replaces ENV variables in config loaded using fileLoader #1022

Fixes

• Fixes odd types scripting issue breaking plugin interfaces when using deepstream.getServices()
• Fixes hash generation via CLI #1025

[5.0.0] - 2019.10.27

Features:

• New License
• Singular HTTP Service
• SSL Support reintroduced
• Better Config file validation
• JSON Logger
• NGINX Helper
• Combined authentication handler
• Embedded dependencies
• Builtin HTTP Monitoring
• Storage authentication endpoint
• Guess whats back, official clustering support!

Backwards compatibility

• Custom authentication plugins now have to use the async/await API
• Custom permission handlers need to slightly tweak the function arguments
• Deployment configuration has to be (simplified) to respect the single HTTP/Websocket port

Upgrade guide

You can see the upgrade guide for backwards compatibility here

[4.2.5] - 2019.10.01

Fix

Removing dom lib from typescript, which exposed variables that throw exceptions #1008

Release description

[4.2.3] - 2019.10.01

Improvement

Hardening the config validator

Fix

Allow empty password for mqtt endpoint when authentication is not enabled (@Aapkostka) #1003

ResolvePluginClass should look for lowercase plugins #1002

RPC not routed to different deepstream node depending on startup order #1001

Misc

Updating dependencies

Release description

Release description

[4.2.0] - 2019.09.09

Feat

Two new connection endpoints have been added. They are currently experimental and will be properly
announced with associated documentation.

One endpoint is mqtt! This allows us to support mqtt auth (using username and password), retain using records and QoS 1 using write acks. The only issue is since mqtt only supports one sort
of concept (with flags distinguishing them) we bridge both events and records together. That means if you subscribe to 'temperature/london', you'll get the update from both a client doing event.emit('temperature/london') and record.setData('temperature/london').

The second endpoint is ws-json which allows users to interact with deepstream by just passing through json serialized text blobs instead of protobuf. This is mainly to help a few people trying to write SDKs without the hassle of a protobuf layer.

Value also injects a name variable which allows you to reference the name your currently in. Useful for cross referencing.

[4.1.0] - 2019.08.30

Feat

Backwards compatibility with V3 clients / text protocol using a ws-text connection endpoint

This has a couple of small differences, like has is no longer supported and snapshot errors
are exposed using the global error callback instead of via the response. Otherwise all the e2e
tests work, and best of all you can run both at the same time if you want to run JS 4.0
and Java 3.0 simultaneously!

It is worth keeping in mind there is a small CPU overhead between switching from V3 custom deepstream
encoding to JSON (V4), so it is advised to monitor your CPU when possible!

- type: ws-text
    options:
        # port for the websocket server
        port: 6021
        # host for the websocket server
        host: 0.0.0.0

[4.0.6] - 2019.08.19

Feat

Allow SUBSCRIBE and READ without CREATE actions, for clients that are in read only mode

Improvement

Adding declaration types (thank you @Vortex375!)

[4.0.5] - 2019.08.09

Improvement

Adding meta objects to logs and monitoring for easier tagging to monitoring solutions

[4.0.4] - 2019.08.05

Fix

• Don't buffer error messages in relation to connections, otherwise the client will get the close event first
• Ignore ping messages during the connecting and authenticating stages

[4.0.3] - 2019.08.04

Fix

• Notify monitoring plugin of all messages sent out individually

[4.0.2] - 2019.08.03

Features

• Alpine docker image

Fix

• Override the http port and host correctly

[4.0.1] - 2019.07.31

Improvements

• Exit immediately if HTTP server port is occupied
• When using debug, log exact error to why a plugin could not be loaded

Features:

• New protobuf protocol support (under the hood)
• Bulk actions instead of individual subscribes (under the hood)
• Official Plugin Support
• Monitoring Support
• Clustering Support (with small caveats)
• Listening Discovery Simplification
• V2 storage API
• V2 cache API
• Notify API

Improvements

• Lazy data parsing
• Improved deepstream lifecycle
• Upgraded development tools
• New deepstream.io website

Backwards compatibility

• All V3 SDKs no longer compatible due to protobuf binary protocol

Upgrade guide

You can see the upgrade guide for backwards compatibility here

TLDR;

You can see the in depth side explanation of the changes here