Jesse Griffin - Domain-Driven Laravel: Learn to Implement Domain-Driven Design Using Laravel

Any source code or other supplementary material referenced by the author in this book is available to readers on GitHub via the books product page, located at www.apress.com/9781484260227 . For more detailed information, please visit http://www.apress.com/source-code .

Domain-driven design (DDD) has been around for almost two decades. During this time, it has seen a sharp increase in interest because of its clear guidelines and tactical strategies and approaches to the problems that you might face when developing applications in any industry, particularly complex ones. It is immensely practical in the real world and has provided solutions for what used to be a lack of any standards or practices suggesting how to best go about solving the underlying businesss domain-specific problemsthe kind you dont see in everyday programming and wouldnt even write if it werent in the context of the domain that your business operates in to achieve a goal (which is probably to make a profit, but may be to service customers, support users, market products, tracking metrics, etc.).

There is a lot of material to be covered when studying either of the two central topics in this book. Laravel and domain-driven design each has its own respective anthologies of blog posts, white papers, books, tutorials, and, of course, practical examples. We will go over some basics of Laravel, but I highly recommend you find some introductory tutorials on the Web so you can get a feel for how the frameworks components fit together. A good resource for this is Laracasts.com. I highly recommend checking out at least the starting episodes; or, if you prefer to read rather than watch/listen, you can always do a quick glerch (thats a Google search) for Intro to Laravel Tutorial.

However it is that you become familiar with the framework on the level that you will need to apply a domain-driven Laravel application is acceptable. Its from this foundational information that we will develop a practical, real-world example later in the book, which will be set up in a controlled environment using DDD as the backbone of our decision-making. Along the way, Ill give you practical advice and potential patterns to look for when attempting to implement a domain-driven Laravel application. My hope is that you will find the material digestible as well as useful in a real-life environment and team.

What I dont expect you to be fully knowledgeable in (or even heard of before) is domain-driven design. I take ample page space in this book to describe and define DDD and lay out the concepts in terms of their application to developing web applications. If you are already familiar with DDDs concepts, thats great! That will flatten the learning curve a bit, but it is not a requirement. I will describe some of the