Second Chapter Flashcards
(42 cards)
Architecture of a System
Structure in terms of specified components aimed to be reliable, manageable, adaptable, and cost-effective.
Middleware Layers
Includes Applications, OS, Middleware, Platform, and Hardware.
Client-Server Model
Client requests services, server provides them.
Two-Tier Architecture
UI and business logic on client, data layer on server.
Three-Tier Architecture
Adds a middle server for translation, metering, or intelligent services.
Null Client
Only captures input and forwards it to server, e.g., X-Terminal.
Thin Client
UI separated from application logic, server handles most computation.
Applet Client
Applets run on client, some business logic and data stored locally.
Fat Client
Most or all application logic on client, server used mainly for storage.
Mobile Code
Downloaded code executed locally, restricted in a sandbox.
Transaction Monitor
Monitors and limits the number of simultaneous client requests.
Proxy Server
Forwards client requests to the appropriate server.
Broker
Returns address of a server offering a requested service.
Trader
Selects server based on required service quality.
Load Balancer
Distributes requests among multiple servers.
Agent
Combines services from different servers for a client.
Vertical Distribution
Different layers (UI, logic, data) on separate physical machines.
Horizontal Distribution
Multiple replicas of services for load distribution.
Peer-to-Peer Architecture
Nodes act as equals, sharing resources directly.
Mobile Agent
Executable code that moves between systems to perform tasks.
Mobile Devices
Devices that move across networks, causing dynamic associations.
Responsiveness
How fast a system responds to user input.
Throughput
How much work is done in a given time.
Load Balancing
Distributing computational tasks across multiple nodes.