Hello! I need some advise. Let’s say there are two...
# general
z
Hello! I need some advise. Let’s say there are two services A and B connected using http and protobuf A -> monolithic legacy service which is written in
Ruby
(Consumer) B -> microservice which is written in
GoLang
(Producer) Do I need to use
pact-ruby
and
pact-go
on consumer and producer side respectively? Is there anything in addition I should before introducing the pact contract tests?
t
I think your question is missing a verb, but it’s also a bit too general to help without more context
you’ll have a better time with pact-ruby and pact-go on each side, but you don’t technically need to
Also it might depend on what you want to do with protobuf. The protobuf plugin isn’t release ready, I think
#CEQBDD5U4 might have what you need
z
Hi @Timothy Jones Thanks for the response! Sorry for the typo in my question. Actually my question is pretty genetic and I’m confused since there are so many pact plugins available like pact-jvm, ruby, go etc
you'll have a better time with pact-ruby and pact-go on each side, but you don't technically _need_ to
Can you please explain it a bit? Would it be possible to write the pact tests without using pact-ruby since consumer service is written in pretty old version of Ruby ? Also, would contract tests be ideal to have between a monolithic and microservice ?
t
Would it be possible to write the pact tests without using pact-ruby since consumer service is written in pretty old version of Ruby ?
Apologies, I probably led you a bit astray. It's technically possible, but you'll be much better off using the native framework for your language(s), as then you can easily (eg) call client code, etc.
Also, would contract tests be ideal to have between a monolithic and microservice ?
Yes. Contract tests are useful any time you have a consumer (client) and a provider (server) that are deployed separately.
z
It helps! Thanks a ton. I’ll start on it and will get back in case of any questions:)
🙌 1
t
Glad to help!