18-19 January 2019
Status: Accepting submissions

About Distributed Systems Conf

Managing and running large infrastructure systems requires work at the foundation – at the architecture level. Our goal with the Distributed Systems Conf is to:

  1. Facilitate meaningful interactions between systems engineers from Bangalore and across the world.
  2. Enable senior technologists and decision-makers in tech to evaluate approaches for building complex architecture.
  3. Build a community of senior technologists, systems engineers, VPs of technology and CTOs for peer-to-peer learning and sharing.

Topics to propose talks:

We are seeking case study talks on the following topics:

  1. Shift from batch processing to stream processing.
  2. Service discovery.
  3. Move from monolith to SOA-related case studies.

Audience and nature of talks to propose:

Distributed systems conference will bring together:

  1. Senior engineers
  2. Engineering managers
  3. Systems engineers
  4. Architects
  5. Tech leads
  6. VPs of technology
  7. CTOs

We will not accept how-to and introductory-level talks for Distributed Systems Conf. We are interested in discussing the “whys” and “approaches” rather than “how-to”


Distributed Systems Conf is a two-day with:

  1. Single track of talks in audi 1
  2. BOF sessions in BOF area
  3. Hands-on and strategy workshops before and after the conference

Dates and venue:

Date: 18 and 19 January
Venue: NIMHANS Convention Centre, Bangalore

Selection criteria:

The first filter for a proposal is whether the technology or solution you are referring to is open source or not. While the winter edition does not include talks on engineering, talks which advertise proprietary solutions will be considered under sponsored sessions category.

Note the following guidelines for sponsored talks:

  1. If the technology or solution is proprietary, and you want to speak about your proprietary solution to make a pitch to the audience, you should pick up a sponsored session. This involves paying for the speaking slot. Write to rootconf.editorial@hasgeek.com
  2. If the technology or solution is in the process of being open sourced, we will consider the talk only if the solution is open sourced at least three months before the conference.
  3. If your solution is closed source, you should consider proposing a talk explaining why you built it in the first place; what options did you consider (business-wise and technology-wise) before making the decision to develop the solution; or, what is your specific use case that left you without existing options and necessitated creating the in-house solution.

Selection criteria:

The criteria for selecting proposals, in the order of importance, are:

  1. Key insight or takeaway: what can you share with participants that will help them in their work and in thinking about analytics and the problem space?
  2. Structure of the talk and flow of content: a detailed outline – either as mind-map or draft slides or textual description – will help us understand the focus of the talk, and the clarity of your thought process.
  3. Ability to communicate succinctly, and how you engage with the audience. You must submit link to a two-minute preview video explaining what your talk is about, and what is the key takeaway for the audience.

No one submits the perfect proposal in the first instance. We therefore encourage you to:

  1. Submit your proposal early so that we have more time to iterate if the proposal has potential.
  2. Write to rootconf.editorial@hasgeek.com if you have questions about how to submit a talk.

Our editorial team helps potential speakers in honing their speaking skills, fine tuning and rehearsing content at least twice - before the main conference - and sharpening the focus of talks.

We only accept one speaker per talk. This is non-negotiable. Workshops may have more than one instructor.

How to submit a proposal (and increase your chances of getting selected):

The following pointers will help you in submitting a proposal:

  1. Focus on why, not how. Explain to participants why you made a business or engineering decision, or why you chose a particular approach to solving your problem.
  2. The journey is more important than the solution you may want to explain. We are interested in the journey, not the outcome alone. Share as much detail as possible about how you solved the problem. Glossing over details does not help participants grasp real insights.
  3. We do not accept how-to talks unless they demonstrate latest technology. If you are demonstrating new tech, show enough to motivate participants to explore the technology later.
  4. Similarly, we don’t accept talks on topics that have already been covered in the previous editions. If you are unsure about whether your proposal falls in this category, drop an email to: rootconf.editorial@hasgeek.com
  5. Content that can be read off the internet does not interest us. Our participants are keen to listen to use cases and experience stories that will help them in their practice.

To summarize, we do not accept talks that gloss over details or try to deliver high-level knowledge without covering depth. Talks have to be backed with real insights and experiences for the content to be useful to participants.

Passes and honorarium for speakers:

We pay an honorarium of Rs. 3,000 to each speaker and workshop instructor at the end of their talk/workshop. Confirmed speakers and instructors also get a pass to the conference. We do not provide free passes for speakers’ colleagues and spouses. Please do not ask us for this.

Travel grants for outstation speakers:

Travel grants are available for international and domestic speakers. We evaluate each case on its merits, giving preference to women, people of non-binary gender, and Africans. If you require a grant, request it when you submit your proposal in the field where you add your location. Distributed Systems Conf is funded through ticket purchases and sponsorships; travel grant budgets vary.

Last date for submitting proposals is 10 November 2018:

You must submit the following details along with your proposal, or within 10 days of submission:

  1. Draft slides, mind map or a textual description detailing the structure and content of your talk.
  2. Link to a self-recorded, two-minute preview video, where you explain what your talk is about, and the key takeaways for participants. This preview video helps conference editors understand the lucidity of your thoughts and how invested you are in presenting insights beyond the solution you have built, or your use case. Please note that the preview video should be submitted irrespective of whether you have spoken at past editions of Rootconf.
  3. If you submit a workshop proposal, you must specify the target audience for your workshop; duration; number of participants you can accommodate; pre-requisites for the workshop; link to GitHub repositories and a document showing the full workshop plan.

Contact details:

For more information about the conference, sponsorships, or any other information contact support@hasgeek.com or call 7676332020.

Propose a session