StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
629497
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-10T09:56:11.347
FavoriteCount
0
LastActivityDate
2009-03-10T09:56:11.347
LastEditDate
LastEditorUserId
0
OwnerUserId
20402
ParentId
622735
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
"Network application" is an unclear category covering quite a broad spectrum of possible requirements and designs. By definition, you will have to deal with concurrency and latencies. Robustness is always a challenge: it is all too easy to design a system whose availability is the lowest common denominator of all its hardware and software components. You will have to upgrade the O/S and components of your application: can you live with taking down all of the solution, or do you need some hot/cold standby or even failover capability? Networks fail in exotic ways (at least to us poor pure software guys): you are dependent on so many things you never consider (routers, switches, DNS servers, the temper of that bearded network engineer down the hallway!), and should design the interactions with a pessimistic frame of mind. One warning: don't be too object-oriented when designing distributed applications. Objects have their place in managing software complexity, but the moment you start pushing them on the wire, a huge number of performance and version dependency problems raise their ugly heads. Service oriented architecture is a buzzword, but is useful as a design principle, to a point. The mainframe guys have known this for ages... Two general book recommendations: <ul> <li><a href="http://rads.stackoverflow.com/amzn/click/0201657937" rel="nofollow noreferrer">Designing Concurrent, Distributed, and Real-Time Applications with UML</a> is a few years old, but brings home the challenges you may be facing (especially if you really have hard or soft real-time dependencies somewhere). A bit theoretical, but serves to instil a certain amount of respect for the complexities!</li> <li><a href="http://rads.stackoverflow.com/amzn/click/0321200683" rel="nofollow noreferrer">Enterprise Integration Patterns</a> is a systematic look at the different design options you can use to integrate new and legacy components. </li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow have you structured your network oriented apps?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPontus Gagge
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.