Highload at a University: Idealism, Calculating Management or Empty Hopes
summary
Examines common misconceptions teams from regular software projects bring to building high-load systems, naming components like databases and ElasticSearch. Argues that developers, managers and ops often assume synchronous calls and unprotected integration points are fine, and discusses the need for joint responsibility and different engineering practices to avoid failures seen in production.
AI-written summary · about
chapters (4)
related talks
44mCurriculum for a Highload Guru
01mInterview
52mYour Brain on Software Development
49mLessons from a Project with a 2001 Commit
49mExtreme Professionalism - Software Craftsmanship.
21mDiamonds with Flaws: Examining the Pressures, Realities, and...
14mHow to Succeed with Your Software Project
42mThe Monster Coming Over The Hill