Rootconf 2018

Rootconf 2018

On scaling infrastructure and operations

##About Rootconf 2018 and who should attend:

Rootconf is India’s best conference on DevOps, SRE and IT infrastructure. Rootconf attracts systems and operations engineers to share real-world knowledge about building reliable systems.

The 2018 edition is a single track conference. Day 1 – 10 May – features talks on security. Colin Charles (chief evangelist at Percona Foundation), Pukhraj Singh (former national cybersecurity manager at UIDAI), Shamim Reza (open source enthusiast), Alisha Gurung (network engineer at Bhutan Telecom) and Derick Thomas (former network engineer at VSNL and Airtel Bharti) will touch on important aspects of infrastructure, database, network and enterprise security.

Day 2 – 11 May – is filled with case studies and stories about legacy code, immutable infrastructure, root-cause analysis, handling dependencies and monitoring. Talks from Exotel, Kayako, Intuit, Helpshift, Digital Ocean, among others, will help you evaluate DevOps tools and architecture patterns.

If you are a:

  1. DevOps programmer
  2. Systems engineer
  3. Architect
  4. VP of engineering
  5. IT manager

you should attend Rootconf.

Birds Of Feather (BOF) sessions at Rootconf 2018 will cover the following topics:

  1. DevSec Ops
  2. Microservices - tooling, architecture, costs and culture
  3. Mistakes that startups make when planning infrastructure
  4. Handling technical debt
  5. How to plan a container strategy for your organization
  6. Evaluating AWS for scale
  7. Future of DevOps

Rootconf is a conference for practitioners, by practitioners.

The call for proposals is closed. If you are interested in speaking at Rootconf events in 2018, submit a proposal here:


NIMHANS Convention Centre, Lakkasandra, Hombegowda Nagar, Bengaluru, Karnataka 560029.

Schedule, event details and tickets:

For more information about Rootconf, sponsorships, outstation events, contact or call 7676332020.

Hosted by

We care about site reliability, cloud costs, security and data privacy

Soubhik Bhattacharya


Dealing with a (failing) dependency

Submitted Mar 9, 2018

A microservice calling another via REST is a common scenario. We use 4 patterns for dealing with failures associated with this scenario viz bulkheads, timeouts, circuit breaker and management plane. I share deep insights learnt from using these patterns in production. I also describe the principles and building blocks for management plane pattern.


I start with a simple pattern that most of us can relate to: a microservice calling another via a REST API. I show how things can go wrong in this pattern and how we deal with them at Intuit.

I cover 4 resiliency design patterns in details: sharing the motivation, key intuitions and deep insights drawn from our experience of using them in production.

3 of the 4 patterns (bulkheads, timeouts and circuit breaker) are better researched on the internet. however, the practical lessons we learnt are rather unique and not easily available in public domain.

the 4th pattern, management plane, though used in practice, is not discussed often. in this talk, I cover the principles and building blocks for this pattern.

I also touch upon Hystrix, a popular library for microservice resiliency and describe what it does and does not solve.

Speaker bio

Soubhik is a hands-on technical leader. In his current role at Intuit, he’s focussed on building highly resilient microservices that deliver frictionless authentication experience to Intuit’s users.

His past experience spans across embedded operating systems for networking (Cisco), information extraction and search (Yahoo! and BloomReach), electronic design automation (Mentor Graphics and Atrenta).



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

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

{{ errorMsg }}

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

Hosted by

We care about site reliability, cloud costs, security and data privacy