Best Update Order for Server and Client Library Compatibility

·Jul 15, 2024 08:04 PM

Hi team, could you tell me what would be the preferred order to update deployed server version and the client library from the compatibility perspective? Currently, we’re using 3.24.0, the version we want to update to is 4.4.1. Should we update the client first, and the server next? Or the other way around?

5 comments

· Sorted by Oldest

Roger Y.
·
What are you referring to by “client library”?
Roger Y.
·
i think the server is generally backward compatible so it should go first
Roger Y.
·
but i think there may be some routes that have been re-named, but generally shouldn’t be a big issue
Gregory S.
·
Hi Roger, thanks for the response. My bad actually, I was thinking we use arize-phoenix library for some instrumentation within our codebase. But it looks that we actually only depend on opentelemetry and openinference libraries. So we should be good updating the deployed server only.
Roger Y.
·
ah yes, in that case there should be no worries
1

Roger Y.
·
What are you referring to by “client library”?
Roger Y.
·
i think the server is generally backward compatible so it should go first
Roger Y.
·
but i think there may be some routes that have been re-named, but generally shouldn’t be a big issue
Gregory S.
·
Hi Roger, thanks for the response. My bad actually, I was thinking we use arize-phoenix library for some instrumentation within our codebase. But it looks that we actually only depend on opentelemetry and openinference libraries. So we should be good updating the deployed server only.
Roger Y.
·
ah yes, in that case there should be no worries
1