About Rootconf 2018 and who should attend:
Rootconf is India’s best conference on DevOps, SRE and IT infrastructure. Rootconf attracts systems and operations engineers to share real-world knowledge about building reliable systems.
The 2018 edition is a single track conference. Day 1 – 10 May – features talks on security. Colin Charles (chief evangelist at Percona Foundation), Pukhraj Singh (former national cybersecurity manager at UIDAI), Shamim Reza (open source enthusiast), Alisha Gurung (network engineer at Bhutan Telecom) and Derick Thomas (former network engineer at VSNL and Airtel Bharti) will touch on important aspects of infrastructure, database, network and enterprise security.
Day 2 – 11 May – is filled with case studies and stories about legacy code, immutable infrastructure, root-cause analysis, handling dependencies and monitoring. Talks from Exotel, Kayako, Intuit, Helpshift, Digital Ocean, among others, will help you evaluate DevOps tools and architecture patterns.
If you are a:
- DevOps programmer
- Systems engineer
- VP of engineering
- IT manager
you should attend Rootconf.
Birds Of Feather (BOF) sessions at Rootconf 2018 will cover the following topics:
- DevSec Ops
- Microservices - tooling, architecture, costs and culture
- Mistakes that startups make when planning infrastructure
- Handling technical debt
- How to plan a container strategy for your organization
- Evaluating AWS for scale
- Future of DevOps
Rootconf is a conference for practitioners, by practitioners.
The call for proposals is closed. If you are interested in speaking at Rootconf events in 2018, submit a proposal here: rootconf.talkfunnel.com/rootconf-round-the-year-2018/
NIMHANS Convention Centre, Lakkasandra, Hombegowda Nagar, Bengaluru, Karnataka 560029.
Schedule, event details and tickets: https://rootconf.in/2018
For more information about Rootconf, sponsorships, outstation events, contact email@example.com or call 7676332020.
Production Report - Using Apache Flink as a microservice for stateful asynchronous processing
This talk highlights why we chose flink as a microservice for stateful asynchronous event processing and challenges we faced in production, how we solved those and recommendations for productionization of the applications using Apache flink.
- Architecture pattern of using Flink/similar platform as a microservice for statuful async event processing
- Flink fault tolerance concepts in-depth understanding
- Production issues/challenges faced and insights on how to solve (& also prevent) them
Basic understanding of stream processing will be an advantage.
- Brief summary of what is flink and important terminologies
- Flink as a microservice for asynchronous stateful event stream processing
- Challenges in doing it in a conventional way
- Prerequisite concepts
- Fault tolerance and checkpointing
- Scalable partitioned state
- State Backend - Rocksdb
- Asynchronous checkpointing details
- Production Experiences
- Flink taskmanager failover time tuning
- Failure detection mechanism
- Tuning Akka Deathwatch
- How state leaks happen and how to prevent and monitor them
- How to clear old state (result of state leak) of running system, without taking downtime
- How state size and checkpointing can cause processing delays and how to tune it
- Recommendations & Summary
Software architect at Helpshift. Have worked on streaming processing,various backend architectures and end-end data pipelines before. Have a good understanding of systems side of software as well. More details can be found on https://www.linkedin.com/in/jagadish-bihani-1335a04a/