Rootconf Delhi edition

On network engineering, infrastructure automation and DevOps

Strongly consistent centralized Document Service with eventual consistent Search Store

Submitted by Aman Bansal (@aman-bansal) on Oct 27, 2019

Section: Crisp talk (20 mins) Category: Distributed systems Status: Rejected

Abstract

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

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.

Links

Comments

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

{{ gettext('You need to be a participant to comment.') }}

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

{{ errorMsg }}