Call for round the year submissions for Rootconf in 2020

Call for round the year submissions for Rootconf in 2020

Submit a proposal at any time in the year on DevOps, infrastructure security, cloud, and distributed systems. We will find you a suitable opportunity to share your work.

Make a submission

Accepting submissions till 31 Dec 2020, 12:00 PM

About Rootconf:

Rootconf is HasGeek’s annual conference – and now a growing community – around DevOps, systems engineering, DevSecOps, security and cloud. The annual Rootconf conference takes place in May each year, with the exception of 2019 when the conference will be held in June.

Besides the annual conference, we also run meetups, one-off public lectures, debates and open houses on DevOps, systems engineering, distributed systems, legacy infrastructure, and topics related to Rootconf.

This is the place to submit proposals for your work, and get them peer reviewed by practitioners from the community.

Topics for submission:

We seek proposals – for short and long talks, as well as workshops and tutorials – on the following topics:

  1. Case studies of shift from batch processing to stream processing
  2. Real-life examples of service discovery
  3. Case studies on move from monolith to service-oriented architecture
  4. Micro-services
  5. Network security
  6. Monitoring, logging and alerting – running small-scale and large-scale systems
  7. Cloud architecture – implementations and lessons learned
  8. Optimizing infrastructure
  9. SRE
  10. Immutable infrastructure
  11. Aligning people and teams with infrastructure at scale
  12. Security for infrastructure

Contact us:

If you have questions/queries, write to us on rootconf.editorial@hasgeek.com

Hosted by

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

Barani Subramanian

@baranis30

Firebolt: Asynchronous Processing System for Payments

Submitted Feb 21, 2019

At Flipkart Payments we build robust systems to provide a smooth experience to customers. In this session, we’ll talk about how we levarage aysnchronous processing to improve the performance of the payment systems which are pivotal to Flipkart. We’ll go over the details of the streaming pipelines we built using MySQL, Hbase, Kafka and Storm, and the customization we did over them. We’ll share our journey and learnings for the same.

Outline

Outline

Firebolt: Async Processing for Payments
   - System functionlity and components
   - High level architecture

Why Async Processing
   - Performance impact of sync processing in user live path
   - Customizations for high throughput

Resilient Streaming
   - Avoiding Head of Line blocking through sidelines
   - Automatic sideline management

Reliable Pipelines
   - Transactional event processing with high availability
   - Achieving at-least once in-order delivery for database relayers
   - Replay capability with GTID
   - Monitoring the system

Speaker bio

Barani Subramanian works as a software developer in Flipkart. She has 4+ years of experience in Sales and Payments domains.
She likes to read books in free time.

Slides

https://docs.google.com/presentation/d/1yeaAJGDzHy86fVuQj8Tu7DhaAtm6m8yLzZMV9GRf2KQ/edit#slide=id.p

Comments

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

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

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Make a submission

Accepting submissions till 31 Dec 2020, 12:00 PM

Hosted by

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