You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the docker-compose files present in this repository tend to favor a "full-on" approach.
Using the DATABASE variable in the main .env file, the user can either takes the postgresOR the cassandra road.
Often, it is convenient to take the best of both worlds by storing the entities in postgres and the telemetries in cassandra as described in the official documentation as the "hybrid" storage:
Hi
Currently the docker-compose files present in this repository tend to favor a "full-on" approach.
Using the
DATABASE
variable in the main.env
file, the user can either takes thepostgres
OR thecassandra
road.Often, it is convenient to take the best of both worlds by storing the entities in postgres and the telemetries in cassandra as described in the official documentation as the "hybrid" storage:
Do you intend to evolve this repository so it can handle this common scenario? Thanks.
The text was updated successfully, but these errors were encountered: