Artwork

Content provided by Utsav Shah. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Utsav Shah or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Software at Scale 36 - Decomposing Monoliths with Ganesh Datta

43:28
 
Share
 

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on August 05, 2024 18:25 (11d ago)

What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

Manage episode 306167849 series 2899471
Content provided by Utsav Shah. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Utsav Shah or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Ganesh Datta is the CTO and co-founder of Cortex, a microservice management platform.

Apple Podcasts | Spotify | Google Podcasts

We continue the age-old monolith/microservice debate and dig into why companies seem to like services so much (I’m generally cautious about such migrations). Ganesh has a ton of insights into developer productivity and tooling to make engineering teams successful that we dive into.

Highlights

00:00 - Why solve the service management problem?

06:00 - When to drive a monolith → service migration? What inflection points should one think about to make that decision?

08:30 - What would Ganesh do his next service migration?

10:30 - What tools are useful when migrating to services?

12:00 - Standardizing infrastructure to facilitate migrations. How much to standardize (à la Google), to letting team make their own decisions (à la Amazon)?

17:30 - How does a tool like Cortex help with these problems?

21:30 - How opinionated should such tools be? How much user education is part of building such tools?

27:00 - What are the key cultural components of successful engineering teams?

31:00 - Tactically, what does good service management look like today?

37:00 - What’s the cost/benefit ratio of shipping an on-prem product vs. a SaaS tool?

41:30 - What would your advice be for the next software engineer embarking on their monolith → microservice migration?


This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.softwareatscale.dev
  continue reading

60 episodes

Artwork
iconShare
 

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on August 05, 2024 18:25 (11d ago)

What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

Manage episode 306167849 series 2899471
Content provided by Utsav Shah. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Utsav Shah or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Ganesh Datta is the CTO and co-founder of Cortex, a microservice management platform.

Apple Podcasts | Spotify | Google Podcasts

We continue the age-old monolith/microservice debate and dig into why companies seem to like services so much (I’m generally cautious about such migrations). Ganesh has a ton of insights into developer productivity and tooling to make engineering teams successful that we dive into.

Highlights

00:00 - Why solve the service management problem?

06:00 - When to drive a monolith → service migration? What inflection points should one think about to make that decision?

08:30 - What would Ganesh do his next service migration?

10:30 - What tools are useful when migrating to services?

12:00 - Standardizing infrastructure to facilitate migrations. How much to standardize (à la Google), to letting team make their own decisions (à la Amazon)?

17:30 - How does a tool like Cortex help with these problems?

21:30 - How opinionated should such tools be? How much user education is part of building such tools?

27:00 - What are the key cultural components of successful engineering teams?

31:00 - Tactically, what does good service management look like today?

37:00 - What’s the cost/benefit ratio of shipping an on-prem product vs. a SaaS tool?

41:30 - What would your advice be for the next software engineer embarking on their monolith → microservice migration?


This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.softwareatscale.dev
  continue reading

60 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide