Hi I'm Vinay, a curious DevOps Engineer with ~5 years of experience who loves to solve problems & help others. Ask Me Anything!

github logo Updated on ・1 min read

Hi everyone! I'm Vinay Hegde, a DevOps Engineer with ~5 years of hands-on expertise in deploying, scaling & troubleshooting production applications on infrastructure distributed across diverse cloud / co-located environments to ensure high availability.


If you have any questions about SysAdmin / SRE / DevOps, blogging, career tips, side projects or anything else - feel free to ask away!

twitter logo DISCUSS (10)
markdown guide
 

Hi Vinay, welcome to dev.together!

I'm curious to know about your experience implementing the SRE philosophy? I've just finished reading the Google SRE book, but how to start with actual on-ground implementation still escapes me.

 

Thanks for the bonhomie, Ayush! The Google SRE Book is indeed a Gem for anyone looking to broaden their know-how on reliability.

You could start with this post I made purely out of my experience

Hoping it gives you enough clarity to kick-start your implementation, cheers!

 
 

Could you be a bit more specific on what exactly in AWS?

 

Just in general, I suppose. I don't have any particular questions. For example someone reccomended that I use aurora instead of RDS for speed (although I looked into that and couldn't find out what exactly made it faster)

Before implementing any service especially cloud-based, a handy approach is to analyze one's own use-case, implement a small PoC & go for self benchmarking to see what fits better.

Here's a guide that should help you begin comparison between RDS & Aurora

 

In your opinion, what are things that every developer (no matter if FrontEnd, BackEnd or DevOps) should know?

 

Great question Louis, really appreciate it. Here's some of my pointers on it:

  1. Always ask questions, especially the why on something has to be done before beginning work. This will not only give you more perspective but also help you avoid becoming mechanical.

  2. Focus on learning things 1 at a time to avoid confusion, frustration and burnout.

  3. Invest time in activities such as attending Meetups, Conferences, Conducting Interviews (My recent learning having a tremendous impact), Blogging (Both personal & professional of wherever you're currently employed). The vibe of such things is infectious!

  4. Focus on remaining calm since it'll power you to be logical & prove useful when debugging issues.

  5. Lastly, be humble enough to realize someone with lesser experience & exposure than you might be much smarter. Connect with them to improve your shortcomings.

 

Hi Vinay,
I've been curious about Docker. I can't figure out if Docker is not Virtual Machine, then why it needs Hyper-visor to run ? Hyper-v is a virtual machine supporting hardware, isn't it ?

 

Docker doesn't need hypervisor to run but relies on the Host OS for its functionality.

This is because Docker Containers consist of only essential binaries & dependencies to be executed.

By that definition, many containers of the same application can share the same OS kernel & run independently.

Hypervisor is an interface used by VM OSes to work with hardware.

Hoping this helps!

Classic DEV Post from Apr 23

The Amazing Secret to Crafting Conference Submissions that Don't Suck

How to write a quality submission that might not get rejected.

Vinay Hegde profile image
Site Reliability Engineer with 4.9+ years of experience. Otherwise an avid artist, reader, cine-phile & football fan. Looking forward to connect with everyone :)