Rootconf Sessions

Rootconf Sessions

Presentations on DevOps and Dev-Oops

Make a submission

Submissions are closed for this project

DevOps and Dev-Oops sessions cover:

  1. DevOps (obviously!)
  2. Databases and database disasters
  3. Distributed systems
  4. Systems engineering
  5. Infrastructure security
  6. War stories, failures and anti-patterns with running operations and infrastructure

Rootconf is a forum for:

  1. DevOps engineers
  2. Systems engineers
  3. Software engineers
  4. DevOps leads
  5. Infrastructure security professionals and experts
  6. Cloud service providers
  7. Providers of the pieces on which an organization’s IT infrastructure runs – monitoring, log management, alerting, etc
  8. Engineering managers looking to optimize infrastructure and teams

Contact information: If you have questions, call Rootconf on 7676332020 or email

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more

Swamynathan S


Bringing Effective CI using AWS + Docker for Microservices

Submitted Mar 5, 2020

With organizations opting towards microservices for easy management and maintenance of services/releases, testing becomes more challenging in catching up with the speed of development. At such situations, traditional testing that helped waterfall models, before decades, will not be of use any more. While a lot of testing/quality teams follow matured process to solve their problems, there had always been some adhoc needs, especially on bringing up the environments for random testing, along with following matured testing. A lot of organizations lose a lot of time just to boot strap their environments with their manual/semi-automated way. Here, we would like to present, how Bounce is solving this problem. The intent is to ensure that we bring in a self-sustained environment on-demand (for CI automation / adhoc needs) with the needed hand-picked micro-services with specific builds, with dbs, caches, apps, queues etc. Further, this helped us in tying up the integration and e2e test frameworks to run against the environment created, once it was spawned - fulfilling the CI.

Initially, bringing up an environment in adhoc manner took us around 4 hours, which was reduced to 5-10 mins through this approach.

Technology Used : AWS, Code Build, BitBucket, Lambdas, Docker


  1. Requirement that we had - microservices/multiple repos and teams and parallel developments/daily releases/quality confidence
  2. AWS centric environment and why we arrived at the decision
  3. Architecture of our CI and boot-strapping solution
  4. How we achieve bringing up seletive environments with the right fall-back options.
  5. Q & A



Speaker bio

I currently work as a Sr SDET Architect at Bounce(Ex : AppDynamics, Ex: InMobi, Ex: VMware) and I have been passionate about taking test and release automations to the next level. I love solving complex problems and I have been recently solving problems related to CI/CD architecting and building test frameworks.



{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Pravin Nair

SRE Transformation - A Paradigm shift

The traditional SREs own Infrastructure and Production environments. What happens when we move from On premise Data Center to Cloud ? This session will talk about the evolution of both Developers and SREs in the Cloud world and what paradigm shift needs to happen for business to continue functional with minimal disruption. more

10 Mar 2020