Scribd
Upload
42 views

What Is Distributed Software Architecture?

Distributed architecture involves components running on different platforms that cooperate over a network to achieve a common objective. It allows for information processing to be distributed across multiple independent computers. Common distributed architectures include client-server, where clients request services from servers, and multi-tier architectures, where functions are separated across logical tiers like presentation, application, and data. Middleware supports the development and execution of distributed applications by providing a buffer between components.

Uploaded by

Imran Haider
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
42 views

What Is Distributed Software Architecture?

Distributed architecture involves components running on different platforms that cooperate over a network to achieve a common objective. It allows for information processing to be distributed across multiple independent computers. Common distributed architectures include client-server, where clients request services from servers, and multi-tier architectures, where functions are separated across logical tiers like presentation, application, and data. Middleware supports the development and execution of distributed applications by providing a buffer between components.

Uploaded by

Imran Haider
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Distributed Architecture

What is Distributed software architecture?


In distributed architecture, components are presented on different platforms
and several components can cooperate with one another over a
communication network in order to achieve a specific objective.
Objectives:


In this architecture, information processing is not confined to a single
machine rather it is distributed over several independent computers.A
lot of computers combined togather to perform specific task.


A distributed system can be demonstrated by the client-server
architecture which forms the base for multi-tier architectures;
alternatives are the broker architecture such as CORBA, and the
Service-Oriented Architecture (SOA).
There are several technology frameworks to support distributed
architectures, including .NET, J2EE, CORBA, .NET Web services,
AXIS Java Web services, and Globus Grid services.


Middleware is an infrastructure that appropriately supports the
development and execution of distributed applications. It provides a
buffer between the applications and the network.


It sits in the middle of system and manages or supports the different
components of a distributed system. Examples are transaction
processing monitors, data convertors and communication controllers
etc
Client-Server Architecture
he client-server architecture is the most common distributed system
architecture which decomposes the system into two major subsystems or
logical processes −


Client − This is the first process that issues a request to the second
process i.e. the server.
Server − This is the second process that receives the request, carries
it out, and sends a reply to the client.

Client-server Architecture can be classified into two models based on the


functionality of the client −
Thin-client model

A thin client is a stateless, fanless desktop terminal that has no hard drive. All
features typically found on the desktop PC, including applications, sensitive
data, memory, etc., are stored back in the data center when using a thin
client.
The client is simply responsible for running the presentation software.


Used when legacy systems are migrated to client server architectures
in which legacy system acts as a server in its own right with a
graphical interface implemented on a client
A major disadvantage is that it places a heavy processing load on both
the server and the network.

Thick/Fat-client model

A thick client (sometimes called a fat client) is a form of client-server


architecture. Specifically, it is a networked computer system with most
resources installed locally, rather than distributed over a network.


Most appropriate for new C/S systems where the capabilities of the
client system are known in advance
More complex than a thin client model especially for management.
New versions of the application have to be installed on all clients.
Multi-Tier Architecture (n-tier Architecture)
N-tier architecture is also called multi-tier architecture because the software is
engineered to have the processing, data management, and presentation
functions physically and logically separated.

The most general use of multi-tier architecture is the three-tier architecture. A


three-tier architecture is typically composed of a presentation tier, an
application tier, and a data storage tier and may execute on a separate
processor.

Presentation Tier
Application Tier (Business Logic, Logic Tier, or Middle Tier)
Data Tier
References:

https://www.tutorialspoint.com/software_architecture_design/distributed_architect
ure.htm
https://www.britannica.com/technology/client-server-architecture
http://www.devonit.com/thin-client-education
https://whatis.techtarget.com/definition/fat-client-thick-client#:~:text=A%20thick
%20client%20(sometimes%20called,than%20distributed%20over%20a%20network.
https://stackify.com/n-tier-architecture/#:~:text=N%2Dtier%20architecture%20is
%20also,functions%20physically%20and%20logically%20separated.&text=The
%20%E2%80%9CN%E2%80%9D%20in%20the%20name,to%20any%20number
%20from%201.

You might also like