With Atlas of Novel Tectonics, Reiser+Umemoto hone in on the many facets of architecture and illuminate their theories with great thought and simplicity. The Atlas is organized as an accumulation of short chapters that address the workings of matter and force, material science, the lessons of art and architectural history, and the influence of architecture on culture (and vice versa). Reiser+Umemoto see architectural design as a series of problem situations, and each chapter is an argument devoted to a specific condition or case. Influenced by a wide range of fields and phenomenaBrillat-Savarin's classic The Physiology of Taste is one of their primary modelsthe authors provide a cross-section of thinking and inspiration. The result is both an elucidation of the concepts that guide Reiser+Umemoto through their own design process and a series of meditations on topics that have formed their own sense as architects. Atlas of Novel Tectonics offers an entirely fresh perspective on subjects that are generally taken for granted, and does so with a welcome punch and energy.

    This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours-- sometimes even minutes-no matter what the size of a project or the complexity of its code base. Jez Humble and David Farley begin by presenting the foundations of a rapid, reliable, low-risk delivery process. Next, they introduce the "deployment pipeline," an automated process for managing all changes, from check-in to release. Finally, they discuss the "ecosystem" needed to support continuous delivery, from infrastructure, data and configuration management to governance. The authors introduce state-of-the-art techniques, including automated infrastructure management and data migration, and the use of virtualization. For each, they review key issues, identify best practices, and demonstrate how to mitigate risks. Coverage includes - Automating all facets of building, integrating, testing, and deploying software - Implementing deployment pipelines at team and organizational levels - Improving collaboration between developers, testers, and operations - Developing features incrementally on large and distributed teams - Implementing an effective configuration management strategy - Automating acceptance testing, from analysis to implementation - Testing capacity and other non-functional requirements - Implementing continuous deployment and zero-downtime releases - Managing infrastructure, data, components and dependencies - Navigating risk management, compliance, and auditing Whether you're a developer, systems administrator, tester, or manager, this book will help your organization move from idea to release faster than ever--so you can deliver value to your business rapidly and reliably.

    Taking as his starting point dramatic examples such as the High Line in New York City and the outrageous island experiment of Dubai, Moore then reaches far and wide: back in time to explore the Covent Garden brothels of eighteenth-century London and the fetishistic minimalism of Adolf Loos; across the world to assess a software magnate's grandiose mansion in Atlanta and Daniel Libeskind's failed design for the World Trade Center site; and finally to the deeply naturalistic work of Lina Bo Bardi, whom he celebrates as the most underrated architect of the modern era.Just published in the UK, Why We Build is already being hailed as a vibrant new classic:"Moore's writing is lively and engaging, his language straightforward, his case studies unpredictable and instructive. . . . Moore certainly knows how to make these sacred monsters come alive on the page."-The Evening Standard (London)"Mischievous . . . [Moore] has a lot to offer those who like verbal flexibility and thought-provoking aphorisms. . . . Elegant and witty, with a sometimes eighteenth-century sensuality, this is a hard-hitting book with great panache." -The Daily Telegraph"Elegantly written. . . . What Moore explores with insight and wit [is] the DESIRE to build. The emotions carrying it. The drive for beauty, monumentality, display, a kind of immortality." -The New Humanist"[A] fresh analytic approach [that is] engaging, outrageous, wise, very probably true and rather important ." -Country LifeReaders will never look at architecture the same way again.

    Even though these systems are essential, when was the last time you gave them much thought? Not only is infrastructure shrouded in mystery, much of it is woefully out of date--bridges are falling, public transportation is overcrowded, and most roads haven't been updated since the 1950s. In On the Grid, Scott Huler sets out to understand all of the systems that shape our society--from transportation, water, and garbage to the Internet coming through our cable lines.He begins his entertaining, fascinating journey at his house in Raleigh, North Carolina, and travels everywhere from the inside of a storm water pipe to the sewers of ancient Rome. Each chapter follows one element of infrastructure back to its source. Huler visits power plants, watches new asphalt pavement being laid, and traces a drop of water backward from his faucet to the Gulf of Mexico. He reaches out to guides along the way, both the workers who operate these systems and the people who plan them.A mesmerizing and hilarious narrative, On the Grid is filled with amazing insights, interviews, and stories that bring an overlooked but indispensable subject to life. You'll never look at your day the same way again.

    With this book, you'll get a candid and insightful look at how software is constructed and maintained by some of the world's leading practitioners.Titus Winters, Tom Manshreck, and Hyrum K. Wright, software engineers and a technical writer at Google, reframe how software engineering is practiced and taught: from an emphasis on programming to an emphasis on software engineering, which roughly translates to programming over time.You'll learn:Fundamental differences between software engineering and programmingHow an organization effectively manages a living codebase and efficiently responds to inevitable changeWhy culture (and recognizing it) is important, and how processes, practices, and tools come into play

    The Reactive Application model addresses these demands through new patterns designed to "react" effectively to user and system events, changes in load, competition for shared system resources, and unanticipated failures. Although reactive design patterns can be implemented using standard enterprise development tools, you best realize the benefits when you pair them with a functional programming language like Scala and an Actor-based concurrency system like Akka.Reactive Design Patterns is a clearly-written guide for building event-driven distributed systems that are resilient, responsive, and scalable. Written by the authors of the Reactive Manifesto, this book teaches you to apply reactive design principles to the real problems of distributed application development. You'll discover technologies and paradigms that can be used to build reactive applications including Akka and other actor-based systems, functional programming, replication and distribution, and implementation techniques such as futures, iteratees, and reactive streams. While the book presents concrete examples in Scala, Java, JavaScript, and Erlang, the primary goal is to introduce patterns and best practices that you can use to apply reactive principles to common problems you'll face when building distributed systems.WHAT'S INSIDE* Discover best practices and patterns for building responsive applications* Build applications that can withstand hardware or software failure at any level* Patterns for fault tolerance, scalability, and responsiveness* Maximize multicore hardware using asynchronous and event-driven solutions* Scale applications under tremendous loadReaders should be familiar with a standard programming language like Java, C++ or C# and be comfortable with the basics of distributed systems. Software engineers and architects will learn how to avoid common pitfalls and apply patterns for solving day-to-day problems in a fault-tolerant and scalable way to maximize their application's responsiveness to users and clients. Project leaders and CTOs will gain a deeper understanding of the philosophy behind resilience and scalability in distributed systems, as well as their limitations, challenges and benefits.

    Thread programming enables developers to design applications that are more responsive to user demands, faster, and more easily controlled. This book offers comprehensive coverage of this vital aspect of the Java language. The book is completely up-to-date with the new thread model that is now incorporated into the most recent version of the Java Virtual Machine. All Java programmers interested in doing concurrent programming must understand these new concepts. The book approaches the topic from a design pattern point of view. It introduces and summarizes Java's concurrency support, shows readers how to initiate, control, and coordinate concurrent activities, and offers numerous recipe-like techniques for designing and implementing Java structures that solve common concurrent programming challenges. Specifically, the book presents important strategies for avoiding the inconsistencies that can crop up in multi-threaded programs, addresses the concept of liveness-how to ensure that all threads in use are kept active simultaneously, examines state-dependent action, and demonstrates effective methods for handling user requests in a multi-threaded environment.

    The consequences of this gathering may be enormous. In this new ebook, experts Patrick J. Michaels and Paul C. Knappenberger assess the issues sure to drive the debate before, during, and after the Paris meeting.

    Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. This practical guide ties those parts together with a new way to think about architecture and time.

    The bridge, completed in 1937, also announced to the world America's engineering prowess and full assumption of its destined continental dominance. The Golden Gate is a counterpart to the Statue of Liberty, pronouncing American achievement in an unmistakable American fashion. The nation's very history is expressed in the bridge's art deco style and stark verticality. Kevin Starr's Golden Gate is a brilliant and passionate telling of the history of the bridge, and the rich and peculiar history of the California experience. The Golden Gate is a grand public work, a symbol and a very real bridge, a magnet for both postcard photographs and suicides. In this compact but comprehensive narrative, Starr unfolds the hidden-in-plain-sight meaning of the Golden Gate, putting it in its place among classic works of art.

    This practical, practitioner-oriented guide explains how to design successful architectures for information systems and to see these through to their successful implementation.

    Williams any rock used as building material can tell a fascinating story. All he has to do is look at building stone in any urban center to find a range of rocks equal to any assembled by plate tectonics. In Stories in Stone, he takes you on his explorations to find 3.5-billion-year-old rock that looks like swirled pink and black taffy, a gas station made of petrified wood, and a Florida fort that has withstood 300 years of attacks and hurricanes, despite being made of a stone that has the consistency of a granola bar.In Stories in Stone, Williams also weaves in the cultural history of stone. He shows why a white, fossil-rich limestone from Indiana became the only building stone to be used in all 50 states; how in 1825, the construction of the Bunker Hill Monument led to America's first commercial railroad; and why when the same kind of marble used by Michelangelo was used on a Chicago skyscraper it warped so much after 19 years that all 44,000 panels of the stone had to be replaced. A love letter to building stone, from New England brownstone and Morton Gneiss of Minnsota to the limestone of Salem, Indiana; from granite and travertine to Carrara marble, David Willilams brings to life the stones you will see in the structures of every city, large and small. After reading his book, you will forever look at stone buildings with new eyes.

    Advocates of NoSQL databases claim they can be used to build systems that are more performant, scale better, and are easier to program." ""NoSQL Distilled" is a concise but thorough introduction to this rapidly emerging technology. Pramod J. Sadalage and Martin Fowler explain how NoSQL databases work and the ways that they may be a superior alternative to a traditional RDBMS. The authors provide a fast-paced guide to the concepts you need to know in order to evaluate whether NoSQL databases are right for your needs and, if so, which technologies you should explore further. The first part of the book concentrates on core concepts, including schemaless data models, aggregates, new distribution models, the CAP theorem, and map-reduce. In the second part, the authors explore architectural and design issues associated with implementing NoSQL. They also present realistic use cases that demonstrate NoSQL databases at work and feature representative examples using Riak, MongoDB, Cassandra, and Neo4j. In addition, by drawing on Pramod Sadalage's pioneering work, "NoSQL Distilled" shows how to implement evolutionary design with schema migration: an essential technique for applying NoSQL databases. The book concludes by describing how NoSQL is ushering in a new age of Polyglot Persistence, where multiple data-storage worlds coexist, and architects can choose the technology best optimized for each type of data access.

    But developing these systems brings its own set of headaches. With lots of examples and practical advice, this book takes a holistic view of the topics that system architects and administrators must consider when building, managing, and evolving microservice architectures.Microservice technologies are moving quickly. Author Sam Newman provides you with a firm grounding in the concepts while diving into current solutions for modeling, integrating, testing, deploying, and monitoring your own autonomous services. You'll follow a fictional company throughout the book to learn how building a microservice architecture affects a single domain.Discover how microservices allow you to align your system design with your organization's goalsLearn options for integrating a service with the rest of your systemTake an incremental approach when splitting monolithic codebasesDeploy individual microservices through continuous integrationExamine the complexities of testing and monitoring distributed servicesManage security with user-to-service and service-to-service modelsUnderstand the challenges of scaling microservice architectures

    But with so many distributed databases and tools available today, it’s often difficult to understand what each one offers and how they differ. With this practical guide, Alex Petrov guides developers through the concepts behind modern database and storage engine internals.Throughout the book, you’ll explore relevant material gleaned from numerous books, papers, blog posts, and the source code of several open source databases. These resources are listed at the end of parts one and two. You’ll discover that the most significant distinctions among many modern databases reside in subsystems that determine how storage is organized and how data is distributed.This book examines:Storage engines: Explore storage classification and taxonomy, and dive into B-Tree-based and immutable log structured storage engines, with differences and use-cases for eachDistributed systems: Learn step-by-step how nodes and processes connect and build complex communication patterns, from UDP to reliable consensus protocolsDatabase clusters: Discover how to achieve consistent models for replicated data