You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In complex microservices architecture, usually what you have is a consumer A that calls another provider B and at the same time, this provider B acts as a consumer of other services, let's call it Providers C and D.
So when you want to validate that Consumer A meets the expectations from Provider B, you write the contract test for the consumer by stubbing Provider B. But when you want to validate that Provider B also meets the expectations you need to stub its collaborators (Providers C and D). So in this case what you need is Service Virtualization to "mock" that services.
Ideally, you should not add a new technology for service virtualization, you could use the same used on the consumer side but in provider side.
Issue Overview
In complex microservices architecture, usually what you have is a consumer A that calls another provider B and at the same time, this provider B acts as a consumer of other services, let's call it Providers C and D.
So when you want to validate that Consumer A meets the expectations from Provider B, you write the contract test for the consumer by stubbing Provider B. But when you want to validate that Provider B also meets the expectations you need to stub its collaborators (Providers C and D). So in this case what you need is Service Virtualization to "mock" that services.
Ideally, you should not add a new technology for service virtualization, you could use the same used on the consumer side but in provider side.
https://github.com/lordofthejars/pactstandalone
Expected Behaviour
Use Pact Consumer stubbing capabilities in Provider to simulate the service dependencies of the provider.
The text was updated successfully, but these errors were encountered: