Project architecture, using DDD

Question

Requirements
Project should contain 1 main application and some secondary sub applications (which uses the same domain objects, has some shared services, but has some slightly different too - unneeded for main app, therefore - should be separated).

There should exist shared search service (probably, in different DLL) over most of the domain objects, if not all, by customizable search criterias and shared logic for retrieving possible values of those criterias (like sub-search of authors, to retrieve a book by it).

Problem
Does DDD fits here? And if it does, how my project structure should look like? (best format for answer - list of structured DLL`s + some most significant namespaces).

Answer 1

The idea of globally shared domain classes sounds contrary to DDD. Have you read the book?

With globally shared domain classes there's little room left for context maps. Without context maps you'll get little advantage out of DDD in anything but trivial applications.