Rootconf is a platform to discuss real-world problems around Site Reliability Engineering (SRE), network management, cloud, infrastructure, distributed systems and DevSecOps.
Participants, speakers and reviewers who attend/contribute to Rootconf include:
- DevOps engineers
- Site Reliability Engineers (SRE)
- Security and DevSecOps professionals
- Software engineers
- Network engineers
The Hyderabad edition will bring new ideas, new community members and novel problem-solving approaches around:
- Systems engineering
- Distributed systems, especially problems that Indian companies are solving
Rootconf Hyderabad will be held on 16 November, 2019. The event venue will be announced shortly. Workshops will be held before and after the conference.
To know more about Rootconf, check out the following resources:
For information about the event, tickets (bulk discounts automatically apply on 5+ and 10+ tickets) and speaking, call Rootconf on 7676332020 or write to email@example.com
Great Expectations : Observability in asynchronous systems using temporal logic
by AdityaBasic flows in Asynchronous systems Challenges of monitoring asynchronous systems What is an expectation ? Parts of an expectation Basics of a state machine Basics of linear temporal logic How it all fits together Instrumenting the Expectation engine - with a description of components and reason for choice Variations of the basic expectation in context with real world examples Success stories where other monitoring systems would be insufficient Challenges faced and how we overcame them Future flows
Shatabdi - P2P layer for fast object distribution
by Ankur JainMotivation for fast object distribution Overview of bittorrent protocol Goals for a torrent-based distribution layer Design, architecture and functional flows of Shatabdi Indexing store and leader election using etcd Achieving HA for torrent tracker Comparison of open-source torrent clients API contracts of daemon binary which abstracts http and p2p downloads Performance tuning of QBittorrent client and uncharted territories of libtorrent Benchmarking container deployments powered by Shatabdi
Dashboards as Code
by Sanooj MananghatHow to make use of the world’s top technology to build your Dashboards with more robustness without tech debt. Why dashboards? Existing methods of maintaining dashboards. At current scale of using dashbaords and alerts, difficult to scale without proper automation. Consistency issues Dashboards can be easily edited by any layman resulting in consistency issues. Alerts disbaled during maintenance/deployment leading to undetected incidents. Automate challenges 90% of the dashboards are still being created/modified by clicking on the UI. Manual configuration can lead to errors. No history. No rollbacks possible during an unintended modification. Solution 1: Git Will solve Consistency issues and maintains history. It still cannot validate the huge json files, manual review is required. Automation of stored json files to dashboards are still not solved. Solution 2: Git + Terraform Terraform providers/plugins. - Automating dashboards using terrafrom providers. Manage state, conflicts, support validation, rollback, everything with zero tech debt. Add value to your skills. Demo of how to create a dashboard with Terraform and Grafana
Deploying and Managing CSP - the Browser-side Firewall
by Lavakumar KuppanIntroduction to client-side Data Exfiltration attacks Introduction to Content-Security Policy Content Security Policy to prevent Data Exfiltration attacks ○ What is possible ○ What are the limitations How to design and deploy CSP to detect/prevent Data Exfiltration attacks How to monitor policy violations and alerts
Designing microservices around your data design
by Jambunathan V RIntroduction Usecases Definition Image Classification Product Recommendations AI Stylist Architecture and workflow of each usecase Merge the workflows into single architecture Core Platform Architecture v0.1 Design Considerations Latency & throughput Deployment strategy datastore design Core platform architecture v0.2 Learnings from our design Case study: Microservice Registry Problem statement Architecture Config change for single service Config change between microservices Questions ?