StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODomain Driven Design - External Data API as Respository or Service
primarykey
Id
2272601
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-16T11:49:17.013
FavoriteCount
2
LastActivityDate
2010-02-16T17:41:21.230
LastEditDate
LastEditorUserId
0
OwnerUserId
134211
ParentId
0
PostTypeId
1
Score
7
ViewCount
1716
LastEditorDisplayName
text
Body
In a blog application developed using domain driven design a 'Post' entity has a related collection of tag entities. On creating the post (e.g populating the object from the UI) i would like to call a third party API via REST which takes the content of the post and extracts semantic tags (<a href="http://www.opencalais.com/" rel="noreferrer">link text</a>) for association. Main Question : What is the best way to design this... Is it best designed so that the Post entity would call a domain service such as PostServices.GetTags(Postcontent) passing its content and retrieving back a list of tags.? ** PostServices.GetTags would then inteface with the REST API via a further wrapper class. Or should the third party API be wrapped as a repository? Should the function Post.GenerateTags(), should not exist within the domain entity at all? Further questions : 1 : I have also read that it is not good practice to have a domain entity converse with a domain service. Is this true? 2 : Is it ok to get a reference to the PostServices domain service via a factory creation method. e.g... IPostService PostService = ServiceUtil.GetPostService(); return PostService.GetTags(Post.content); 3 : Is it acceptable to have the domain service coupled to a third party api? 4 : Should the domain entity simply just know how to deal with the tags received via the application layer which has called the REST API. Slowly trying to get my head around DDD, however I can't seem to find any examples of how to implement this sort of thing.
Tags
<repository><domain-driven-design><service><infrastructure>
Title
Domain Driven Design - External Data API as Respository or Service
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsjb101
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PODomain Driven Design - External Data API as Respository or Service
 UserUserId
 USMauro Destro
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 PODomain Driven Design - External Data API as Respository or Service
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.