Chapter 1, A Typical JavaScript Project, introduces a typical business application and how it is developed. It shows how domain-driven design can help steer clear of common issues during the development to create a more problem-tailored application.

Chapter 2, Finding the Core Problem, shows how we can effectively explore an application's problem domain and identify the most important aspects to work on.

Chapter 3, Setting up a Project for Domain-driven Design, focuses on setting up a structure for the project that is ready to grow. It not only shows how we can lay out files and folders, but also creates the right testing and build environments.

Chapter 4, Modelling the Actors, shows how a project grows using object-oriented techniques together with domain-driven design to really isolate the domain. We also tackle one of the hardest problems of computer science, naming.

Chapter 5, Classification and Implementation, is all about the language we use in domain-driven design to make the project understandable and readable. We look at the relationship between domains and sub-domains, and then drill further down into the core of domain objects.

Chapter 6, Context Map – The Big Picture, is about not only growing the application from a technical perspective, but also from an organizational perspective. We talk about organizing the different parts that form the application as a whole, either as separate parts or as interlinked pieces.

Chapter 7, It's Not All Domain-driven Design, talks about fitting domain-driven design into the space of development techniques, talking about what problems fit where. We also talk about influences such as object-orientation, domain-specific languages, and more.

Chapter 8, Seeing It All Come Together, is about how our project fits into a space of projects in JavaScript, referring back to the beginning. We also look at alternative choices for frameworks and development styles.

The book uses JavaScript as the language of choice throughout. In order to provide a consistent runtime environment, JavaScript Node.js is used throughout the book as the runtime. Other tools from the Node.js ecosystem are used as well, mainly npm as the package manager. To work with the code in the book, you need a version of Node.js, which is available for Windows, Macintosh OS, and Linux from the Node.js website http://nodejs.org/. It comes packaged with npm. For editing code, I recommend using your favorite text editor or IDE. If you don't have one, maybe give Sublime Text or Vim a try, these are also available for Windows, Macintosh OS, and Linux.

This book assumes a certain familiarity with the JavaScript language. It is targeted at JavaScript developers, who are faced with the problems of growing applications, and the problems that arise from the growth. It provides a practical approach to domain-driven design and focuses on the parts that are the most useful in day-to-day development.

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "At the time of the writing, the currently active version was node.js 0.10.33."

A block of code is set as follows:

var Dungeon = function(cells) {
  this.cells = cells
  this.bookedCells = 0
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

var dungeons = {}
Dungeon.find = function(id, callback) {
  if(!dungeons[id]) {
    dungeons[id] = new Dungeon(100)
  }

Any command-line input or output is written as follows:

$ npm install –g express

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Clicking on the Next button moves you to the next screen."

Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of.

To send us general feedback, simply e-mail <[email protected]>, and mention the book's title in the subject of your message.

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.