Other Sellers on Amazon
& FREE Delivery
+ S$1.99 Delivery
FREE Delivery. No Minimum order value for first order in this category Details
Design Patterns: Elements of Reusable Object-Oriented Software Hardcover – 31 October 1994
Enhance your purchase
- ISBN-100201633612
- ISBN-13978-0201633610
- Edition1st
- Publication date31 October 1994
- LanguageEnglish
- Print length416 pages
Frequently bought together
- +
- +
Customers who viewed this item also viewed

Must-Read for Every Software Developer and Engineer
This classic is on just about every single must-read list for software developers, engineers, and architects (including lists featured on ZDNET, DZone, Guru99, Built In, Geeks for Geeks, Hacker News, and more) as a bible for solving software design problems effeciently.
Despite being one of the oldest books on a software engineer's shelf, it is still relevant and THE guide to creating reusable designs that are elegant and flexible, without having to rediscover the design solutions themselves.
Product description
From the Back Cover
Capturing a wealth of experience about the design of object-oriented software, four top-notch designers present a catalog of simple and succinct solutions to commonly occurring design problems. Previously undocumented, these 23 patterns allow designers to create more flexible, elegant, and ultimately reusable designs without having to rediscover the design solutions themselves.
The authors begin by describing what patterns are and how they can help you design object-oriented software. They then go on to systematically name, explain, evaluate, and catalog recurring designs in object-oriented systems. With Design Patterns as your guide, you will learn how these important patterns fit into the software development process, and how you can leverage them to solve your own design problems most efficiently.
Each pattern describes the circumstances in which it is applicable, when it can be applied in view of other design constraints, and the consequences and trade-offs of using the pattern within a larger design. All patterns are compiled from real systems and are based on real-world examples. Each pattern also includes code that demonstrates how it may be implemented in object-oriented programming languages like C++ or Smalltalk.
0201633612B07092001
About the Author
Product details
- Language : English
- Hardcover : 416 pages
- ISBN-10 : 0201633612
- ISBN-13 : 978-0201633610
- Best Sellers Rank: 4,865 in Books (See Top 100 in Books)
- 14 in Software & Graphics
- 30 in Software Design, Testing & Engineering
- 45 in Computer Science
- Customer reviews:
Customer reviews
Top reviews from other countries

- Programming languages. I do vast majority of my coding in Java, sometimes I code in another JVM languages. This book provides examples in C++ and/or Smalltalk. Even more, this book was written before Java was a thing! This has to have an impact on how easy to follow are some of the examples. If you write Java 8 code, I bet you know what is the difference between external and internal iterator. At the same time, C++ friends will probably be less obvious to you, and the concept of e.g. enum-based singletons will not be mentioned at all. If only someone could write this book once again, but focus on Java-centric point of view.
- GUI-based examples. For nearly all the patterns, there is a GUI-related example. I am deeply alergic to GUI development and would appreciate more examples relating to backend functionalities.
- Didn't we evolve since then? Many of these design patterns are explicitly targetting challenges around excessive memory utilisation and other past limitations. We can do better now. Same constraints still exist, but are applicable to a very different extent. I can see people blindly following some of these patterns today in the field, with very little reflection upon the actual problem they are trying to solve. Today good programming is frequently not about making the application consume less memory, but about making it easier to understand and change. The problems we are trying to solve have changed, therefore the solutions we apply need to change as well. Keep it in mind while reading this book - not all of that is of equal value today, as it was when this book was first published. This takes us swiftly to the next point, which is...
- The pattern catalogue. While many of these design patterns are still valuable these days, there may be others which are more valuable. Just compare and contrast the builder pattern, as described in this book vs the one described many years later by Joshua Bloch.
My recommendation - read this book if you haven't done it already. Learn all the good things, just don't forget the world has moved on since then.

Every team who use object-orientation should have a copy in the office to refer to.
If you want a softer read, there is a Head First book on design patterns - but I would still recommend having a copy of this book to refer to when you want to implement and adapt a pattern in real life.

There's still plenty to learn from this tome (the fundamentals haven't changed, after all). Just bare in mind that practicality and readability (particularly in the case of your successors) should trump "correctness" in all but the most niche high performance and academic projects.

