Apedia

Server Service Application Architecture P2p Aspects End Systems

Front Application Architecture: P2P (4 aspects)
Back - No server
- End systems Communicate directly with each other
- Each participant brings both service capacity and service requirements into the network
-> Automatic scaling (Self scalability)
- Management of participants is complex
-> Is often done on a dedicated server (hybrid architecture)

Learn with these flashcards. Click next, previous, or up to navigate to more flashcards for this subject.

Next card: Application architecture main network client server peer-to-peer p2p

Previous card: Application architecture p2p problems isp friendly low upload

Up to card list: Computer Networks TopDownApproach -ENGLISH