O'Reilly logo

Implementing Domain-Driven Design by Vaughn Vernon

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Modules in Other Layers

Regardless of the Architecture (4) you choose, you will always have to create and name the Modules of the non-model components of your architecture. Here we discuss some options for a conventional Layered Architecture (4), but ones that can be applied with other architectural styles.

In a typical Layered Architecture used for an application that sports a domain model, you’d stack the layers as follows: User Interface, Application, Domain, Infrastructure. Depending on the kinds of components in each layer, as determined by your application’s needs, the Modules within each layer will vary.

To start, consider the User Interface Layer (14) and the effect of supporting RESTful resources. It is possible that your resources ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required