Skip to content
0:00 / 0:00

#monolith#microservices#randyshoup

Why Most Apps Should Start as Monoliths – Randy Shoup Explains

Dev Tools Made Simple

25K subscribers • 12 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Randy Shoup, former engineering leader at Google, eBay, and Stitch Fix
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

4.7K views1 year ago2 recommendations

Software designDistributed systemsSoftware architectureMicroservices and monoliths

Randy Shoup explains why starting with a monolith is usually the right choice and when it actually makes sense to transition to microservices.

#SoftwareArchitecture #RandyShoup #MonolithVsMicroservices #Microservices #SoftwareEngineering #TechLeadership #SystemDesign #StartupTech #DevTalks Boost your coding skills by joining Scrimba: scrimba.com?via=DevToolsMadeSimple youtu.be/MjPoob7CYnY?si=aW0akyEUvzHhVRda In this clip, Randy Shoup—former engineering leader at Google, eBay, and Stitch Fix—breaks down why most software projects should start as monoliths. He explains the common misconceptions around microservices, and the point at which splitting your system actually makes architectural sense. Avoid premature complexity. Learn when scaling demands justify microservices—and when they don’t.

Why it's here

2 people recommend this

What people say. Recommended as a clear explanation of the monolith-first approach to software architecture.

u/MinimumMagician5302in r/softwarearchitecture • Recommends

Why Most Apps Should Start as Monoliths

u/MinimumMagician5302in r/scala • Recommends

Why Most Apps Should Start as Monoliths

u/South-Reception-1251in r/dotnet • Recommends

Why Most Apps Should Start as Monoliths