yea so current envoy config is for all shards within a database and dc.
in current version
- each DC requires individual envoy xds server. thus each DC specific envoy XDS will have the dc-id configured accordingly. this also means that clients won't be able to make cross DC calls directly.
- we will only support 1 database for now.
I think above requirements are fine for current DKV.
in next version, we will change both DKV client SDK and envoy xds to support multi database, inter DC interaction with the same envoy xds and DKV cluster.
above is additional effort which we can prioritise based on which client is onboarding.
Originally posted by @krishan1390 in #99 (comment)
yea so current envoy config is for all shards within a database and dc.
in current version
I think above requirements are fine for current DKV.
in next version, we will change both DKV client SDK and envoy xds to support multi database, inter DC interaction with the same envoy xds and DKV cluster.
above is additional effort which we can prioritise based on which client is onboarding.
Originally posted by @krishan1390 in #99 (comment)