StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3876681
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-06T20:40:36.553
FavoriteCount
0
LastActivityDate
2010-10-06T20:40:36.553
LastEditDate
LastEditorUserId
0
OwnerUserId
39094
ParentId
3856108
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I've put this in a seperate answer as its focus is quite different to my first one. It sounds like you've thought things through and have a good grasp of both your problem and solution. Let me have another crack at (what I think is) your key question... <blockquote> How would you decide... </blockquote> Go back to basics: start with what you know to be true. Have a whiteboard workshop with relevant people from your team(s), in which you need to: <ul> <li>Draw up a list of the relevant constraints.</li> <li>List outcomes you don't want (single big unmanagable application, etc).</li> <li>Also recommended but perhaps not essential: Identify risks and potential impacts (as part of the constraints or undesireable outcomes).</li> <li>List the outcomes you want (sharing data, easy deployment, etc).</li> <li>Prioritise the desireable and undesireable outcomes (very important), and don't be surprised if they change during the course of the debate.</li> </ul> This information should be enough to start establishing a framework for discussion and decison making. There's also some extra things you can do ahead of this workshop (or as part of it depending on the political and social dynamics of your situation). <ul> <li>Identify the goals of the system - both in a "business" sense and an "architectural" sense. (hint: the two should align - or at least not conflict).</li> <li>If there's a well defined Vision for the system or your business that should help (but bear in mind that these don't always exists, and good ones are even rarer).</li> <li>Refer to business / strategic plans for the systems your working on - and consider the market, trends etc. What do you think is likely to happen to the applications in the future? Thinking ahead architecturally isn't the same as YAGNI at a code level, and careful consideration of the future may influence decsions you're making now.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhen to combine multiple apps to simplify their data integration?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAdrian K
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhen to combine multiple apps to simplify their data integration?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.