0:00 / 0:00
#microservices#technicaldebt#systemdesign
Microservices are Technical Debt
NeetCodeIO
352K subscribers • 1 video on Hallway
- Recommended by 2 people: 1 on Lobsters and 1 in engineering communities.
- Presented by Navdeep Singh, creator of NeetCode
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
1.1M views2 years ago2 recommendations
Software designDistributed systemsMicroservices and monolithsSoftware architecture
Navdeep Singh explains the hidden costs of microservices, how they impact developer productivity, and why they often act as technical debt.
🚀 neetcode.io - A better way to prepare for coding interviews 🧑💼 LinkedIn: linkedin.com/in/navdeep-singh-3aaa14161/ 🐦 Twitter: twitter.com/neetcode1 ⭐ BLIND-75 PLAYLIST: youtube.com/watch?v=KLlXCFG5TnA&list=PLot-Xpze53ldVwtstag2TL… - Intro - Why Microservices? - Developer Productivity - Microservices are tech debt - Was it worth it for Doordash - Programming Principles - Hot takes - Programming Advice For sponsorship inquiries please reach out to mail@neetcode.io #neetcode #leetcode #pythonWhy it's here
2 people recommend thisWhat people say. Recommended for engineers considering breaking a monolith into microservices.
u/Defualtin r/softwarearchitecture • Recommends
On “Lead Architect wants to break our monolith into 47 microservices in 6 months, is this insane?”
Microservices are technical debt link to this video
u/askaiserin r/dotnet • Mentions
On “How do do you deal with 100+ microservices in production?”
You'll get something out of decoupling and breaking these "big ass services", but at a cost that you'll pay later. [video