Rootconf is India’s principal conference where systems and operations engineers share real world knowledge about building resilient and scalable systems.
We are now accepting submissions for our next edition which will take place in Bangalore 14-15 April 2016.
The theme for this edition will be learning from failure. We are keen to explore how devops think about failure when designing, building and scaling their systems. We invite presentations related to failure in database systems, servers and network infrastructure.
We encourage presentations that relate to failure not only in terms of avoidance but also in terms of mitigation and education. How do we decide which parts of our systems cannot fail? What measures do we take to mitigate failure when it does inevitably happen? And most importantly: what lessons can be learned from failure?
This year’s edition spans two days of hands-on workshops and conference. We are inviting proposals for:
- Full-length 40 minute talks.
- Crisp 15-minute talks.
- Sponsored sessions, 15 minute duration (limited slots available; subject to editorial scrutiny and approval).
- Hands-on Workshop sessions, 3 and 6 hour duration.
Proposals will be filtered and shortlisted by an Editorial Panel. We urge you to add links to videos / slide decks when submitting proposals. This will help us understand your past speaking experience. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals.
We expect you to submit an outline of your proposed talk – either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.
We will notify you about the status of your proposal within three weeks of submission.
Selected speakers must participate in one-two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.
There is only one speaker per session. Entry is free for selected speakers. As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek will provide a grant to cover part of your travel and accommodation in Bangalore. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer).
Commitment to open source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.
Key dates and deadlines
- Paper submission deadline: 31 January 2016
- Schedule announcement: 29 February 2016
- Conference dates: 14-15 April 2016
Rootconf will be held at the MLR Convention Centre, J P Nagar.
For more information about speaking proposals, tickets and sponsorships, contact firstname.lastname@example.org or call +91-7676332020.
Buckle up for any disaster with your database
The objective is to share the experience of disaster recovery in different situations for the database servers. I would be taking PostgreSQL as the main example, but most of them, except PostgreSQL specific tools or commands, apply for all databases.
‘Data’ is the most valuable component for any organization. As the owner for managing the database servers, we have to plan and be ready for any kind of disaster recovery, whether it’s a recovery of a single row from a table or complete cluster data.
My talk’s outstructure will look like as follow:
Different disaster scenarios
It will include different scenarios in which any kind of disaster from a small scale to a large scale can happen.
It will include some real examples of prodcution environment.
Different mechanism for being ready for disaster recovery
It will include what are different mechanism and pre planning for disaster recovery.
It includes all corner cases planning like a disaster situation due to manual mistake, any application bug or any big less probable scenario.
Different tools/mechanism that can be used.
The Do’s and Dont’s at the time of disaster situation
- Some basic sanity that one need to follow and not to follow. It will be both technical and non technical situations.
You should understand some basics of RDBMS.
I am currently working at InMobi as ‘Tech Lead -Production and Infrastructure Engineering’. I have been with the database engineering team for more than 6 years. Database applications and operations solution has been my primary area, which includes RDBMS, Data ware house, NoSQL. Other than databases; scripting, automations, deployments, tech talks have been my work area.
In my free time, I love reading (non technical stuffs) and spending time with my family:-) .