容量规划的艺术(英文影印版)
点击看大图基本信息
- 作者： (美)John Allspaw
- 丛书名： 南京东南大学出版社O'Reilly系列
- 出版社：东南大学出版社
- ISBN：9787564116521
- 上架时间：2009-7-27
- 出版日期：2009 年5月
- 开本：16开
- 页码：135
- 版次：1-1
- 所属分类：
计算机 > 软件工程及软件方法学 > 软件项目管理
内容简介回到顶部↑
使用和发展情况用于衡量web的成功与否，而基于web的公司生存与否取决于他们根据不断增长的需求扩展基础架构的能力。这本简单实用的指南将给予你需要用来测量、部署和管理w曲应用程序架构的知识和工具，以走在具有威胁的瓶颈和急速的增长前面。.
本书作者johnallspaw是图片共享网站flickr.com的运营工程经理。《容量规划的艺术》汲取了flickr的成长中很多作者的个人心得，并结合了作者在其他企业工作的同仁们的领悟。他们的第一手经验将会是你测算增长、预测趋势和做出符合成本效益的准备工作的有力方针。..
主题包括：
·使用高效的工具用于测量及部署
·存储、数据库和应用服务能力的分析和预测
·设计易于添加并测算其效能的架构
·处理突发流量峰值
·预测指数式和爆发式增长
·使虚拟化和像ec2这样的云服务与容量策略相适应
在本书中，作者allspaw利用多年的宝贵经验，从flickr的早期，当他不得不去管理任何具有成长型互动状态服务（web presence）的公司典型的成本与性能的平衡开始讲述。他在《容量规划的艺术》中给出的建议将会帮助你为突发的增长做好准备，对你会有非常大的帮助。...
本书作者johnallspaw是图片共享网站flickr.com的运营工程经理。《容量规划的艺术》汲取了flickr的成长中很多作者的个人心得，并结合了作者在其他企业工作的同仁们的领悟。他们的第一手经验将会是你测算增长、预测趋势和做出符合成本效益的准备工作的有力方针。..
主题包括：
·使用高效的工具用于测量及部署
·存储、数据库和应用服务能力的分析和预测
·设计易于添加并测算其效能的架构
·处理突发流量峰值
·预测指数式和爆发式增长
·使虚拟化和像ec2这样的云服务与容量策略相适应
在本书中，作者allspaw利用多年的宝贵经验，从flickr的早期，当他不得不去管理任何具有成长型互动状态服务（web presence）的公司典型的成本与性能的平衡开始讲述。他在《容量规划的艺术》中给出的建议将会帮助你为突发的增长做好准备，对你会有非常大的帮助。...
目录回到顶部↑
preface .
1 goals, issues, and processes in capacity planning
quick and dirty math
predictinr when your systems will fail
make your system stats tell stories
buyinr stuff: procurement is a process
performance and capacity: two different animals
the effects of social websites and open apis
2 setting goals for capacity
different kinds of requirements and measurements
architecture decisions
3 measurement: units of capacity
aspects of capacity tracking tools
applications of monitoring
api usare and its effect on capacity
examples and reality ..
summary
4 predicting trends
ridinr your waues
procurement
1 goals, issues, and processes in capacity planning
quick and dirty math
predictinr when your systems will fail
make your system stats tell stories
buyinr stuff: procurement is a process
performance and capacity: two different animals
the effects of social websites and open apis
2 setting goals for capacity
different kinds of requirements and measurements
architecture decisions
3 measurement: units of capacity
aspects of capacity tracking tools
applications of monitoring
api usare and its effect on capacity
examples and reality ..
summary
4 predicting trends
ridinr your waues
procurement
前言回到顶部↑
SOMEWHERE AROUND 3 A.M. ON JULY 7TH, 2005, MY COWORKER, CAL HENDERSON, AND I WERE FINISHING up some final details before moving all of the traffic for our website, Flickr.com, to its new home: a Yahoo! data center in Texas. The original infrastructure in Vancouver was becom-ing more and more overloaded, and suffering from serious power and space constraints.Since Yahoo! had just acquired Flickr, it was time to bring new capacity online. It was about an hour after we changed DNS records to point to our shiny new servers that Cal happened to glance at the news. The London subway had just been bombed.
Londoners responded with their camera phones, among other things. Over the next 24 hours, Flickr saw more traffic than ever before, as photos from the disaster were uploaded to the site. News outlets began linking to the photos, and traffic on our new servers went through the roof.
It was not only a great example of citizen journalism, but also an object lesson--sadly, one born of tragedy--in capacity planning. Traffic can be sporadic and unpredictable at times.Had we not moved over to the new data center, Flickr.com wouldn't have been available that day.
Capacity planning has been around since ancient times, with roots in everything from economics to engineering. In a basic sense, capacity planning is resource management.When resources are finite, and come at a cost, you need to do some capadty planning.
When a civil engineering firm designs a new highway system, it's planning for capacity, as is a power company planning to deliver electricity to a metropolitan area. In some ways,their concerns have a lot in common with web operations; many of the basic concepts and concerns can be applied to all three disciplines.
While systems administration has been around since the 1960s, the branch focused on serving websites is still emerging. A large part of web operations is capacity planning and management. Those are processes, not tasks, and they are composed of many different parts.Although every organization goes about it differently, the basic concepts are the same:
·Ensure proper resources (servers, storage, network, etc.) are available to handle expected and unexpected loads.
·Have a clearly defined procurement and approval system in place.
·Be prepared to justify capital expenditures in support of the business.
·Have a deployment and management system in place to manage the resources once they are deployed.
Why I Wrote This Book
One of my frustrations as an operations engineering manager was not having somewhere to turn to help me figure out how much equipment we'd need to keep running. Existing books on the topic of computer capacity planning were focused on the mathematical theory of resource planning, rather than the practical implementation of the whole process.
A lot of literature addressed only rudimentary models of website use cases, and lacked specific information or advice. Instead, they tended to offer mathematical models designed to illustrate the principles of queuing theory, which is the foundation of traditional capac-ity planning. This approach might be mathematically interesting and elegant, but it doesn't help the operations engineer when informed he has a week to prepare for some unknown amount of additional traffic--perhaps due to the launch of a super new fea-ture--or seeing his site dying under the weight of a link from the front page of Yahoo!,Digg, or CNN.
I've found most books on web capacity planning were written with the implied assump-tion that concepts and processes found in non-web environments, such as manufacturing or industrial engineering, applied uniformly to website environments as well. While some of the theory surrounding such planning may indeed be similar, the practical application of those concepts doesn't map very well to the short timelines of website development.
In most web development settings, it's been my observation that change happens too fast and too often to allow for the detailed and rigorous capacity investigations common to other fields. By the time the operations engineer comes up with the queuing model for his system,new code is deployed and the usage characteristics have likely already changed dramati-cally. Or some other technological, social, or real-world event occurs, making all of the modeling and simulations irrelevant.
What I've found to be far more helpful, is talking to colleagues in the industry--people who come up against many of the same scal!ng and capacity issues. Over time, I've had contact with many different companies, each employing diverse architectures, and each experiencing different problems. But quite often they shared very similar approaches to solutions. My hope is that I can illustrate some of these approaches in this book.
Focus and Topics
This book is not about building complex models and simulations, nor is it about spending time running benchmarks over and over. It's not about mathematical concepts such as Lit-tle's Law, Markov chains, or Poisson arrival rates.
What this book is about is practical capacity planning and management that can take place in the real world. It's about using real tools, and being able to adapt to changing usage on a website that will (hopefully) grow over time. When you have a flat tire on the highway,you could spend a lot of time trying to figure out the cause, or you can get on with the obvious task of installing the spare and getting back on the road.
This is the approach I'm presenting to capacity planning: adaptive, not theoretical.
Londoners responded with their camera phones, among other things. Over the next 24 hours, Flickr saw more traffic than ever before, as photos from the disaster were uploaded to the site. News outlets began linking to the photos, and traffic on our new servers went through the roof.
It was not only a great example of citizen journalism, but also an object lesson--sadly, one born of tragedy--in capacity planning. Traffic can be sporadic and unpredictable at times.Had we not moved over to the new data center, Flickr.com wouldn't have been available that day.
Capacity planning has been around since ancient times, with roots in everything from economics to engineering. In a basic sense, capacity planning is resource management.When resources are finite, and come at a cost, you need to do some capadty planning.
When a civil engineering firm designs a new highway system, it's planning for capacity, as is a power company planning to deliver electricity to a metropolitan area. In some ways,their concerns have a lot in common with web operations; many of the basic concepts and concerns can be applied to all three disciplines.
While systems administration has been around since the 1960s, the branch focused on serving websites is still emerging. A large part of web operations is capacity planning and management. Those are processes, not tasks, and they are composed of many different parts.Although every organization goes about it differently, the basic concepts are the same:
·Ensure proper resources (servers, storage, network, etc.) are available to handle expected and unexpected loads.
·Have a clearly defined procurement and approval system in place.
·Be prepared to justify capital expenditures in support of the business.
·Have a deployment and management system in place to manage the resources once they are deployed.
Why I Wrote This Book
One of my frustrations as an operations engineering manager was not having somewhere to turn to help me figure out how much equipment we'd need to keep running. Existing books on the topic of computer capacity planning were focused on the mathematical theory of resource planning, rather than the practical implementation of the whole process.
A lot of literature addressed only rudimentary models of website use cases, and lacked specific information or advice. Instead, they tended to offer mathematical models designed to illustrate the principles of queuing theory, which is the foundation of traditional capac-ity planning. This approach might be mathematically interesting and elegant, but it doesn't help the operations engineer when informed he has a week to prepare for some unknown amount of additional traffic--perhaps due to the launch of a super new fea-ture--or seeing his site dying under the weight of a link from the front page of Yahoo!,Digg, or CNN.
I've found most books on web capacity planning were written with the implied assump-tion that concepts and processes found in non-web environments, such as manufacturing or industrial engineering, applied uniformly to website environments as well. While some of the theory surrounding such planning may indeed be similar, the practical application of those concepts doesn't map very well to the short timelines of website development.
In most web development settings, it's been my observation that change happens too fast and too often to allow for the detailed and rigorous capacity investigations common to other fields. By the time the operations engineer comes up with the queuing model for his system,new code is deployed and the usage characteristics have likely already changed dramati-cally. Or some other technological, social, or real-world event occurs, making all of the modeling and simulations irrelevant.
What I've found to be far more helpful, is talking to colleagues in the industry--people who come up against many of the same scal!ng and capacity issues. Over time, I've had contact with many different companies, each employing diverse architectures, and each experiencing different problems. But quite often they shared very similar approaches to solutions. My hope is that I can illustrate some of these approaches in this book.
Focus and Topics
This book is not about building complex models and simulations, nor is it about spending time running benchmarks over and over. It's not about mathematical concepts such as Lit-tle's Law, Markov chains, or Poisson arrival rates.
What this book is about is practical capacity planning and management that can take place in the real world. It's about using real tools, and being able to adapt to changing usage on a website that will (hopefully) grow over time. When you have a flat tire on the highway,you could spend a lot of time trying to figure out the cause, or you can get on with the obvious task of installing the spare and getting back on the road.
This is the approach I'm presenting to capacity planning: adaptive, not theoretical.
媒体评论回到顶部↑
“John Allspaw的书在入门时非常有用——非常实用的Web工作原理深入研究。无论你是正在团队中学习采购过程（procurement process），还是必须成功计划一些详细而明确的方法，这本书对于任何想了解如何构建下一个Flickr的人都是必读教材。”.
——Chad Dickerson，Etsy网站的CTO，Salon．com和InfoWorld．com的前任CTO，以及Yahoo！Developer Network和Brickhouse的主管...
——Chad Dickerson，Etsy网站的CTO，Salon．com和InfoWorld．com的前任CTO，以及Yahoo！Developer Network和Brickhouse的主管...
加载中...
