What if the updated version of app faces the problem of multiple versions of the interface at the same time?

The updated version of app is faced with the problem that multiple versions of the interface exist at the same time. In view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

Background:

The updated version of app faces the problem of multiple versions of the interface at the same time.

Scenario 1: system-level service registration and discovery

Http requests the caller to pass the version through header, defining the specification. Dynamically change the target address in the business system caller. Like svc1,svc2. Dynamically modify the destination address when feign is called.

Scenario 2: application-level service registration and discovery

Application layer version configuration, application layer routing. The application service is registered with the registry, and the routing implementation of the service center version service list is found through the parameters.

Change points:

Application Gateway layer svcname

Each module adjusts svcname to each other

The answer to the question about how the updated version of app is faced with multiple interfaces and multiple versions at the same time is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.