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
Is your feature request related to a problem? Please describe.
Nowaday SQL is scalable like YugabyeDB or Cockroachdb, so there is no need to maintain another NoSQL DB to implement Federated Cluster. Which will help to simplify the deployment of OpenSIPS but still keep the scalability.
Describe the solution you'd like
Support columnar capability to cachedb_sql or a way to config federated cluster without enabled cachedb.
Describe alternatives you've considered
No any alternatives unless deploying both SQL and NoSQL.
The text was updated successfully, but these errors were encountered:
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Yes, there are so many scalable and popular SQL solutions nowadays (Redis Cluster, Percona PXC, YugaByte, etc.), that we should definitely add support for the federated usrloc cluster to work with them.
Nowadays, with the current solution (originally designed in 2018), you most often end up maintaining an additional NoSQL cluster just for storing user location metadata, which although seems nice from a separation (microservices) point of view, the load on this cluster is not that high and it could very well work with just an extra database in your SQL cluster, e.g. user_location.
Is your feature request related to a problem? Please describe.
Nowaday SQL is scalable like YugabyeDB or Cockroachdb, so there is no need to maintain another NoSQL DB to implement Federated Cluster. Which will help to simplify the deployment of OpenSIPS but still keep the scalability.
Describe the solution you'd like
Support columnar capability to cachedb_sql or a way to config federated cluster without enabled cachedb.
Describe alternatives you've considered
No any alternatives unless deploying both SQL and NoSQL.
The text was updated successfully, but these errors were encountered: