What is the typical use of each architecture?

Multiprocessor: real-time systems such as traffic control; client-server: business and web systems such as banking

Multiprocessor: banking and e-mail; client-server: traffic control

Both are used only for compilers

What is the main concern of a multiprocessor architecture?

Meeting timing and performance needs by dividing processing

Selling services over the Internet

How do the communications differ?

Multiprocessor: message passing or shared memory; client-server: request-reply over a network

Multiprocessor: HTTP only; client-server: shared memory

Which is more easily scaled by adding servers or clients?

Client-server, whereas multiprocessor is limited by hardware and processor count

Multiprocessor, because it is hardware independent

Year not given · 4 marks

Multiprocessor versus client-server architecture

Short answer

Multiprocessor architecture spreads processes of one system across processors for speed and timing, used in real-time control; client-server separates service providers and users over a network for sharing services. Multiprocessor uses message passing or shared memory with peer processes, while client-server uses request-reply between fixed client and server roles, scaling easily for many users.

Provide brief comparison of multiprocessor and client-server architecture.

A multiprocessor architecture is a system made of several processes that run on different processors, each processor doing a dedicated part of the work (typical in real-time control systems). A client-server architecture organises the system as servers that provide services and clients that request them over a network.

Point	Multiprocessor	Client-server
Basic idea	Processes of one system spread across processors	Services provided by servers, used by clients
Roles	Peer processes, each with a fixed task	Fixed client and server roles
Communication	Message passing or shared memory, often high speed	Request–reply over a network (LAN/Internet)
Allocation	Pre-determined or by a dispatcher	Clients and servers on separate machines by design
Number of users	Usually none or few operators	Many users through many clients
Typical use	Real-time systems: traffic control, process control	Business and web systems: banking, e-mail, file sharing
Scalability	Limited by hardware and processor count	Easy to add servers or clients
Main concern	Meeting timing and performance needs	Sharing data and services among users

Example:

Multiprocessor: a traffic control system with a sensor processor, a traffic-flow processor and a traffic-light control processor.
Client-server: an internet banking system where browsers (clients) use a web server and a database server.

Both are distributed system architectures; multiprocessor focuses on dividing processing for speed and timing, while client-server focuses on sharing services among many users.

✓ Answer checked by Claude Sonnet 5.5

Distributed object versus multiprocessor architecture · Software Engineering, chapter 3
Client-server versus distributed object architecture · Software Engineering, chapter 3
Architecture before specification; client-server · Software Engineering, chapter 3
Architectural design and multiprocessor architecture · Software Engineering, chapter 3
General OS versus real-time OS · Software Engineering, chapter 4
Application framework versus component reuse · Software Engineering, chapter 5
Client/server architecture and FTP operation · Internet and Intranet, chapter 3
Features of client/server architecture · Computer Networks and Security, chapter 1
Client-side versus server-side scripting · Web Technology, chapter 3 · asked 3×
Internet vs WWW; client-server paradigm · Web Technology, chapter 1

All Software Engineering chapter 3 questions →

Multiprocessor versus client-server architecture

Related questions