Forgot your password?
typodupeerror

Comment: Re:Don't mix the vendor networking gear? (Score 1) 54

by phreakocious (#37554756) Attached to: Book Review: Scalability Rules
Your scenario (multi-vendor conference call, urgency of resolution) implies a problem in a production environment. When architectures are fully end-to-end tested before being put into production, problems like these are eliminated long before solutions like complete hardware replacement are palatable to the business people signing the checks. In my experience, these are best practices and extend to things like configuration management and code upgrades for everything from access switches to firewalls, load balancers, etc.

Comment: Re:Don't mix the vendor networking gear? (Score 1) 54

by phreakocious (#37552322) Attached to: Book Review: Scalability Rules
I'm happy to hear that you've found a strategy that works for you. There are many functional infrastructures out there that don't follow this model, and they are doing very well. The entire internet routing infrastructure is heterogeneous, for one example. I just think it's disingenuous to suggest that fundamental incompatibilities between major players with protocols like BGP and OSPF occur so often. Which equipment vendor do you work for?

Comment: Re:Don't mix the vendor networking gear? (Score 1) 54

by phreakocious (#37548354) Attached to: Book Review: Scalability Rules
Sorry, but no. I've been in the industry for over 10 years, and it's rare to experience these types of problems. Consumer-grade equipment is notorious for this type of thing, but it's much less common with a major vendor with a reputation to protect. Single vendor rarely means best of breed.

...when fits of creativity run strong, more than one programmer or writer has been known to abandon the desktop for the more spacious floor. - Fred Brooks, Jr.

Working...