《Beautiful Architecture》——架构之美的英文版

需积分: 32 92 浏览量更新于2024-07-20 收藏 4.4MB PDF 举报

"Beautiful Architecture，架构之美英文版" 《Beautiful Architecture》是一本由Diomidis Spinellis和Georgios Gousios编辑的书籍，聚焦于软件架构的美学和设计原则。这本书探讨了如何构建优雅、高效且易于维护的系统结构。出版于2009年，由O'Reilly Media发行，其内容可能涵盖了多个与软件架构相关的主题，包括但不限于设计模式、架构风格、可扩展性、灵活性、可维护性以及系统集成。在软件工程领域，"架构之美"并不仅仅是视觉上的吸引力，更关乎功能性和可持续性。一个优秀的架构能够清晰地定义组件之间的关系，支持模块化设计，使得代码更容易理解和修改。这通常涉及选择合适的架构风格，例如微服务架构、层状架构、事件驱动架构等，每种风格都有其特定的优势和适用场景。本书可能详细介绍了各种实际案例，展示如何在特定项目中应用这些架构原则，以解决复杂问题并确保系统的高性能。编辑Diomidis Spinellis和Georgios Gousios都是在软件工程和系统分析方面有深厚背景的专家，他们的贡献很可能使这本书成为软件开发者、架构师和项目经理的重要参考资料。编辑团队包括Mary Treseler、Sarah Schneider以及Genevieve d'Entremont等人，他们确保了内容的质量和呈现方式的专业性。此外，Nancy Reinhardt负责校对，Fred Brown负责索引，封面和内页设计则由Karen Montgomery和David Futato操刀，整体上为读者提供了一本既教育性又视觉吸引人的读物。第一版于2009年1月发布，这本书可能已经成为了软件开发领域的经典之作，对于那些想要提升自己在软件架构设计方面能力的人来说，是一本不可多得的资源。尽管是英文版，但对于全球范围内的专业读者，尤其是英语为工作语言的IT专业人士来说，它提供了深入理解软件架构艺术的宝贵机会。

How This Book Is Organized

We have organized the contents of this book around five thematic areas: overviews, enterprise

applications, systems, end-user applications, and programming languages. There is an obvious,

but not deliberate, lack of chapters on desktop software architectures. Having approached more

than 50 software architects, this result was another surprise for us. Are there really no shining

examples of beautiful desktop software architectures? Or are talented architects shying away

from an area often driven by a quest to continuously pile ever more features on an application?

We are really looking forward to hearing from you on these issues.

Part I: On Architecture

Part I of this book examines the breadth and scope of software architecture and its implications

for software development and evolution.

Chapter 1,

What Is Architecture?

, by John Klein and David Weiss, defines software architecture

by examining the subject through the perspectives of quality concerns and architectural

structures.

Chapter 2,

A Tale of Two Systems: A Modern-Day Software Fable

, by Pete Goodliffe, provides

an allegory on how software architectures can affect system evolution and developer

engagement with a project.

Part II: Enterprise Application Architecture

Enterprise systems, the IT backbone of many organizations, are large and often tailor-made

conglomerates of software usually built from diverse components. They serve large,

transactional workloads and must scale along with the enterprise they support, readily

adapting to changing business realities. Scalability, correctness, stability, and extensibility are

the most important concerns when architecting such systems. Part II of this book includes some

exemplar cases of enterprise software architectures.

Chapter 3,

Architecting for Scale

, by Jim Waldo, demonstrates the architectural prowess

required to build servers for massive multiplayer online games.

Chapter 4,

Making Memories

, by Michael Nygard, goes through the architecture of a

multistage, multisite data processing system and presents the compromises that must be made

to make it work.

Chapter 5,

Resource-Oriented Architectures: Being “In the Web”

, by Brian Sletten, discusses

the power of resource mapping when constructing data-driven applications and provides an

elegant example of a purely resource-oriented architecture.

xiv P RE FA CE

Chapter 6,

Data Grows Up: The Architecture of the Facebook Platform

, by Dave Fetterman,

advocates data-centric systems, explaining how a good architecture can create and support an

application ecosystem.

Part III: Systems Architecture

Systems software is arguably the most demanding type of software to design, partly because

efficient use of hardware is a black art mastered by a selected few, and partly because many

consider systems software as infrastructure that is “simply there.” Seldom are great systems

architectures designed on a blank sheet; most systems that we use today are based on ideas

first conceived in the 1960s. The chapters in Part III walk you through four innovative systems

software architectures, discussing the complexities behind the architectural decisions that

made them beautiful.

Chapter 7,

Xen and the Beauty of Virtualization

, by Derek Murray and Keir Fraser, gives an

example of how a well-thought-out architecture can change the way operating systems evolve.

Chapter 8,

Guardian: A Fault-Tolerant Operating System Environment

, by Greg Lehey,

presents a retrospective on the architectural choices and building blocks (both software and

hardware) that made Tandem the platform of choice in high-availability environments for

nearly two decades.

Chapter 9,

JPC: An x86 PC Emulator in Pure Java

, by Rhys Newman and Christopher Dennis,

describes how carefully designed software and a good understanding of domain requirements

can overcome the perceived deficiencies of a programming system.

Chapter 10,

The Strength of Metacircular Virtual Machines: Jikes RVM

, by Ian Rogers and Dave

Grove, walks us through the architectural choices required for creating a self-optimizable, self-

hosting runtime for a high-level language.

Part IV: End-User Application Architectures

End-user applications are those that we interact with in our everyday computing lives, and the

software that our CPUs burn the most cycles to execute. This kind of software normally does

not need to carefully manage resources or serve large transaction volumes. However, it does

need to be usable, secure, customizable, and extensible. These properties can lead to popularity

and widespread use and, in the case of free and open source software, to an army of volunteers

willing to improve it. In Part IV, the authors dissect the architectures and the community

processes required to evolve two very popular desktop software packages.

Chapter 11,

GNU Emacs: Creeping Featurism Is a Strength

, by Jim Blandy, explains how a set

of very simple components and an extension language can turn the humble text editor into

an operating system

the Swiss army knife of a programmer’s toolchest.

As some die-hard users say, “Emacs is my operating system; Linux just provides the device drivers.”

P RE FA CE xv

Chapter 12,

When the Bazaar Sets Out to Build Cathedrals

, by Till Adam and Mirko Boehm,

demonstrates how community processes such as sprints and peer-reviews can help software

architectures evolve from rough sketches into beautiful systems.

Part V: Languages and Architecture

As many people have pointed out in their works, the programming language we use affects

the way we solve a problem. But can a programming language also affect a system’s

architecture and, if so, how? In the architecture of buildings, new materials and the adoption

of CAD systems allowed the expression of more sophisticated and sometimes strikingly

beautiful designs; does the same also apply to computer programs? Part V, which contains the

last two chapters, investigates the relationship between the tools we use and the designs we

produce.

Chapter 13,

Software Architecture: Object-Oriented Versus Functional

, by Bertrand Meyer,

compares the affordances of object-oriented and functional architectural styles.

Chapter 14,

Rereading the Classics

, by Panagiotis Louridas, surveys the architectural choices

behind the building blocks of modern and classical object-oriented software languages.

Finally, in the thought-provoking Afterword, William J. Mitchell, an MIT Professor of

Architecture and Media Arts and Sciences, ties the concept of beauty between the building

architectures we encounter in the real world and the software architectures residing on silicon.

Principles, Properties, and Structures

Late in this book’s review process, one of the reviewers asked us to provide our personal

opinion, in the form of commentary, on what a reader could learn from each chapter. The idea

was intriguing, but we did not like the fact that we would have to second-guess the chapter

authors. Asking the authors themselves to provide a meta-analysis of their writings would lead

to a Babel tower of definitions, terms, and architectural constructs guaranteed to confuse

readers. What was needed was a common vocabulary of architectural terms; thankfully, we

realized we already had that in our hands.

In the Foreword, Stephen Mellor discusses seven principles upon which all beautiful

architectures are based. In Chapter 1, John Klein and David Weiss present four architecture

building blocks and six properties that beautiful architectures exhibit. A careful reader will

notice that Mellor’s principles and Klein’s and Weiss’s properties are not independent of each

other. In fact, they mostly coincide; this happens because great minds think alike. All three,

being very experienced architects, have seen many times in action the importance of the

concepts they describe.

xvi P RE FA CE

We merged Mellor’s architectural principles with the definitions of Klein and Weiss into two

lists: one containing principles and properties (Table P-1), and one containing structures

(Table P-2). We then asked the chapter authors to mark the terms they thought applied to their

chapters, and produced a corresponding legend for each chapter. In these tables, you can see

the definition of each principle, property, or architectural construct that appears in the chapter

legend. We hope the legends will guide your reading of this book by giving you a clean

overview of the contents of each chapter, but we urge you to delve into a chapter’s text rather

than simply stay with the legend.

TABLE P-1. Architectural principles and properties

Principle or property

The ability of an architecture to...

Versatility

...offer “good enough” mechanisms to address a variety of problems with an economy of

expression.

Conceptual integrity

...offer a single, optimal, nonredundant way for expressing the solution of a set of similar

problems.

Independently

changeable

...keep its elements isolated so as to minimize the number of changes required to

accommodate changes.

Automatic propagation

...maintain consistency and correctness, by propagating changes in data or behavior across

modules.

Buildability

...guide the software’s consistent and correct construction.

Growth accommodation

...cater for likely growth.

Entropy resistance

...maintain order by accommodating, constraining, and isolating the effects of changes.

TABLE P-2. Architectural structures

Structure A structure that...

Module

...hides design or implementation decisions behind a stable interface.

Dependency

...organizes components along the way where one uses functionality of another.

Process

...encapsulates and isolates the runtime state of a module.

Data access

...compartmentalizes data, setting access rights to it.

Conventions Used in This Book

The following typographical conventions are used in this book:

Italic

Indicates new terms, URLs, email addresses, filenames, and file extensions.

P RE FA CE xvii

Constant width

Used for program listings, as well as within paragraphs to refer to program elements such

as variable or function names, databases, data types, environment variables, statements,

and keywords.

Constant width bold

Shows commands or other text that should be typed literally by the user.

Constant width italic

Shows text that should be replaced with user-supplied values or by values determined by

context.

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book

in your programs and documentation. You do not need to contact us for permission unless

you’re reproducing a significant portion of the code. For example, writing a program that uses

several chunks of code from this book does not require permission. Selling or distributing a

CD-ROM of examples from O’Reilly books does require permission. Answering a question by

citing this book and quoting example code does not require permission. Incorporating a

significant amount of example code from this book into your product’s documentation does

require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author,

publisher, and ISBN. For example: “

Beautiful Architecture

, edited by Diomidis Spinellis and

If you feel your use of code examples falls outside fair use or the permission given here, feel

free to contact us at

permissions@oreilly.com

Safari® Books Online

When you see a Safari® Books Online icon on the cover of your favorite

technology book, that means the book is available online through the O’Reilly

Network Safari Bookshelf.

Safari offers a solution that’s better than e-books. It’s a virtual library that lets you easily search

thousands of top tech books, cut and paste code samples, download chapters, and find quick

answers when you need the most accurate, current information. Try it for free at

http://safari

.oreilly.com

xviii P RE FA CE

剩余427页未读，继续阅读

wdbmail

粉丝: 0
资源: 4

《Beautiful Architecture》——架构之美的英文版

架构之美（Beautiful Architecture）

架构之美英文完整版(Beautiful.Architecture)

架构之美beautiful architecture（中文精选版）

Beautiful Architecture 架构之美

架构之美 英文版 Beautiful Architecture

beautiful-architecture 架构之美

架构之美（Beautiful Architecture）英文版

架构之美 （Beautiful Architecture) 英文版

架构之美英文版'Reilly+Beautiful+Architecture

架构之美英文版(beautiful architecture leading thinkers reveal the hidden beauty in software design)

最新资源

架构之美英文版 Beautiful Architecture

架构之美（Beautiful Architecture) 英文版