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

Amit Patil

@apatil3

Transformation from zero to shipping Production code daily

Submitted Apr 15, 2019

The advent of DevOps has revamped the traditional application development process in a drastic way. The software industry is rapidly seeing the value of moving away from conventional ways of releasing code to more matured workflows enabling them to move faster.
We have seen a big transformation on how code is build, developed and executed. Journey from manual builds to script based deployment, script based to CI, CI to CD and so on. This change has brought a big paradigm shift no how the code is treated. Everything codified with no manual intervention is the new mantra in todays culture of application development. Infrastructure as Code hence has become the cornerstone to allow for the speed that DevOps demands and the management of multiple versions of multiple environments, to handle the CI builds being spun out by development. Infrastructure as Code (IaC) is a key element of DevOps philosophy with benefits for both development and operation teams.

What transpired this change and How this has benefitted the overall development lifecycle.?

Outline

What transpired this change
How DevOps/Cloud is changing on “how we ship code”.
How this has benefitted the overall development lifecycle.
What are different kinds of workflows?

Speaker bio

Amit Patil is a Sr.Manager in Sapient’s DevOps and Cloud COE practice with 15+ years of industry experience in managing large complex infrastructure projects and delivering enterprise level project on Cloud, DevOps and Continuous Delivery framework across infrastructure space.
He specializes in digital transformation program with strong knowledge in managing and delivering Cloud and DevOps projects.

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