In this concise and comprehensive guide to the world of architecture, art historian Susie Hodge outlines the history and theory of architecture, from the earliest structures and monuments to the cutting-edge concepts of the present day, and profiles dozens of key buildings and celebrated architects. Topics and concepts include the Greek orders, Roman engineering, Gothic architecture, the Renaissance, the Baroque era, Revivalism, Art Nouveau, Modernism, Futurism, and Dynamic architecture. Every concept is accompanied by an illustration.
Winy Maas proposed a provocative and inspiring brief; he asked participants to redesign the cities of Rotterdam and New York in a way that everything is reachable within five minutes. A series of serious questions arise from the challenging brief: 'What will such a city look like? What happens to such an hypothesis if cars are the only mode of transport? What will such a city look like when it is only accessed by public transport? Or by walking?' How one can extend the knowledge of compact or dense cities? How fast cities can be? Is increased speed an ideal concept for future cities? Is development of new infrastructure sustainable for cities in future? Can Rotterdam become such a city? Is it possible to upscale Manhattan? How does mobility affects the working and living qualities of the cities and how is mobility shaping cities?
The 50 most significant principles and styles in architecture, each explained in half a minute. The bestselling 30-Second series offers a new approach to learning about those subjects you feel you should really understand. Every title takes a popular topic and dissects it into the 50 most significant ideas at its heart. Each idea, no matter how complex, is explained using a mere two pages, 300 words, and one picture: all easily digested in only half a minute. 30-Second Architecture presents you with the foundations of architectural knowledge. Expert authors are challenged to define and describe both the principles upon which architects depend, and the styles with which they put those principles into practice. So, if you want to know your arch from your elevation, and your Baroque from your Brutalism, or you wish to top off your next dinner party with a stirring speech on how form follows function, this is the quickest way to build your argument.
The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology--from Smalltalk to CORBA to Java to .NET--the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform. This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. The topics covered include · Dividing an enterprise application into layers · The major approaches to organizing business logic · An in-depth treatment of mapping between objects and relational databases · Using Model-View-Controller to organize a Web presentation · Handling concurrency for data that spans multiple transactions · Designing distributed object interfaces
Update Your Architectural Practices for New Challenges, Environments, and Stakeholder Expectations "I am continuously delighted and inspired by the work of these authors. Their first book laid the groundwork for understanding how to evolve the architecture of a software-intensive system, and this latest one builds on it in some wonderfully actionable ways." --Grady Booch, Chief Scientist for Software Engineering, IBM Research Authors Murat Erder, Pierre Pureur, and Eoin Woods have taken their extensive software architecture experience and applied it to the practical aspects of software architecture in real-world environments. Continuous Architecture in Practice provides hands-on advice for leveraging the continuous architecture approach in real-world environments and illuminates architecture's changing role in the age of Agile, DevOps, and cloud platforms. This guide will help technologists update their architecture practice for new software challenges. As part of the Vaughn Vernon Signature Series, this title was hand-selected for the practical, delivery-oriented knowledge that architects and software engineers can quickly apply. It includes in-depth guidance for addressing today's key quality attributes and cross-cutting concerns such as security, performance, scalability, resilience, data, and emerging technologies. Each key technique is demonstrated through a start-to-finish case study reflecting the authors' deep experience with complex software environments. Key topics include: Creating sustainable, coherent systems that meet functional requirements and the quality attributes stakeholders care about Understanding team-based software architecture and architecture as a "flow of decisions" Understanding crucial issues of data management, integration, and change, and the impact of varied data technologies on architecture Architecting for security, including continuous threat modeling and mitigation Architecting for scalability and resilience, including scaling microservices and serverless environments Using architecture to improve performance in continuous delivery environments Using architecture to apply emerging technologies successfully Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.
Over 200 illustrations drawn from the Art Institute of Chicago's repository of architectural drawings, models, and building fragments present a striking record of Chicago's great buildings and structures.
This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties. It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts. It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail. It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.
