flâneur

Path Dependence in Telecoms and Technology | AWS Cloud Enterprise Strategy Blog

aws.amazon.com · 1,160 words · saved by 1 readers

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies. If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.” Essential cookies are necessary to provide our site and services and cannot be deactivated. They are usually set in response to your actions on the site, such as setting your privacy preferences, signing in, or filling in forms. Performance cookies provide anonymous statistics about how customers navigate our site so we can improve sit

Path Dependence in Telecoms and Technology In this guest post John Naylon, AWS Principal SA for Telecoms, talks about path dependence—the idea that solutions are sometimes subject to historical accident—and why the AWS notion of “reinvention” in the cloud is a possible solution. While his examples are drawn from the telecom industry, the point is an important one for all of us. — Mark By John Naylon, Principal Solutions Architect for Telecoms at AWS Path dependence is the name for the phenomenon of a de facto standard enduring, not because it represents a currently optimal choice, but because

saved by

related reading