InfoQ Homepage Presentations Scalable Internet Architectures
Scalable Internet Architectures
Summary
Theo Schlossnagle presents several architectural design principles useful for building scalable systems starting from the networking up to the application layer.
Bio
Theo Schlossnagle is the author of Scalable Internet Architectures (SAMS) and a frequent speaker at worldwide IT conferences. He was the Principal Architect of the Momentum MTA, a new email system. Theo is a member of the IEEE and a senior member of the ACM. He serves on the editorial board of the ACM’s Queue Magazine. You can follow Theo on Twitter as @postwait.
About the conference
Software is changing the world; QCon aims to empower software development by facilitating the spread of knowledge and innovation in the enterprise software development community; to achieve this, QCon is organized as a practitioner-driven conference designed for people influencing innovation in their teams: team leads, architects, project managers, engineering directors.
Community comments
Knuth's quote
by Jeff Hain,
Knuth's quote
by Jeff Hain,
Your message is awaiting moderation. Thank you for participating in the discussion.
+1 on Knuth's "premature optimization is the root of all evil":
"Everytime an engineer writes crappy code, this comes out of their mouth next. (...) So, next time someone uses the first quote, you can punch him in the face, and give him the rest of it." (30m20)
Adding more about it, from
www.bluebytesoftware.com/blog/2010/09/06/ThePre...
"I have heard the "premature optimization is the root of all evil" statement used by programmers of varying experience at every stage of the software lifecycle, to defend all sorts of choices, ranging from poor architectures, to gratuitous memory allocations, to inappropriate choices of data structures and algorithms, to complete disregard for variable latency in latency-sensitive situations, among others.
Mostly this quip is used defend sloppy decision-making, or to justify the indefinite deferral of decision-making. In other words, laziness.
(...)
First and foremost, you really ought to understand what order of magnitude matters for each line of code you write. (...) To be successful at this, you’ll need to know what things cost. If you don’t know what things cost, you’re just flailing in the dark, hoping to get lucky."