Continuously Delivering Microservices using Docker and Friends

No one has escaped the "Microservices" wave recently. As every architecture brings with it a lot of good practises, microservices brings success by helping us achieve a faster to market releases. Though the concept of "two-pizza" teams has been prevalent from early 2000’s, we now have many successful poster children to learn from. The success in this journey depends on infrastructure, automation, architecture and process elements. These includes good CI practises, different testing approaches, dynamic service registration & discovery, orchestration, logging and tracing. Though they are familiar, we all know that it is not as easy as it sounds, let us see what we need to consider from start to finish to make Microservices journey a real success in a 'show and tell' format.

Sneak Peek of what to expect: A bit of many concepts with corresponding tools including CI, Microservices, Docker, Consumer Driven Contracts, Service discovery, Consul, Registator, Multihost deployments, Kibana, Elastic search, Prometheus

1 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

In this 90 mins demo, we'll help you learn how to achieve autonomy between delivery teams so they can safely build, test, and independently deploy Microservices to production.

Learning Outcome

  • Continuously building, testing, and deploying Microservices autonomously
  • Testing Microservices and ensuring changes do not break dependent systems
  • Deploying and scaling Microservices in a multi-host Docker environment
  • Keeping different versions of Microservices running side-by-side
  • Service discovery
  • Operational concerns
  • Future trends

Target Audience

DevOps, Developers

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Sergey Shishkin
    By Sergey Shishkin  ~  1 year ago
    reply Reply

    Hi Kiruthika,

    Thanks for your proposal! I see the slide deck is over 200 slides and is theory heavy (not a bad thing). Just wanted to make sure you will be able to deliver the demo and explain the theory simultaneously.

    • Kiruthika Samapathy
      By Kiruthika Samapathy  ~  1 year ago
      reply Reply

      Hi Sergey,

      The deck has more slides as it is exported with each animation build. The emphasis is more on production readiness rather than how to run Docker containers. I just presented at Agile India, spent 30 minutes for demo and 60 minutes for the talk. I would prefer to keep this fluid and decide based on the maturity level of the audience.