-1

Which storage may be used for storing RefreshTokens (TTL=30min)? This storage has to be used by multiple instances of OAuth2 Authorization Servers written in java.

The possible options are:

  1. Hazelcast IMDG (written in Java)
  2. Postgres (written in C/C++)
  3. Redis (written in C)
  4. Memcached (written in C)
  5. MongoDB (written in C ?)
  6. Terracotta (written in Java)
  7. Infinispan (written in Java)

Those refresh tokens do not need strong transactional consistency and backup ability provided by Postgres.

Features needed:

  1. High availability mode
  2. Storing simple data i.e. JSON object
  3. TTL for rows
  4. High performance for minimal latency when refreshing tokens
  5. Consise API to access storage from Admin UI for management purposes

Hazelcast is a pretty candidate, but as far as I know it does not have adequate UI for data management i.e. for RefreshToken revocation. Postgres provides pgadmin for accessing stored data.

So which one would you prefer to use in such case?

aalekseyev
  • 133
  • 1
  • 10

1 Answers1

0

We have chosen Hazelcast IMDG. High performance and no persistence

aalekseyev
  • 133
  • 1
  • 10