Rootconf 2019

Rootconf 2019

On infrastructure security, DevOps and distributed systems.

About Rootconf 2019:

The seventh edition of Rootconf is a two-track conference with:

  1. Security talks and tutorials in audi 1 and 2 on 21 June.
  2. Talks on DevOps, distributed systems and SRE in audi 1 and audi 2 on 22 June.

Topics and schedule:

View full schedule here:

Rootconf 2019 includes talks and Birds of Feather (BOF) sessions on:

  1. OSINT and its applications
  2. Key management, encryption and its costs
  3. Running a bug bounty programme in your organization
  4. PolarDB architecture as Cloud Native Architecture, developed by Alibaba Cloud
  5. Vitess
  6. SRE and running distributed teams
  7. Routing security
  8. Log analytics
  9. Enabling SRE via automated feedback loops
  10. TOR for DevOps

Who should attend Rootconf?

  1. DevOps programmers
  2. DevOps leads
  3. Systems engineers
  4. Infrastructure security professionals and experts
  5. DevSecOps teams
  6. Cloud service providers
  7. Companies with heavy cloud usage
  8. Providers of the pieces on which an organization’s IT infrastructure runs – monitoring, log management, alerting, etc
  9. Organizations dealing with large network systems where data must be protected
  10. VPs of engineering
  11. Engineering managers looking to optimize infrastructure and teams

For information about Rootconf and bulk ticket purchases, contact or call 7676332020. Only community sponsorships available.

Rootconf 2019 sponsors:

Platinum Sponsor


Gold Sponsors

Atlassian Endurance Trusting Social

Silver Sponsors

Digital Ocean GO-JEK Paytm

Bronze Sponsors

MySQL sumo logic upcloud
platform sh nilenso CloudSEK

Exhibition Sponsor

FreeBSD Foundation

Community Sponsors

Ansible PlanetScale

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more

Guruprasad GV


Patterns for designing stateful microservices at scale

Submitted Jan 13, 2019

Age old wisdom says - “make your services stateless”. There is a lot of merit in that.
While we strive to make our services stateless, have you considered the cost you are paying for this. In this session, we will challenge the norms, dive into use cases for making your microservice stateful, how does it impact user performance, cost, and fault tolerance. We will walk through scenarios that this starts to become enticing.


What is a microservice, and what is a stateful microservice?

Our Use case
- A Game Server
- Consistency Requirements
- Scale Requirements
- User Performance
- Fault Tolerance

Event Sourced Pattern

Managing State
- In Memory/ Off HeapSnapshot
- External Snapshot
- Dealing with failures
- Managing State Sharding
- Managing State Movement

- Consistency Vs Availability
- Building for Always On
- Scaling

Building for Fault Tolerance
- Minimize Blast Radius
- Recovery aspects

Propagating State to downstream
- Absolutes
- Deltas
- Change Logs
- Batches
- Consumer Options

Techs that might be well suited for this.
- Actor Models
- Erlang(?)

- Why would you want to consider stateful microservices
- Hard to manage but they can be done.
- There are real-world benefits

Why would you consider
- Other Use Cases.


Have a basic understanding of microservices, and undertand some challenges of operating them at scale.

Speaker bio

I am Architect at Moonfrog. In the last 14 years as an engineer, I have mostly been relishing solving technology challenges in various domains: compilers, client designs, distributed systems, big data systems etc. Now exploring technology in gaming at its best in Moonfrog for the past 1 year.



{{ 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 forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more