SRE Conf 2023
Rootconf For members

SRE Conf 2023

Availability and reliability 24/7- the SRE life



Schedule for the conference on 24 November is published.

Why SRE Conf?

When any organization goes from product market fit or beta test phase to production rollout, or from first x customers to 10x or 100x customers and starts scaling, they typically start running into challenges with systems stability and resiliency. These challenges change with every phase of growth. So does the need for having a SRE team and/or a DevOps team, and the role these teams play.
Unfortunately, there is no one-size-fits-all solution when it comes to what roles these teams should play, and which tools various teams should use to track the metrics and processes involved. But there are some common building blocks that apply in similar (and different) ways and forms for most teams. The idea of the SRE Conference is to get together and to know about these building blocks, share and learn about the themes that fall under the SRE umbrella.

SRE Conf tracks

SRE Conf is a two-track conference. The track, “Culture, career and Evolution” is more focused on leadership, team, and organizational topics while the “Stories from the Trenches” track will cover real-world scenarios, and lessons learned which will help engineers and engineering teams to upskill themselves by understanding experiences from their industry peers.

Culture, career, and evolution

  1. SRE v/s DevOps v/s Platform Engineering teams in organizations.
  2. Hiring and building SRE teams.
  3. Blameless postmortems.
  4. Role of AI in SRE/DevOps/Platforms.
  5. FinOps and cost optimization.
  6. SRE Anti-patterns

Stories from the trenches:

  1. Incident management.
  2. Change management.
  3. Scalability and performance.
  4. SLA/SLO and golden signals.
  5. Security and DevSecOps.
  6. Systems and networking.

Key takeaways for participants

  1. Improved understanding of organizational needs and requirements.
  2. Enhanced optimization skills.
  3. Networking opportunities.
  4. Knowledge sharing and community building.

Who should participate

  • Members of SRE, DevOps or platform teams.
  • A software developer or manager who is responsible for services running on any cloud platform or on-prem data center.
  • Technology leader of an engineering team that manages critical systems which should have minimal to zero downtime.


If you are interested in speaking at the conference, submit your talk idea here. The editors - Sarika Atri, Safeer CM and Saurabh Hirani - will review your talk description and give feedback.

Speakers will also receive feedback and assistance during rehearsals from past speakers such as Sitaram Shelke.

Guidelines for speaking, speaker honorarium policy, and travel grant policy details are published here.

About the editors

This conference themes were set up by Sarika Atri and Safeer CM. Together with Saurabh Hirani, the three editors have:

  1. Reviewed the talks.
  2. Set up the editorial workflow.
  3. Finalized talk selections.
  4. Curated the schedule.

Sarika Atri is Software Architect with over twenty years experience in the industry. Sarika was reviewer for Rootconf Cloud Costs Optimization conference held in July 2023.
Safeer CM is Senior Staff SRE at Flipkart. He is author of Architecting Cloud-Native Serverless Solutions published by Packt.
Saurabh Hirani is former editor of Rootconf, and a passionate member of the community. Saurabh is SRE at,. He has a keen interest in mentoring speakers.

Become a Rootconf Member to join

SRE Conf is a community-funded conference. It will be held in-person. Attendance is open to Rootconf members only. Support this conference with a membership. If you have questions about participation, post a comment here.


Sponsorship slots are open for:

  1. Tool and solutions providers.
  2. Companies interested in tech branding for hiring.

Email sponsorship queries to

Contact information

Join the Rootconf Telegram group at or follow @rootconf on Twitter.
For inquiries, contact Rootconf at +91-7676332020.

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Raadhikaa Srinivasan

Shell based architecture for maintaining High Availability

Submitted Sep 30, 2023

High availability is critical for tech companies to meet user expectations, maintain business operations, honor SLAs, gain a competitive edge and scale operations in their services or products.
Maintaining high availability requires implementing a robust architecture. It is a challenge faced by every multi-tenant tech company that has grown larger over the past years, in terms of number of customers, size, and features. Multi-tenancy means that multiple customers of a cloud vendor are using the same compute resources. In a multi-tenant architecture, an issue for a single customer can easily cascade and impact all its neighbors. As a matter of fact, there have been incidents in the past where a simple failure for one customer at the database level has threatened to take the entire web cluster down.

Shell architecture

For Freshdesk to be a highly available product, blast radius had to be minimized. Blast radius is the maximum impact that might be sustained in the event of a failure. To minimize the blast radius and increase availability, shell architecture was introduced in Freshdesk. Shell architecture is a logical grouping of compute resources. Each shell is a stack, but serving only a smaller bucket of customers categorized by shards that they belong to. A shard is a horizontal partition of data in the database. Hence a set of customers are mapped to a particular shard. Set of shards are mapped to a shell. For observability of each stack and tenant, shell information is exposed as metric and shell specific alerts are configured.

Key Benefits of shell architecture

Flexibility to increase compute capacity for specific use cases.
Flexibility to isolate noisy tenants and help reduce blast radius.

Any company can adopt this architecture to maintain high availability as the company scales. This will give the company feasibility to isolate noisy tenants and help reduce blast radius.
To move to this architecture, companies need to come up with an approach to group customers into different stacks based on a particular/ set of criterias.For example, the nature of requests (light/heavy impact to DB) , rate of requests (rpm), business priorities of requests etc. Companies must have infra setup to support on demand scaling of stacks and adopt autoscaling solutions to scale within stacks.

This talk will focus on primary motivations, architecture, challenges companies should prepare for if they decide to move to shell architecture and its benefits.


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

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

{{ errorMsg }}

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

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more