Rootconf Delhi edition
Rootconf For members

Rootconf Delhi edition

On network engineering, infrastructure automation and DevOps

Tickets

Loading…

Rootconf is a platform to discuss real-world problems around Site Reliability Engineering (SRE), DevOps for data engineering platforms, evaluating and adopting technologies such as Kubernetes and containers, and DevSecOps.

Rootconf Delhi edition will be held on 18 January 2020 at the India International Centre (IIC).

Speakers from Flipkart, Hotstar, MindTickle, Red Hat and Naukri.com will discuss the following topics:

  1. Scaling and engineering challenges from Hotstar’s and Flipkart’s experiences.
  2. Data store choices.
  3. Kubernetes and K8s -- when to choose what and why?
  4. DevSecOps

##Who should attend Rootconf:

  1. Operations engineers
  2. DevOps programmers
  3. Software developers
  4. SRE
  5. Tech leads

To know more about Rootconf, check the following resources:

  1. hasgeek.com/rootconf
  2. https://www.youtube.com/channel/UCDHao9FxNRHw1VyLuGXI_rA

#Sponsors:

Click here to view the Sponsorship Deck.
Email sales@hasgeek.com for bulk ticket purchases, and sponsoring the above Rootconf Series.


Rootconf Delhi sponsors:


#Silver Sponsor

Verizon

#Bronze Sponsors

upcloud SumoLogic

#Community Partner

IFF Null Delhi

For information about the event, tickets (bulk discounts automatically apply on 5+ and 10+ tickets) and speaking, call Rootconf on 7676332020 or write to info@hasgeek.com.

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

Aman Bansal

@aman_bansal

Strongly consistent centralized Document Service with eventual consistent Search Store

Submitted Oct 27, 2019

Organizations with multiple teams generally end up with different applications that manage it’s own database interactions. This approach would be fine at a smaller scale but as we move forward towards a large scale, the situation will become more error-prone. Because now each application needs to either deploy experts in each team or build expertise to make the data available, consistent and usable at all times. This leads to wastage of resources both in terms of computing as well as human. In addition to that, applications need to manage Disaster Recovery (DR), migrations (if needed), Recovery Time Objective (RTO) and Recovery Point Objective which all leads to inconsistencies. This talk is about our experience of how we solved this problem at Mindtickle. We developed a strongly consistent centralised document service and we believe it is worth sharing with the community.

Outline

https://docs.google.com/document/d/1XRCihGpvLDsQjnbqy9oYEhFigaCqSy2fkdZK0gGlOxM/edit?usp=sharing

Requirements

some development experience in client server applications

Speaker bio

Aman Bansal is a technology enthusiast who is lucky enough to hack on various projects at Mindtickle, Pune. Currently, he is part of the Infrastructure team which is developing a centralized database service solution.

Comments

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