Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > ASP.NET and ASP > Other ASP.NET > BOOK: Professional ASP.NET Design Patterns
Password Reminder
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Professional ASP.NET Design Patterns
This is the forum to discuss the Wrox book Professional ASP.NET Design Patterns by Scott Millett; ISBN: 978-0-470-29278-5
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional ASP.NET Design Patterns section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old April 14th, 2011, 05:50 AM
Registered User
Join Date: Jan 2011
Posts: 9
Thanks: 0
Thanked 0 Times in 0 Posts
Default Domain Services & Application Services

In my understanding of your book, Application Services are just kind of a facade to translate requests to the domain model.
Domain Services were introduced to be a collaboration of Domain entities (Aggregate Roots): methods that do not really fit into a specific entity.

In term of projects (or layers), the Domain Services would be put in the Domain Model project? Or would they be put into a seperate project?

Application Services have their own project/layer as is visible from your book.

But I get confused about theese services/layers as they seem to have merged somewhere through your book. In the end it seems that the domain services (as I describe them here) are part of the application services. Not sure by heart, but they might have been private. I think I found this in the Agatha demo source code.

Could you please explain:
- the roles of each of these two services?
- where each of these services will be put (project/layer)?
- how they are different/the same/similar in some way?

I greatly appreciate your help and answers on this forum.
Reply With Quote
  #2 (permalink)  
Old September 20th, 2011, 09:17 AM
elbandit's Avatar
Wrox Author
Points: 599, Level: 8
Points: 599, Level: 8 Points: 599, Level: 8 Points: 599, Level: 8
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: May 2007
Location: Southsea, Portsmouth, Hampshire, United Kingdom.
Posts: 107
Thanks: 10
Thanked 17 Times in 15 Posts

Hi Mr Fixxit,

Sorry for the late reply!

Take a look at this blog post on the differences between the domain and application services http://stochastyk.blogspot.com/2008/...en-design.html. I like to think of my application services as being the API into the code, a client interacts with the API (application services) and behind the scences and within the domain model a domain service may use multiple entities and value objects in collaboration to fulfill a business request.

I hope that answers your question, if not please respond and we can talk about the differences further.


Last edited by elbandit; September 21st, 2011 at 04:45 AM..
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Services.ViewModels vs Services.Presentation.Model ? ksouthworth BOOK: Professional ASP.NET Design Patterns 1 April 9th, 2011 11:53 AM
Configuring Your Database for the Application Services guynorton ASP.NET 3.5 Basics 3 February 17th, 2011 06:19 PM

All times are GMT -4. The time now is 12:35 PM.

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.