The motivation is that users want to implement Fallback services (e.g. a different AppConfig server instance / region) in case a connection failure persists.
We could in theory extend the FallbackDataSource meachanism we already have. However the Node / Python / Go clients have a way simpler implementation:
They expose a isConnected() method and all fallback logic is then responsibility of the user.
The motivation is that users want to implement Fallback services (e.g. a different AppConfig server instance / region) in case a connection failure persists.
We could in theory extend the FallbackDataSource meachanism we already have. However the Node / Python / Go clients have a way simpler implementation:
They expose a
isConnected()method and all fallback logic is then responsibility of the user.