hits counter Applying Domain-Driven Design and Patterns : With Examples in C# and .NET - Ebook PDF Online
Hot Best Seller

Applying Domain-Driven Design and Patterns : With Examples in C# and .NET

Availability: Ready to download

Patterns, Domain-Driven Design (DDD), and Test-Driven Development (TDD) enable architects and developers to create systems that are robust and maintainable. While the examples in this guide are in C# and .NET, the principles can be used by developers using any language and IDE.


Compare

Patterns, Domain-Driven Design (DDD), and Test-Driven Development (TDD) enable architects and developers to create systems that are robust and maintainable. While the examples in this guide are in C# and .NET, the principles can be used by developers using any language and IDE.

55 review for Applying Domain-Driven Design and Patterns : With Examples in C# and .NET

  1. 5 out of 5

    Cezary Piątek

    It's a book about writing your own ORM. There's nothing about Domain-Driven Design inside. It's a book about writing your own ORM. There's nothing about Domain-Driven Design inside.

  2. 5 out of 5

    Max Savchenko

    Вы уже прочитали DDD Эванса, PoEAA Фаулера, что-нибудь по методологии TDD, с уважением посмотрели на экземпляр книги "Банды Четырёх", который вы иногда берете в руки, чтобы проникнуться мудростью предков, и пытаетесь понять, как это всё применить на практике? Тогда обратите внимание на эту книгу. Тут показан подход конкретного разработчика к конкретной задаче с применением вышеуказанных методик. Эта книга - далеко не библия программиста, но она определенно наведет вас на некоторые мысли. Если Вы уже прочитали DDD Эванса, PoEAA Фаулера, что-нибудь по методологии TDD, с уважением посмотрели на экземпляр книги "Банды Четырёх", который вы иногда берете в руки, чтобы проникнуться мудростью предков, и пытаетесь понять, как это всё применить на практике? Тогда обратите внимание на эту книгу. Тут показан подход конкретного разработчика к конкретной задаче с применением вышеуказанных методик. Эта книга - далеко не библия программиста, но она определенно наведет вас на некоторые мысли. Если есть возможность - читайте в оригинале, ибо переводчик явно перестарался. Продираться через введенные им русские аббревиатуры для общепринятых понятий достаточно сложно.

  3. 5 out of 5

    Pawel Wujczyk

    I really thought this will be about DDD. Unfortunately it wasn't. Author describes very detailed thinking process how his path to particular solution has looked. He starts with whole concept of application classes and others I was very brave and read everything w waiting for some ddd info. But on page 200 he wrote that we right now already described ddd and let's move to other topics. From now on reading book make physical hurt to me. Author describes everything patterns, orm, GUI, database even I really thought this will be about DDD. Unfortunately it wasn't. Author describes very detailed thinking process how his path to particular solution has looked. He starts with whole concept of application classes and others I was very brave and read everything w waiting for some ddd info. But on page 200 he wrote that we right now already described ddd and let's move to other topics. From now on reading book make physical hurt to me. Author describes everything patterns, orm, GUI, database even aspect developing has its own chapter. No no no. Please do not open this.

  4. 5 out of 5

    Johnny

    So far the best book on Domain-Driven Design. Jimmy Nilsson explains in great detail how he comes to the solution and what he thought about and discarded. Seeing how an application grows and understanding all the decisions on the way is a great help to build your own application. Even when you don’t build the same application, the ideas and approaches of the book can guide you. I especially liked the situations when I didn’t agree with the solution. With the explanation in place while he chooses So far the best book on Domain-Driven Design. Jimmy Nilsson explains in great detail how he comes to the solution and what he thought about and discarded. Seeing how an application grows and understanding all the decisions on the way is a great help to build your own application. Even when you don’t build the same application, the ideas and approaches of the book can guide you. I especially liked the situations when I didn’t agree with the solution. With the explanation in place while he chooses it, I could find the points where we differ and see how different approaches result in different outcomes. Designing software is not about right or wrong, but about decisions and their pros and cons.

  5. 4 out of 5

    Rebecca

    I've read Eric Evans' book on domain driven design...but wanted someone's tae on the nuances of actually implementing Eric's domain patterns. This book is OK, but didn't go as far in the directions I might've wanted to see. Although the book says "with examples in C# and .NET) this should not be a barrier to Java folks. It reads just fine. My one disappointment is that it seems to be a walk through Jimmy's experiences without a good summary of issues/implementation concerns. He spent too much ti I've read Eric Evans' book on domain driven design...but wanted someone's tae on the nuances of actually implementing Eric's domain patterns. This book is OK, but didn't go as far in the directions I might've wanted to see. Although the book says "with examples in C# and .NET) this should not be a barrier to Java folks. It reads just fine. My one disappointment is that it seems to be a walk through Jimmy's experiences without a good summary of issues/implementation concerns. He spent too much time on TDD and refactoring, rather than on nuances of certain patterns for my needs.

  6. 5 out of 5

    Tom

    This book is hit and miss. Some parts I liked and found useful, while others seemed dated or I simply disagreed with. It's a good book for gaining exposure to things like domain-driven design, test-driven development, object-relational mapping, and dependency injection, but there are other books that go into deeper detail on each of these subjects. So I'd say check this book out if you're new to these topics but otherwise go to the books that this book references. This book is hit and miss. Some parts I liked and found useful, while others seemed dated or I simply disagreed with. It's a good book for gaining exposure to things like domain-driven design, test-driven development, object-relational mapping, and dependency injection, but there are other books that go into deeper detail on each of these subjects. So I'd say check this book out if you're new to these topics but otherwise go to the books that this book references.

  7. 5 out of 5

    Nuwan

    The Initial part was very impressive. But he sort of starts to discuss so many options and try to pick a simple solution and all of a sudden starts discussing some advanced concepts. I couldnt quite follow the middle part. I guess i will give it another try after reading Patterns of Enterprise Architecture and Domain Driven Design. Not sure whether i ll have time though.

  8. 4 out of 5

    Alena Varkockova

    Too little about DDD and too much about everything else. The focus of the book was quite broad - it touched TDD, Dependency injection and investigated NHibernate and other frameworks. I would much more prefer it to be more focused on the DDD and domain design. If you don't know anything about DDD, I would rather start with the Evans book. Too little about DDD and too much about everything else. The focus of the book was quite broad - it touched TDD, Dependency injection and investigated NHibernate and other frameworks. I would much more prefer it to be more focused on the DDD and domain design. If you don't know anything about DDD, I would rather start with the Evans book.

  9. 5 out of 5

    Topilno

    Creating Web Pages for Dummies

  10. 5 out of 5

    Rejeev Divakaran

    Very good book for architects.

  11. 4 out of 5

    Günter Zöchbauer

    Good introduction with instructive examples

  12. 5 out of 5

    Rabashani

    Great way to enter the DDD world, well written, very descriptive, can be very exhausting because of its length...

  13. 4 out of 5

    Eugene

    Поставлены интереснейшие вопросы из области практического применения DDD. Уже сама постановка вопросов помогла мне в работе. Но вместо ответов – вода.

  14. 5 out of 5

    Chris

    Just okay.

  15. 5 out of 5

    Leandro Zis

  16. 5 out of 5

    Matt Davis

  17. 5 out of 5

    Istvan Reiter

  18. 5 out of 5

    Victor Gonzalez

  19. 4 out of 5

    Pierre-marc

  20. 4 out of 5

    Matt Jackson

  21. 5 out of 5

    Rustam Baekenov

  22. 5 out of 5

    Iain

  23. 5 out of 5

    Robert

  24. 4 out of 5

    Bjoern Rochel

  25. 5 out of 5

    Sm G

  26. 5 out of 5

    Mark Carrier

  27. 5 out of 5

    Dave

  28. 4 out of 5

    Luiz Augusto

  29. 5 out of 5

    John

  30. 4 out of 5

    Alan

  31. 5 out of 5

    Rodrigo Ferreira

  32. 5 out of 5

    Scott

  33. 4 out of 5

    Amy Gilchrist Thorne

  34. 5 out of 5

    notv

  35. 5 out of 5

    Stevi Deter

  36. 5 out of 5

    Dru Sellers

  37. 5 out of 5

    Witt Igahluk

  38. 5 out of 5

    Lionel

  39. 4 out of 5

    Chris

  40. 5 out of 5

    Mike Brown

  41. 4 out of 5

    Christopher

  42. 5 out of 5

    Rob

  43. 4 out of 5

    Jason Stangroome

  44. 4 out of 5

    Shane Milton

  45. 4 out of 5

    Michael

  46. 5 out of 5

    Alex

  47. 5 out of 5

    Petter

  48. 5 out of 5

    Curtis

  49. 5 out of 5

    Chris

  50. 5 out of 5

    Ed

  51. 5 out of 5

    Doug

  52. 4 out of 5

    Jordan

  53. 4 out of 5

    Eugene

  54. 4 out of 5

    Laurent Capin

  55. 4 out of 5

    Brett

Add a review

Your email address will not be published. Required fields are marked *

Loading...