- Paperback: 720 pages
- Publisher: Wrox; 1 edition (February 24, 2009)
- Language: English
- ISBN-10: 0470257636
- ISBN-13: 978-0470257630
- Product Dimensions: 7.4 x 1.5 x 9.2 inches
- Shipping Weight: 2.2 pounds (View shipping rates and policies)
- Average Customer Review: 21 customer reviews
- Amazon Best Sellers Rank: #646,952 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Design - Build - Run: Applied Practices and Principles for Production Ready Software Development 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
From the Back Cover
Design - Build - Run
Applied Practices and Principles for Production-Ready Software Development
What is the secret to successful software development? Veteran software architect Dave Ingram believes that a true success story is a project that delivers a system with all the required functionality, on time and within budget. In this book, Ingram shares his secrets to building software that must not fail and he explains why everything developers do during the process of software development impacts the overall outcome of a project.
Serving as a guide to designing and building production-ready software from the start, this book examines the entire process and the tools needed to develop and test applications. You'll look at the environments and circumstances in which a system could be used and how to make certain that it's fit for these purposes. Most importantly, the book covers the practices and patterns you can leverage during design and development to improve software quality, lower the total cost of ownership, and ensure that it is truly production-ready. With a thorough understanding of what is involved in designing, building, and running large-scale software systems, you'll enhance your skills for building successful solutions.
What you will learn from this book
What production-readiness means and all the quality characteristics that software needs to meet
Key patterns and practices that ensure systems are designed and built to be production-ready and meet required standards and practices
How to design for resilience, batch, performance, monitoring, incident investigation, reporting, application maintenance, testing, and deployment
The pros and cons of using various tools and technologies and how to use them effectively
Techniques for reviewing and testing a prototype
Ways to plan the logical architecture and model the application
Who this book is for
This book is for software developers of all levelsfrom programmers through to software architectswho are interested in learning all aspects related to building production-ready systems. Familiarity with software designs and development practices is essential.
Wrox guides are crafted to make learning programming languages and technologies easier than you think. Written by programmers for programmers, they provide a structured, tutorial format that will guide you through all the techniques involved.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
gives you a template for the creation of software.Applications, Environments and processes must be fit for
purpose, and the users must be trained.This is the essence of the cycle.
Quality is a large part of all workable software and testing is the key to gain this element. The details
of quality in this book show an understanding of this type of testing. In 7 stages, the book outlines how the
creation build and testing get done, a replicable process that helps take the software through build stages.
Detailed and yet succint, it shows how to implement the design for its Processes and purposes.After the production,
the so called construction phase shows packaging in the traditional box, cd/dvd, manual, sense through to component
specifications. The construction phase can be taken multiple ways, but the basic ideas can be interpreted in the
manner one usually knows, or on a pure download basis.
In a section called the Production Landscape , the book covers environment in detail, entailing testing,
hardware applicability, network relations and connection to "primary", and "secondary" data centres. The testing
section is once again brief but thorough, and it still covers the full gamut of what is needed.The last part of
this section deals with service, the support realms, support on multiple levels, as well as password reset
protocols ( for security ).
Several sections after this cover methods and elements that relate directly to security and operating
functions. The incident investigation, although separate, is a key part of this cycle of the software production,
and slots in after all develop is done and production is complete, and incidents appear from cycles of use that
could not normally be conceived of in previous testing.
Application testing and maintenance is part of what some call the patch cycle, which also includes the
incident investigation and resolution section.
There is a case study for the purposes of the book example.After this there is Patterns and practices where
the writer shows designing for Batch, reporting, Performance, Resilience, Monitoring, Incident Investigation,
Application Maintenance, testing, Deployment, and shows how this works in the software world. The final element, is
of course Application Maintenance, and testing. So, from start to finish, this is an element that covers the end
product the cycles in the book look after. In all respects this is a guide for the project management of software
in all its types.
I never could really find the right "pace" with "Design - Build - Run," though, and I blame the book itself for much of that. The level of granularity and detail at which the topics within are addressed varies greatly (even within chapters), and there were many places I found myself wondering exactly why I needed to be told what the author stated. In fact, I'd almost characterize "Design - Build - Run" as an overview of things most of us already know and should be putting into practice; a lot of it read just like the computer-based training "courses" my employer offers us each year on software architecture and engineering (which I don't particularly find engaging or all that useful). It's a far cry, though, from the sort of material I'd expect to be covered in even a bachelor-level program in Software Engineering, and it's not quite a survey of industry best practices and use cases, either.
The author even admits to some of this varying focus in stating the book isn't a project management reference, nor a compendium of technology-specific best practices. He then goes on to state that the book focuses on the technical aspects of production-ready software development (and, let's be honest: given the timeframes and budgets of the vast majority of software development projects, creating "production-ready" code is really the goal of almost every development team). However, I didn't find the book all that technical where I felt it needed to be, and in other places, the level of attention to technical detail was needlessly involved.
Personally, for a more-focused look at best practices, I'd suggest Steve McConnell's fantastic Rapid Development: Taming Wild Software Schedules. Yes, "Design - Build - Run" covers broader ground than McConnell's book... but as both a developer and an architect (and now increasingly a project manager) I found his text much more applicable to my day-to-day job.