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
Jaideep Khandelwal

Jaideep Khandelwal


Cost Optimization: Not my infrastructure, but my architecture is the culprit.

Submitted Oct 21, 2023

Come economic winter and as Infrastructure engineer your calendar is booked for multiple meetings/calls titled “Optimising Cloud Cost”. I am sure it sounds familiar. Everyone in the engineering teams prioritises cutting the cloud cost. But this is often a reactive and partial approach.
As an observation, we only optimise what is visible to us and pluck low-hanging fruits. What we often need to address are the issues with our architecture. Look into the architecture to consider the cost of other factors like security as first class, cost of scaling, and cost of over-engineering. If we focus on fixing them, the infrastructure cost reduction becomes a by-product. Eventually, it also leads to more predictable costs for your infrastructure.

This talk focuses on why architecture should not be made from Ivory Towers but more realistic to your business to keep the infrastructure cost in check. During this talk, I will touch upon the hidden costs often overlooked and try to explain them with examples and stories. We divide the cost into two categories: direct cost and indirect cost.

Direct cost:

  • Cost of optimisation for scale, used by none: As engineers, everyone wants to solve for scale. We built and optimised it for scale, with zero paying customers. Add more components to the fantastic architecture, which is sadly used by none.

  • Cost of not understanding the workload: Without understanding the workload, over-provisioning, auto-scaling horizontally or vertically without data points.

  • Cost of no signals, but all noise: Just because we have metrics, traces, and logs does not mean we will always use them. Example:

    • Sending metrics with high cardinality does not improve your observability but increases your cost.
    • No guard rails at your central logging infrastructure, which increases your storage, computing, and network.

Indirect cost:

  • Cost of no collaboration: When product engineering teams and infrastructure teams do not collaborate and build architectures in silos.

  • Cost of shiny tool syndrome - Introducing a “shiny new database” excites you because a cool company has solved when they reached a specific scale. The cost of your infrastructure will undoubtedly increase, but the engineering team effort required will be massive for a minimal gain.

  • Cost of overlooking security and compliance: After all the engineering effort, the product that runs on a particular infrastructure does not follow good practices. Example:

    • Running components in the public network.
    • No VPN for the internal tools like logging infrastructure or self-hosted CI/CD.
    • Secret keys spread all across the application.

    The cost is your reputation which trickles to your sales team and the inability to convert leads. Also, the cost to plan and move your stateless/stateful components.

  • Cost of heterogeneity: Multiple ways of doing one thing can exist. Some of the costs we should consider are maintenance and vendor lock-ins, which can be hard to quantify at times. Example:

    • Running a similar workload on Kubernetes and running server-less functions on the cloud.

Why should you attend this talk?

If you are a product engineer or work as infrastructure/platform engineer this talk should help, some of the key takeaways are:

  • Understand the hidden factors for cloud cost optimization. How to treat it as continuous activity instead of one time effort.
  • Cloud cost optimization cannot be done in isolation. It is a joint effort between product engineers and infrastructure engineers. More empathy across teams :-).
  • Guidelines that can help make decisions between self-managed or hosted solutions.


{{ 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