Neuf :
42,21€42,21€
Retours GRATUITS
Livraison à partir de 0,01 € :
mardi 13 juin
en France métropolitaine
En stock
Paiement
Transaction sécurisée
Expédié par
Amazon
Vendu par
Amazon
Achetez d'occasion 33,01 €
Autres vendeurs sur Amazon
+ 0,01 € Livraison
90 % positif(s) au cours des 12 derniers mois
+ Livraison gratuite
Frais d'expédition et Politique de retours
+ 0,01 € Livraison
92 % positif(s) au cours des 12 derniers mois

Téléchargez l'application Kindle gratuite et commencez à lire des livres Kindle instantanément sur votre smartphone, tablette ou ordinateur - aucun appareil Kindle n'est requis. En savoir plus
Lisez instantanément sur votre navigateur avec Kindle pour le Web.
Utilisation de l'appareil photo de votre téléphone portable - scannez le code ci-dessous et téléchargez l'application Kindle.


En savoir plus
Domain-Driven Design: Tackling Complexity in the Heart of Software Relié – 20 août 2003
Prix Amazon | Neuf à partir de | Occasion à partir de |
Format Kindle
"Veuillez réessayer" | — | — |
- Format Kindle
31,69 € Lisez avec notre Appli gratuite - Relié
42,21 €
Options d'achat et paniers Plus
“Eric Evans has written a fantastic book on how you can make the design of your software match your mental model of the problem domain you are addressing.
“His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique.
“The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers—it is a future classic.”
—Ralph Johnson, author of Design Patterns
“If you don’t think you are getting value from your investment in object-oriented programming, this book will tell you what you’ve forgotten to do.
“Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion.”
—Dave Collins, author of Designing Object-Oriented User Interfaces
“Eric weaves real-world experience modeling—and building—business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric’s descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field.”
—Luke Hohmann, author of Beyond Software Architecture
“This book belongs on the shelf of every thoughtful software developer.”
—Kent Beck
“What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important.”
—Kyle Brown, author of Enterprise Java™ Programming with IBM® WebSphere®
The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process.
Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development.
Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis—refactoring not just the code but the model underlying the code—in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:
- Getting all team members to speak the same language
- Connecting model and implementation more deeply
- Sharpening key distinctions in a model
- Managing the lifecycle of a domain object
- Writing domain code that is safe to combine in elaborate ways
- Making complex code obvious and predictable
- Formulating a domain vision statement
- Distilling the core of a complex domain
- Digging out implicit concepts needed in the model
- Applying analysis patterns
- Relating design patterns to the model
- Maintaining model integrity in a large system
- Dealing with coexisting models on the same project
- Organizing systems with large-scale structures
- Recognizing and responding to modeling breakthroughs
With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.
- Nombre de pages de l'édition imprimée560 pages
- LangueAnglais
- ÉditeurAddison Wesley
- Date de publication20 août 2003
- Dimensions18.8 x 3.56 x 24.26 cm
- ISBN-100321125215
- ISBN-13978-0321125217
Produits fréquemment achetés ensemble

Plus d'articles à découvrir
Description de l'éditeur
![]() |
![]() |
![]() |
![]() |
![]() |
|
---|---|---|---|---|---|
Narration de domaine | Conception axée sur le domaine distillée | Conception axée sur le domaine | Mise en œuvre de la conception pilotée par le domaine | Monolithes stratégiques et microservices | |
La description | En racontant et en visualisant des histoires, les experts du domaine et les membres de l'équipe rendent tangibles les processus métier et la connaissance du domaine, permettant à chacun de comprendre les personnes et les activités. | Guide concis, lisible et exploitable des bases de DDD : qu'est-ce que c'est, quels problèmes il résout, comment il fonctionne et comment en tirer rapidement de la valeur. | Entremêlant la conception et la pratique du développement, ce livre incorpore de nombreux exemples basés sur des projets réels pour illustrer l'application de la conception pilotée par le domaine au développement de logiciels dans le monde réel. | S'appuyant sur le livre historique d'Eric Evans, Vaughn Vernon combine des approches guidées de la mise en œuvre avec des architectures modernes, démontre l'importance et la valeur de se confiner au domaine des affaires | Aide les décideurs commerciaux et les membres de l'équipe technique à comprendre clairement leurs problèmes stratégiques grâce à la collaboration et à identifier les approches architecturales optimales. |
Qu'allez-vous apprendre | Les méthodes utilisent un langage pictographique simple, des techniques de modélisation basées sur des scénarios et une relation avec d'autres méthodes de modélisation et comment elles peuvent résoudre de nombreux problèmes courants. | Chaque technique DDD de base pour créer de meilleurs logiciels. Ne vous enterre jamais dans les détails - il se concentre sur ce que vous devez savoir pour obtenir des résultats. | Concevoir les meilleures pratiques, les techniques basées sur l'expérience et les principes fondamentaux qui facilitent le développement de projets logiciels faisant face à des domaines complexes. | Techniques DDD pratiques à travers des exemples de domaines familiers et comment utiliser DDD dans diverses architectures, y compris Hexagonal, SOA, Rest, CQRS, Event-Driven et Fabric/Grid-Based. | Comment construire des monolithes bien conçus, maintenables et extensibles, et progressivement reconcevoir et réimplémenter même les systèmes hérités les plus enchevêtrés en microservices vraiment efficaces. |
Description du produit
Quatrième de couverture
“Eric Evans has written a fantastic book on how you can make the design of your software match your mental model of the problem domain you are addressing.
“His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique.
“The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers―it is a future classic.”
―Ralph Johnson, author of Design Patterns“If you don’t think you are getting value from your investment in object-oriented programming, this book will tell you what you’ve forgotten to do.
“Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion.”
―Dave Collins, author of Designing Object-Oriented User Interfaces“Eric weaves real-world experience modeling―and building―business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric’s descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field.”
―Luke Hohmann, author of Beyond Software Architecture"This book belongs on the shelf of every thoughtful software developer."
--Kent Beck
"What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important."
--Kyle Brown, author of Enterprise Java™ Programming with IBM® WebSphere®
The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process.
Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development.
Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:
- Getting all team members to speak the same language
- Connecting model and implementation more deeply
- Sharpening key distinctions in a model
- Managing the lifecycle of a domain object
- Writing domain code that is safe to combine in elaborate ways
- Making complex code obvious and predictable
- Formulating a domain vision statement
- Distilling the core of a complex domain
- Digging out implicit concepts needed in the model
- Applying analysis patterns
- Relating design patterns to the model
- Maintaining model integrity in a large system
- Dealing with coexisting models on the same project
- Organizing systems with large-scale structures
- Recognizing and responding to modeling breakthroughs
With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.
Biographie de l'auteur
Eric Evans is the founder of Domain Language, a consulting group dedicated to helping companies build evolving software deeply connected to their businesses. Since the 1980s, Eric has worked as a designer and programmer on large object-oriented systems in several complex business and technical domains. He has also trained and coached development teams in Extreme Programming.
Détails sur le produit
- Éditeur : Addison Wesley; 1er édition (20 août 2003)
- Langue : Anglais
- Relié : 560 pages
- ISBN-10 : 0321125215
- ISBN-13 : 978-0321125217
- Poids de l'article : 1,24 Kilograms
- Dimensions : 18.8 x 3.56 x 24.26 cm
- Classement des meilleures ventes d'Amazon : 5 en Programmation orientée objet
- Commentaires client :
À propos de l'auteur

Découvrir d'autres livres de l'auteur, voir des auteurs similaires, lire des blogs d'auteurs et plus encore
Commentaires client
Les avis clients, y compris le nombre d’étoiles du produit, aident les clients à en savoir plus sur le produit et à décider s'il leur convient.
Pour calculer le nombre global d’étoiles et la ventilation en pourcentage par étoile, nous n'utilisons pas une simple moyenne. Au lieu de cela, notre système prend en compte des éléments tels que la date récente d'un commentaire et si l'auteur de l'avis a acheté l'article sur Amazon. Les avis sont également analysés pour vérifier leur fiabilité.
En savoir plus sur le fonctionnement des avis clients sur Amazon-
Meilleures évaluations
Meilleures évaluations de France
Un problème s'est produit lors du filtrage des commentaires. Veuillez réessayer ultérieurement.
Comme ce livre a plus de 10 ans, j'attends avec impatience la suite ou une seconde édition, vu que depuis l'invention du DDD, beaucoup de littérature et améliorations ont fleuri sur ce sujet.
Je le recommande à tout développeur, tout simplement.
Visiblement l'auteur n'est pas seulement exigeant dans son travail de design et de développement logiciel, mais a en plus réfléchi à sa propre pratique avec une grande profondeur d'analyse. Le résultat est un véritable concentré de remarques, principes et techniques, dans un format "patterns" narratif qui se lit néanmoins du début à la fin. Les insights sur comment partager un modèle entre intervenants d'un projet, et sur le design stratégique suffisent à eux seuls à justifier l'achat du livre, qui comprend bien d'autres chapitres.
Ce livre s'adresse manifestement au développeur expérimenté et curieux, il est tellement concentré qu'il semblera indigeste au néophyte, et il mérite plusieurs lectures (4 pour ma part, avec des découvertes à chaque fois).
Si vous aimez l'orienté objet, la modélisation proche du métier, le développement agile avec XP, les patterns de Martin Fowler et même le style de programmation fonctionel, vous devriez adorer ce livre !
Meilleurs commentaires provenant d’autres pays

This book deserves respect for the new paradigm being described and the clear and well structured way it has been described and explained.
Its very possible you may need to have a certain level of experience and knowledge to get the most out of this book, but I think anyone who carefully reads the book, and looks up the things they may not be familiar with, will gain a great understanding of the subject.
Do not expect to be an expert on the first few readings. First read it and understand the core concepts. After that using these ideas and approach on real projects, requires commitment and patience. The author says it's not easy to implement, but it is very effective and provides a solid long term approach.
DDD might not be for all projects, but all software developers, and project managers should be aware of this paradigm and recognise the importance which DDD has.

I’ve now read it once and know I will be reading it cover to cover again. For me it is the right place to start learning about DDD but as Evans admits himself it perhaps lacks some practical guidance on how to go about actually doing DDD for real, in respect to the implementation of software that is as this book is about a philosophy, not technical details. My advice is to try and read it as fluently as it is written, and it is very fluently written, and don’t worry too much that all of its detail is not going in. As I said, this is a difficult subject. Once you’ve read it, read one of the books that takes the material and treats it in a less formal way but a more practical hands on way, I’m doing that right now, then read the Evans again with the context that you’ll get from the less formal book will turbocharge your understanding, well that’s the basis I’m working on :)
Becoming proficient at DDD takes time and work but I suspect the rewards are, as I suggested, game changing.
Already I am looking at code and the way a business is structured to attempt to produce code with the blinkers off and a much clearer picture of the pros and cons of what I see.
For me there are but a few seminal books on writing software and having read this one I’m putting it right up there with the very, very best of them.
Absolutely loved every page.

I understand a bit about domain driven design now but not much. I did give up on the last 100 pages though, I couldn't bear the waste of time anymore. And I did loose focus in a lot of points.
If you told me to read a focussed 20 pages and then asked - "what were they about?" - I couldn't coherently answer 9 times out of 10. There's a lot of filler and complicated language in it.
Even the paragraphs in bold which seemed to convey some meaningful point or summary were usually laughably complicated.
Many on here give this 5 stars though so this may just be me. I applaud anyone who can read it cover to cover and get a lot of value out of it.

However, I find this book so hard to read at the same time. It's a great topic and all developers need to understand this modelling technique properly as this is the basis of the new age of software development. But it lacks analogies and a range of examples to better explain what he means, which means that he uses a very terse descriptive that is hard to process. I think several people should've written it and put in their experiences of the approaches they used and their experiences.
The first quarter of the book is particularly annoying as it talks about what you are about to learn all the time. I think he also means for it to be used as a reference, but it's far too verbose and waffly and not split up enough conceptually to be useful for that.

Great for developing systems in an agile way. DDD requires huge team work and cooperation, courage and tremendous amount of practice.
As with other outstanding books, within many decades it will still be up-to-date, relevant and ignored by many.