1

Topic: The client to service

There are two microservices they  among themselves on http. Service And  service of Century At both services two different solutions. A question. In what  the client to V.Uchityvaja's service should lie that it can use and other services.

2

Re: The client to service

Hello, Gattaka, you wrote: G> There are two microservices they  among themselves on http. Service And  service of Century At both services two different solutions. G> a question. In what  the client to V.Uchityvaja's service should lie that it can use and other services. In the third.

3

Re: The client to service

Hello, neFormal, you wrote: F> Hello, Gattaka, you wrote: G>> There are two microservices they  among themselves on http. Service And  service of Century At both services two different solutions. G>> a question. In what  the client to V.Uchityvaja's service should lie that it can use and other services. F> in the third. It would Seem logically. But let's go further. On an example.net. Let we have still a solution with . The assembly lies in nuget. It is natural that it use all. Including the client to service (we assume for an example). When we update . We can update it in service A, but not update in the client to service B. There will be an error in runtime, since dll c  one. And two assembly of service  on different versions. Or it is possible to update the version  everywhere, but it is not necessary and it is not convenient very much. Since refer to it all. How in this case to be? It actually was the main question.

4

Re: The client to service

Hello, Gattaka, you wrote: G> How in this case to be? To use bindingRedirect... <<RSDN@Home 1.3.108 alpha 5 rev. 56>>

5

Re: The client to service

Hello, _Raz _, you wrote: _R _> Hello, Gattaka, you wrote: G>> How in this case to be? _R _> to use bindingRedirect While this decision seems to me importing  complexity. You as was specific could not explain it it is possible to use.

6

Re: The client to service

Hello, Gattaka, you wrote: G> When we update . We can update it in service A, but not update in the client to service B. There will be an error in runtime, since dll c  one. And two assembly of service  on different versions. G> or it is possible to update the version  everywhere, but it is not necessary and it is not convenient very much. Since refer to it all. How in this case to be? It actually was the main question. I am more on JVM, but unless in # the pattern does not have concept binary compatibility? In an ideal, such  parts as , should remain backward-compatible. Retreats from this rule lead IPC, OSGi, to microservices.

7

Re: The client to service

Hello, Gattaka, you wrote: F>> in the third. G> it would Seem logically. But let's go further. On an example.net. Let we have still a solution with . The assembly lies in nuget. It is natural that it use all. Including the client to service (we assume for an example). G> When we update . We can update it in service A, but not update in the client to service B. There will be an error in runtime, since dll c  one. And two assembly of service  on different versions. G> or it is possible to update the version  everywhere, but it is not necessary and it is not convenient very much. Since refer to it all. How in this case to be? It actually was the main question. To use both versions if it would not be desirable to be updated. nuget is not able in ?

8

Re: The client to service

Hello, Gattaka, you wrote: G> When we update . We can update it in service A, but not update in the client to service B. There will be an error in runtime, since dll c  one. And two assembly of service  on different versions. G> or it is possible to update the version  everywhere, but it is not necessary and it is not convenient very much. Since refer to it all. How in this case to be? It actually was the main question. It is necessary to do the client by the separate project. With the releases,  and so on.  to update its versions in services And and it would will be necessary thoughtfully, reading  and so on. But it is is specific with broad gulls it is possible  easier,  in the client https://github.com/net-commons/common-logging