I am looking at building in some multi-cloud resilience to a deployment, was
considering my options and would appreciate any thoughts !
So far, my ideas are:
1)
Run both clouds completely independently and have some middleware that pushes
the same API command to both PowerDNS instances. I know
On my experience, push is never a good mechanism to ’synchronize’ what we can
call ‘distributed’ databases (which in this case are not if we strictly embrace
the term).
In our case, we run multiple databases in this schema you mention cloud and
no-cloud but with no way to use a direct replicati
> Personally I have good experiences with Lightning Stream in a multi-cloud
> setup, but again: your "best option" might be different than mine.
>
I assume you are manually synching the two cloud S3 instances as AFAIK there no
built-in mechanism for Lightning Stream to write the same data to
On Friday, 24 January 2025 at 10:58, Alexis Fidalgo wrote:
>
> 1. If you loose connection between secondary and primary kafka will hold the
> updates (for the time you configure retention time in the topic) so when
> connection is restored, secondary site (consumer) will receive from where i
Your options seem valid. There's always going to be a trade-off and there's
always going to be some sort of sync-mechanism that you'll have to trust.
Whether that's the middleware app or the database replication mechanism or
something else.
What option to choose is a question only you can make
