Rootconf Sessions

Rootconf Sessions

Presentations on DevOps and Dev-Oops

Make a submission

Accepting submissions till 31 Dec 2020, 11:59 PM

DevOps and Dev-Oops sessions cover:

  1. DevOps (obviously!)
  2. Databases and database disasters
  3. Distributed systems
  4. Systems engineering
  5. Infrastructure security
  6. War stories, failures and anti-patterns with running operations and infrastructure

Rootconf is a forum for:

  1. DevOps engineers
  2. Systems engineers
  3. Software engineers
  4. DevOps leads
  5. Infrastructure security professionals and experts
  6. Cloud service providers
  7. Providers of the pieces on which an organization’s IT infrastructure runs -- monitoring, log management, alerting, etc
  8. Engineering managers looking to optimize infrastructure and teams

Contact information: If you have questions, call Rootconf on 7676332020 or email rootconf.editorial@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

Kayalvizhi NoorulAmeen

Observable Microservices make Monitoring simple

Submitted Mar 24, 2020

Microservices is not a buzz word anymore. Every other organisation builds and deliver scalable, cloud native HA microservices. As a result of the simplicity (broken down microservices), the deployments and environments get complicated.

The complication: In microservices architecture, each and every request is served by one or more services like authentication service, notification service, inventory service etc…The requests can either be initiated by user or initiated by one of the other microservices in the system. Say something went wrong while serving a request.

Though there are umpteen number of tools SREs (Site Reliability Engineers) use in the cloud to monitor the microservices, new issues are always ‘unknown’. Every service would have been logging along the way to serve the request but is not an easy task to find all the relevant log messages for a particular request amongst millions of log messages. So, observability plays a key role here.
How Observability need to be adopted by enterprises as a coding culture so that the debugging & monitoring get soimplified

Outline

This session is targeted to cover how to make the services observable so that the monitoring becomes a piece of cake.
Demo: Making Microservices observable leveraging instrumentation tool
Target Audience: Microservices Adopters, DevOps Practitioners

Key Takeaways:

  1. What is observability in microservices world?
  2. The Pillars of Observability
  3. Tools & Techniques of Making Microservices Observable

Speaker bio

• Have 15 years of overall experience with over 5 years in architecting applications.
• Have a rich breadth of experience and good grip on application architectures considering non-functional areas like resiliency, fault-tolerance, performance, scalability, security, usability etc…and have clarity on what business needs and has ability to transform them to results
• Have passion in being the technology ambassador and coaching engineering excellence to junior engineers.
• Have given good number of technical talks in my current Organisation (Pramati)
• Have strong understanding of the Software design/architecture/data-backed-decision-making processes.
• Proficient in J2EE technologies in web development and has exposure to UI tech stack.
• Expertise in architecting and developing features for enterprise scale systems.
• Capable of coding and beginning an implementation to get a project off the ground

Slides

https://www.slideshare.net/secret/cgNYNTOtQ9Y85E

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, 11:59 PM

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