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

 
0 favorite thumb_down thumb_up 12 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
  • Naresh Jain
    By Naresh Jain  ~  1 year ago
    reply Reply

    Hi Kiruthika,

    Thanks for the proposal. The topic is certainly interesting. However it feels like a bit of repetition from the last year's workshop:

    Would you be interested in exploring one of the following options:

    • Present a 45 mins case study on how your team has leveraged Microservices + Docker to solve real business problems
    • Present a compressed 90 mins live-demo (with parts of it prepared before the session)

    Thanks for your consideration.

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

      Hi Naresh,

      Thank you for those pointers.

      I have personally attended the session by Fred in another conference, and definitely the proposed workshop covers wider topics than just Microservices. Fred covered the concept of Microservices in depth, helping people to understand the value & benefits of Microservices. Whereas this workshop assumes that people are aware of Microservices, and covers only hands-on and testing/scaling challenges.

      "Agile Infrastructure" is more interesting and see lots of overlap. Earlier workshop focuses mainly on 'Docker' and not much on 'services'/'CD'. Docker images, containers, consul are kind of repetitive, but they are the basic building blocks.

      This workshop tries to replicates the journey of an actual application, including CD/pipeline set up, services extraction, Consumer Driven Contracts, Docker Swarm, hands-on module on Kibana, Prometheus, Consul & Registrator.

      That being said, I am open to do a case study/live demo of the same, but I see more value in doing a hands-on workshop. Again going by feedback from my other conferences, hands-on workshop had more positive feedback/learning than talk on the same topic.

      Cheers

      Kiru

      • Naresh Jain
        By Naresh Jain  ~  1 year ago
        reply Reply

        Thanks for the prompt response Kiru.

        I agree with you that a workshop is more effective than a talk. However as a conference, we've constraints around how many pre/post conference workshops we can host.

        My recommendation: You present a 45 mins case study that replicates the journey of an actual application, including CD/pipeline set up, services extraction, Consumer Driven Contracts, Docker Swarm, hands-on module on Kibana, Prometheus, Consul & Registrator. If this is received well, we can certainly work in advance and plan a pre/post conference workshop for 2017.

        If this makes sense, request you to please update the proposal to reflect the same and we'll accept the proposal.

        Thank you.

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

          Hi Naresh,

          I can understand. I will update the proposal accordingly and get back to you in 2/3 days. 

           

          Cheers

          Kiru

          • Naresh Jain
            By Naresh Jain  ~  1 year ago
            reply Reply

            Thanks. If you can do it a bit sooner, we'll be doing the final acceptance this weekend and opening the conference registrations from Monday. Thanks.

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

              I have updated the proposal. Sorry, I could not get back earlier.

              Good day!

  • Joel Tosi
    By Joel Tosi  ~  1 year ago
    reply Reply

    Hi Kiruthika,

         Could you provide examples of the training material and timing breakdowns.  I'm trying to understand how much time is spent where, how the exercises build / intersect, and how tangible the work is.

    Best,

    Joel

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

      Hi Joel,

      As mentioned in below comment, the exercises and required module code will be bundled and available as a VM. Also, each module will have start and end state. If users are struck in between/lagging behind they can easily shift to start/end state of any module.

      The time focus will be more like below,

      Initial set up

      Continuous delivery, Pipeline set up,Intro to monolith app - 1 hour

      Intro to Microservices, Extraction, Docker commands - 1 hour

      CDC testing - 1 hour

      Service discovery, Multi-host deployment - 1 hour

      Logging, monitoring, alerting - 1 hour

      Emerging tools, tech, tips & tricks, lessons learnt - 45 mins

       

      cheers

      Kiru

      • Joel Tosi
        By Joel Tosi  ~  1 year ago
        reply Reply

        Thanks much Kiru.  I like the topic.  All day is a huge investment though.  To help me make a decision, I would need to know if you have delivered this before (if so - when / how large of an audience / what worked / didn't / how did you adjust) and also see the training deck at least. Would you be able to provide that?

        Best,

        Joel

    • Shiv Sivaguru
      By Shiv Sivaguru  ~  1 year ago
      reply Reply

      Kiruthika,

      While the proposal looks interesting, I wanted to understand a few points:

      - will the contents and structure keep the participants occupied for a whole day?

      - if spending a whole day, will there be any discussion on other containers [container management aspects] such as kubernetes

      - has this session been delivered elsewhere earlier?

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

        Hi Sivaguru,

        It is a complete hands-on workshop, where the entire workshop material is bundled in a VM. The workshop will have 5 major modules, each taking an hour. The modules will focus on Continuous delivery (pipeline setups), Microservices (extracting a service from monolith), Consumer driven contracts, Service discovery, Multi host deployment and operational concerns (logging, monitoring and alerting).

        The final module will focus on discussion around emerging tools in this space like Mesos, kubernetes, though it will not be hands-on

        A slightly varying content has been delivered at other conferences

         

        Cheers