Use couchbase as storage for Keycloak - nosql

Is there any guide to use couchbase or NoSQL as the database layer for Keycloak?
My research indicates that Keycloak only has support for RDBMS. MongoDB was supported once but was removed.

Related

Custom storage backend for JanusGraph

I am planning to implement a mongoDB storage backend for JanusGraph. The reason for picking MongoDB is mainly because all of our existing infrastructure and services use MongoDB, so it would be less net new maintenance requirement. Where do I get started? Is there a list of APIs that JanusGraph provides that need to be implemented by a custom backend? I couldn't find any documentation.
As of now Janusgraph supports only limited number of storage-backends as of now (Cassandra, HBase, BigTable, Berkeley). You can find more info here https://docs.janusgraph.org/storage-backend/.

ThingsBoard Hybrid mode

I can read in thingsboard configuration documentation (https://thingsboard.io/docs/user-guide/install/config/), in "Common database parameters" section, that database.ts.type can be sql or cassandra, and cassandra should be used for hybrid mode. what's that hybrid mode?
Do you mean that database.entities.type can be sql (postgres) and database.ts.type can be cassandra? and
vice versa?
what's the recommanded install? All on cassandra?
Many thanks,
Best regards
Found the answer here:
https://thingsboard.io/docs/reference/ , section "SQL vs NoSQL vs Hybrid database approach"
ThingsBard uses database to store entities (devices, assets, customers, dashboards, etc) and telemetry data (attributes, timeseries sensor readings, statistics, events). Platform supports three database options at the moment:
SQL - Stores all entities and telemetry in SQL database. ThingsBoard authors recommend to use PostgreSQL and this is the main SQL database that ThingsBoard supports. It is possible to use HSQLDB for local development purposes. We do not recommend to use HSQLDB for anything except running tests and launching dev instance that has minimum possible load.
NoSQL - Stores all entities and telemetry in NoSQL database. ThingsBoard authors recommend to use Cassandra and this is the only NoSQL database that ThingsBoard supports at the moment. However, due to a lot of interest to deployments with managed databases, we plan to introduce support on AWS DynamoDB in v2.3.
Hybrid - Stores all entities in SQL database and all telemetry in NoSQL database.

Can I do multi master replication for Mongo DB? Any reference architecture with Kubernetes is more expected in this question

I have a use case where we have a write and read intensive application using the MongoDB in backend. We are planning to implement federated K8s deployment for the Mongo DB with multi master architecture(How to do this?). I am looking for some suggestions on the architecture references/solutions if any that REALLY worked with Federation and active DB replication.
This doesn't directly answer you question but I know Kubedb does provide extensive database deployments within K8S. https://kubedb.com/docs/0.9.0/guides/mongodb/

Does mongo atlas support in-memory storage?

Do you know whether Mongo Atlas supports mongo in-memory storage or not?
If so, do we need to purchase Mongo DB enterprise edition license for enabling it or is it coming as part of Atlas itself?
As of today, MongoDB Atlas does not support in-memory storage engine. MongoDB Atlas only supports MongoDB versions 3.4, 3.6, and 4.0 with the WiredTiger storage engine.
However, you can utilise MongoDB Cloud Manager with In-Memory storage engine. As it offers more granular control, exposing numerous MongoDB configuration options such as the storage engine, startup parameters, and access control options. Cloud Manager also provides the ability to manage MongoDB on the infrastructure of your choice.
MongoDB Cloud Manager is better suited for advanced operations users who require this higher level of control, but Cloud Manager requires users to manage the full lifecycle of their infrastructure.
Please note that MongoDB In-Memory Storage Engine is part of the MongoDB enterprise edition offerings.

How to enable Mongodb Atlas data encryption at rest

I am trying to enable data encryption at rest for mongodb Atlas.The documentation is ambiguous.Some places it says its enabled by default and other places it says it is optional and uses underneath AWS volume encryption.Can any help me understand whether Atlas provides data at rest encryption.If so how to enable it.Thank you
It is documented at https://www.mongodb.com/blog/post/secure-your-mongodb-database-on-the-aws-cloud
Disk Encryption
MongoDB Atlas clusters on AWS make use of the General Purpose SSD
(gp2) EBS volumes, which include support for AES-256 encryption.
MongoDB Atlas makes encrypting your data at rest simple by allowing
you to just point and click from the management GUI to encrypt your
persistent storage