Thanks for your interest. Sure – there is another blog post that shows what the functionalities of PACT are: https://blog.novatec-gmbh.de/introduction-microservices-testing-consumer-driven-contract-testing-pact/. Which of the frameworks you are going to choose is a question that depends on your project context, team set up and therefore not easy to answer in a blog post. You can also use the demo projects as basis for further evaluation 🙂
Thanks for the two nice blog posts about CDC. Is it possible that you elaborate more on the differences between Pact and Spring Cloud Contract? For instance, what is possible in one and not in other? Which is easier to integrate with continuous delivery systems. Should Pact still be an option to consider for the projects implemented using Spring Cloud or should Spring Cloud Contract be the default choice for these type of projects? I would like to hear your thoughts about these.
Thank you for your feedback! I really found the framework great!
This is a great post! Congrats 🙂 Glad that you enjoyed working with Spring Cloud Contract.
> In this blog post we presented the second framework supporting the concept behind CDC – Spring Cloud Contract. It is only suitable for JVM based applications.
Not necessarily. I’d say that it’s more suited for JVM based applications. When developing a non JVM basde application, if you’re the consumer, then you can run the Stub Runner Boot application – https://cloud.spring.io/spring-cloud-contract/spring-cloud-contract.html#_stub_runner_boot_application just by typing `java -jar …` . That way you’ll automatically download the stubs and run them aside of your process.