Skip to content

Latest commit

 

History

History
47 lines (31 loc) · 1.53 KB

README.md

File metadata and controls

47 lines (31 loc) · 1.53 KB
Raw

DSPS server storages

DSPS server needs storage to keep messages for (re)sending.

Following types are supported:

  • onmemory : Default, but not recommended for production
  • redis : Use Redis to store messages

See each documents for more detail.

To know how to configure DSPS server, see configuration file documentation.

What storage used for

DSPS stores some information to the storage such as...

  • Unconsumed messages queue of each subscribers
    • DSPS (re-)send messages until subscribers acknowledge it
  • Set of revoked JWT

Multiple storages

You can configure multiple storages.

If multiple given, DSPS server write information into all storages thus it increase durability.

Caution: do not change storage ID after deployment, otherwise it may cause data lost.

storage:
  myRedisA:  # <-- Do not modify this ID after deploy
    redis:
      singleNode: 'my-redis-server-host-1:6379'
  myRedisB:  # <-- Do not modify this ID after deploy
    redis:
      singleNode: 'my-redis-server-host-2:6379'

If you specify two or more storages, DSPS perform followings:

  • Try to write to all available storages
    • If write operation succeeded at least one of storages, DSPS responds success to publisher
  • Read from all available storages and merge results
    • If successfully read from multiple storages, DSPS merge them based on the message ID

Because DSPS is append-only (publish-only) system, above simple rule works.