Rootconf Delhi edition
Rootconf For members

Rootconf Delhi edition

On network engineering, infrastructure automation and DevOps

Tickets

Loading…

Rootconf is a platform to discuss real-world problems around Site Reliability Engineering (SRE), DevOps for data engineering platforms, evaluating and adopting technologies such as Kubernetes and containers, and DevSecOps.

Rootconf Delhi edition will be held on 18 January 2020 at the India International Centre (IIC).

Speakers from Flipkart, Hotstar, MindTickle, Red Hat and Naukri.com will discuss the following topics:

  1. Scaling and engineering challenges from Hotstar’s and Flipkart’s experiences.
  2. Data store choices.
  3. Kubernetes and K8s -- when to choose what and why?
  4. DevSecOps

##Who should attend Rootconf:

  1. Operations engineers
  2. DevOps programmers
  3. Software developers
  4. SRE
  5. Tech leads

To know more about Rootconf, check the following resources:

  1. hasgeek.com/rootconf
  2. https://www.youtube.com/channel/UCDHao9FxNRHw1VyLuGXI_rA

#Sponsors:

Click here to view the Sponsorship Deck.
Email sales@hasgeek.com for bulk ticket purchases, and sponsoring the above Rootconf Series.


Rootconf Delhi sponsors:


#Silver Sponsor

Verizon

#Bronze Sponsors

upcloud SumoLogic

#Community Partner

IFF Null Delhi

For information about the event, tickets (bulk discounts automatically apply on 5+ and 10+ tickets) and speaking, call Rootconf on 7676332020 or write to info@hasgeek.com.

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Vinod Kumaar Ramakrishnan

@vinodkr

If you do CD on cloud, from day 1 your project is a maintenance project

Submitted Nov 24, 2019

Gone are the days when people used to think a project has distinct phases of development and maintenance. Even agile teams have a development window during which the processes are different from the ones followed after a first release. I have observed the most successful ones were the ones which treat every project as a maintenance project from day one. This means building security, monitoring, log aggregation, infra into the design; in simple terms a lot of left shift in the approach when going for cloud. We will look at the absolute must to architect an application for cloud so that going live is just a ribbon cutting exercise.

Outline

Oops moments
Why was it a Oops and its causes
The DOs to a stress free release

Requirements

N/A

Speaker bio

Vinod is an architect with ThoughtWorks India Markets. He has a special interest in workplace efficiency, learning organization and clean code. He plays the role of a trainer when required and designs course work for new joiners.

Comments

{{ 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 community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more