Upgrade to PRO for Only $50/Year—Limited-Time Offer! 🔥

Confidently Releasing Microservices With Consum...

Confidently Releasing Microservices With Consumer Driven Contract Testing

“Many teams working with microservices need confidence they don’t break functionality when making changes. System integration tests, functional tests, and sometimes manual tests are older ways to obtain that confidence. These processes may take more than 1 day or even more if different teams or a different company own the services.

To ensure the same level of confidence and speed up delivery, we can create Contracts for integrations between consumers and providers. Contracts created by consumer services need to pass with every build going in production to guarantee the integrations between systems/services work fine. Checking these contracts in a CI/CD pipeline makes feedback loops even faster.

A Contract is a collection of agreements between a Consumer and a Provider that describes the interactions that can take place between them. Consumer Driven Contracts (CDCs) is a pattern that drives the development of the Providers from its Consumer’s point of view. It is TDD for microservices.

This talk covers an end to end demo of contract testing between two microservices to show how to release microservices with confidence, get early feedback, speed up delivery, and comparison with other testing strategies.

Happy CDC!

Gopinath Langote

September 20, 2019
Tweet

More Decks by Gopinath Langote

Other Decks in Technology

Transcript

  1. Confidently Releasing Microservices With Consumer Driven Contract Testing @GopinathLangote Confidence

    has a common meaning of a certainty about handling something, such as work, family, social events, or relationships. - Wikipedia
  2. Confidently Releasing Microservices With Consumer Driven Contract Testing @GopinathLangote A

    particular way of designing software applications as suites of independently deployable services. - Martin Fowler
  3. Confidently Releasing Microservices With Consumer Driven Contract testing Client /

    Consumer Server / Provider @GopinathLangote Offerings, plans, or strategies motivated by customer demand or expectations.
  4. Confidently Releasing Microservices With Consumer Driven Contracts testing @GopinathLangote A

    contract is a legally binding agreement which recognises and governs the rights and duties of the parties to the agreement. - Wikipedia
  5. Unit Test Limited to method level Not aware of other

    service Trustworthy @GopinathLangote
  6. Mocked User Service Not aware of other service Changes No

    Feedback Loop Trustworthy Mocked Integration Test @GopinathLangote
  7. Consumer Contract Test Register expectation Request Account Service User Service

    Mock Contract Server TEST Response Contract File @GopinathLangote
  8. User Service Get the contracts Assert the expectations from consumer

    Consumer Provider Mock Contract Server Account Service Provider Verification @GopinathLangote
  9. Manually talk to concerned team/partner What if contract fails -

    Communication Automate communication 1. Automatic email 2. Automatic Jira tickets 3. Send alerts to slack @GopinathLangote
  10. 1. JVM 2. .Net 3. Ruby 4. Go 5. JavaScript

    6. Python 7. Php 8. Swift You can implement you own https://pact.io Pact @GopinathLangote