Gratuit avec l’offre d'essai
-
Domain Driven Design
- A Comprehensive Beginner’s Guide to Learn How to Easily Implement Domain Driven Design
- Lu par : Dave Wright
- Durée : 3 h et 54 min
Échec de l’élimination de la liste d'envies.
Impossible de suivre le podcast
Impossible de ne plus suivre le podcast
Acheter pour 13,42 €
Aucun moyen de paiement n'est renseigné par défaut.
Désolés ! Le mode de paiement sélectionné n'est pas autorisé pour cette vente.

Vous êtes membre Amazon Prime ?
Bénéficiez automatiquement de 2 livres audio offerts.Bonne écoute !
Description
Let's address the critical question right off the bat: why do you have to read this book? If you have a knack for software development, please do not throw this opportunity away. Now is your chance to become an expert.
When reliable approaches function without domain-driven design, such denial of this technology or market environment become costly. Even medium-sized mobile apps benefit immensely from the structure of the application of this amazing architecture.
Too often, developers only chuck lines of code at problems that can be fixed with vital structural changes. Domain Driven Design does a great job in incorporating industry conditions into aspects of software development. For example, this book focuses on how the accuracy of the model driven design involves constant communication in multiple occasions, and developers separated by team/locations do not participate in continual contact.
Recommendations are provided on segmenting the software as a consequence of the market reality. This will enable efficient modeling across independent teams. Such approaches also take political problems within groups into consideration, as well as the collaboration of overburdened departments and legacy systems.
In fact, the book points out a claim that many developers are protesting against, but this is particularly true: Not all developers in a group need to pursue the same approach. The claim does not mean that developers are expected to use arbitrary solutions; it implies that programmers are not allowed to tie each other to a unique solution if they can address fundamentally different problems.
Two teams working on your device may have a "user" category and may have a consumer category. But perhaps, Team A wants a customer as part of the payment process, or Team B needs a customer as part of a support system. Should we use all departments in the same customer class? Perhaps not. Maybe, they should have consumer-grade billing and support. Then, each consumer includes only the actions they need for the job they have to do.
Nevertheless, you will find considerable resistance to solutions like this. Critics are complaining of "unnecessary duplication", but in fact, it is not replication, and it is needed. For similar reasons, the book tends to support the possibility of locking "bounded context."
Furthermore, this beginner's guide is right on the money when it comes to structuring code in a manner that allows for business structure. The book also emphasizes concentration and project management in a sense that also helps teams to operate independently without the dictator and the design.
Autres livres audio du même :
Ce que les auditeurs disent de Domain Driven Design
Moyenne des évaluations utilisateurs. Seuls les utilisateurs ayant écouté le titre peuvent laisser une évaluation.Commentaires - Veuillez sélectionner les onglets ci-dessous pour changer la provenance des commentaires.
-
Global
-
Interprétation
-
Histoire

- H.Sheffield
- 06/02/2020
Google translate much?
This whole book is so bizarre. It’s nearly a direct reading from Eric Evans’ book, but stilted and awkward as if it was put through google translate. Huh?
3 personnes ont trouvé cela utile
-
Global
-
Interprétation
-
Histoire

- kiril okun
- 24/12/2021
All the 5 star reviews are suspiciously similar
After getting conned into buying this nonsense i've taken a second look at the 5 star reviews and realized that many are very similar in their writing and in that they praise the exact same thing that is completely missing: clarity of explanation and language. Not to mention that they all seem to come from a particular nation known for review farms. Coincidence?
2 personnes ont trouvé cela utile
-
Global
-
Interprétation
-
Histoire

- JP
- 12/02/2020
Incomprehensible gibberish
Not sure how this book earned high marks from reviewers. I purchased the Audible version. The language is incoherent, as if translated to English. Stick with books written by Vaughn Vernon.
2 personnes ont trouvé cela utile
-
Global
-
Interprétation
-
Histoire

- Ajinke
- 18/02/2020
Must listen to it
I am so excited to have received this book! Even more excited to dive in and start listening it tonight again.
1 personne a trouvé cela utile
-
Global
-
Interprétation
-
Histoire

- zahiaa
- 29/02/2020
best concept
The concepts are well presented and very easy to access. One could implement these ideas in virtually any part of their life.
-
Global
-
Interprétation
-
Histoire

- Cashel
- 28/02/2020
Beginners guide
One of the better DESIGN books that I've read in a long time. The author also has a lot of other bonus content which you can download from his website.
-
Global
-
Interprétation
-
Histoire

- Arshi.af
- 28/02/2020
enjoyed
I enjoyed the writer's methodology. Everything in this book unquestionably makes sense. I discovered this book in all respects help.
-
Global
-
Interprétation
-
Histoire

- Bayoona
- 21/02/2020
Highly recommend
Great job by the author. This the best opportunity for me to learn about this type of interesting books.
-
Global
-
Interprétation
-
Histoire

- Aila
- 21/02/2020
Best
Very practical, easy to follow instructions. Just a good book to have if you work with domain driven design.
-
Global
-
Interprétation
-
Histoire

- Jadeja
- 17/02/2020
Best
The concepts are well presented and very easy to access. One could implement these ideas in virtually any part of their life.