schedule Mar 22nd 03:45 - 04:30 PM place Neptune people 36 Interested

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!

 
43 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

  1. Introduction to microservices common deployment patterns
  2. The pitfall of a couple of deployment strategies
  3. Introduction to Consumer-Driven Contract Tests
  4. How CDC helps in speeding up the Continuous Delivery
  5. Demo of CDC for two microservices integration.
  6. Putting CDC in CI/CD workflow.
  7. Q&A

Learning Outcome

  1. New testing strategy to fasten continues delivery
  2. Understanding multiple testing approaches
  3. Deploying services autonomously with confidence
  4. Understanding contract testing with example
  5. Automating service dependencies
  6. Putting CDC in CI/CD workflow

Target Audience

Developers, Analyst, Agile Coach, anyone who works in a cross functional team

schedule Submitted 7 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Anand Bagmar
    By Anand Bagmar  ~  7 months ago
    reply Reply

    Hi Gopi,

    Do you also plan to do a small demo of CDC? I think that will add a lot of value here, of you can manage it in the alloted time.

    • Gopinath Langote
      By Gopinath Langote  ~  7 months ago
      reply Reply

      Hello @Anand,

      Thank of reminding/suggesting to do a small demo of CDC.

      Of course, I will do a small demo, so that audience can understand it better.

      I have updated my description / Outline of talk to have CDC demo also.

       

       

      Thanks & Regards,

      Gopinath


  • Liked Akshay Dhavle
    keyboard_arrow_down

    Akshay Dhavle / Chirag Doshi - Fear of Failure - What's at stake and What can you do about it?

    45 Mins
    Talk
    Advanced

    In the era of digital transformation, enterprises want to be responsive and innovative. They adopt agile practices to help with this but there are few success stories. Moreover, most success is limited to the team level. There are deep cultural shifts required to be successful in the new world and one of the biggest elements that stops organizations from succeeding in the technology space is fear of failure. This crippling fear works at all levels from individuals to departments and business units and it is imperative for organizations to take bold steps to eradicate it.

    This talk will explain what's at stake because of the fear of failure and a few ways in which enterprises can tackle it.

  • Liked Richa Trivedi
    keyboard_arrow_down

    Richa Trivedi / Pramod N - Agile, products and changes in the world of AI

    45 Mins
    Talk
    Intermediate

    When agile came into being, a lot of the new technologies that we know today did not even exist. Does our definition of agile and the process that we follow change with new areas of technology thinking like data science, artificial intelligence & big data engineering coming into picture? Does INVEST make sense for data stories? Do we even write stories or should we work hypotheses instead? Do we need Acceptance Criteria or Exit criteria? How do lean, agile & product principles work in context of AI problems? What happens when science meets products?