This document discusses client-server architecture. It describes the two main types: two-tier with thin or fat clients, and three-tier. In two-tier, processing is either all on the server (thin client) or split between client and server (fat client). Three-tier distributes the presentation, application, and data layers across separate servers for better scalability and performance than two-tier approaches.
Cloud deployment models: public, private, hybrid, community – Categories of cloud computing: Everything as a service: Infrastructure, platform, software - Pros and Cons of cloud computing – Implementation levels of virtualization – virtualization structure – virtualization of CPU, Memory and I/O devices – virtual clusters and Resource Management – Virtualization for data center automation.
Cloud deployment models: public, private, hybrid, community – Categories of cloud computing: Everything as a service: Infrastructure, platform, software - Pros and Cons of cloud computing – Implementation levels of virtualization – virtualization structure – virtualization of CPU, Memory and I/O devices – virtual clusters and Resource Management – Virtualization for data center automation.
Virtualization is a technique, which allows to share single physical instance of an application or resource among multiple organizations or tenants (customers)..
Virtualization is a proved technology that makes it possible to run multiple operating system and applications on the same server at same time.
Virtualization is the process of creating a logical(virtual) version of a server operating system, a storage device, or network services.
The technology that work behind virtualization is known as a virtual machine monitor(VM), or virtual manager which separates compute environments from the actual physical infrastructure.
To view recording of the webinar please use below URL:
http://wso2.com/library/webinars/2015/09/service-oriented-architecture/
This session focuses on
Key architecture goals of SOA
How these can benefit business efficiencies
Popular methods of SOA realization such as web services its standards
Provides a simple and unambiguous taxonomy of three service models
- Software as a service (SaaS)
- Platform as a service (PaaS)
- Infrastructure as a service (IaaS)
(Private cloud, Community cloud, Public cloud, and Hybrid cloud)
Virtualization is a technique, which allows to share single physical instance of an application or resource among multiple organizations or tenants (customers)..
Virtualization is a proved technology that makes it possible to run multiple operating system and applications on the same server at same time.
Virtualization is the process of creating a logical(virtual) version of a server operating system, a storage device, or network services.
The technology that work behind virtualization is known as a virtual machine monitor(VM), or virtual manager which separates compute environments from the actual physical infrastructure.
To view recording of the webinar please use below URL:
http://wso2.com/library/webinars/2015/09/service-oriented-architecture/
This session focuses on
Key architecture goals of SOA
How these can benefit business efficiencies
Popular methods of SOA realization such as web services its standards
Provides a simple and unambiguous taxonomy of three service models
- Software as a service (SaaS)
- Platform as a service (PaaS)
- Infrastructure as a service (IaaS)
(Private cloud, Community cloud, Public cloud, and Hybrid cloud)
Distributed Services Scheduling and Cloud ProvisioningAr Agarwal
This is the presentation for my final year project at NIT Allahabad (2013-14). The purpose of the project is to design a scheduling algorithm for cloud environment with proper resource management.
Subject: Software Architecture Design
Topic: Distributed Architecture
In this presentation, you will learn about design pattern, softawre architecture, distributed architecture, basis of distributed architecture, why distributed architecture, need of distributed architecture, advantages and disadvantages of DA and much more.
Rate my presentation, It's designed graphically.
Microsoft System Center 2012 R2 Overview - Presented by Atidan
2 08 client-server architecture
1. Client-Server Architecture
King Fahd University of Petroleum & Minerals
SWE 316: Software Design & Architecture
Semester: 072
2. Objectives
To understand client-server architecture
2-tier
3-tier
SWE 316 (072) Client-Server Architecture 2
3. Client-Server Architecture
The application is modelled as a set of services that
are provided by servers and a set of clients that use
these services.
Clients know of servers but servers need not know of
clients.
Clients and servers are logical processes.
SWE 316 (072) Client-Server Architecture 3
4. Application Layers
Presentation layer
Concerned with presenting the results of a computation to
system users and with collecting user inputs.
Application processing layer
Concerned with providing application specific functionality
e.g., in a banking system, banking functions such as open
account, close account, etc.
Data management layer
Concerned with managing the system databases.
SWE 316 (072) Client-Server Architecture 4
6. Types of Client-Server Architectures
Two-tier
The three application layers are mapped onto two computer
systems – the client and the server.
Client can be
Thin client; or
Fat client
Three-tier
The three application layers are mapped onto three logically
separate processes that executes on different processors.
SWE 316 (072) Client-Server Architecture 6
7. Thin and Fat Clients
Thin-client model
In a thin-client model, all of the application processing and
data management is carried out on the server. The client is
simply responsible for running the presentation software.
Fat-client model
In this model, the server is only responsible for data
management. The software on the client implements the
application logic and the interactions with the system user.
SWE 316 (072) Client-Server Architecture 7
8. Thin and Fat Clients (Cont’d)
SWE 316 (072) Client-Server Architecture 8
9. Thin-Client Model
Used when legacy systems are migrated to client
server architectures.
The 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.
SWE 316 (072) Client-Server Architecture 9
10. Fat-Client Model
More processing is delegated to the client as the
application processing is locally executed.
Most suitable 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.
SWE 316 (072) Client-Server Architecture 10
12. Three-Tier Architecture
Each of the application layers may execute on a
separate processor.
Allows for better performance than a thin-client model
and is simpler to manage than a fat-client model.
A more scalable architecture - as demands increase,
extra servers can be added.
SWE 316 (072) Client-Server Architecture 12
15. Use of Client-Server Architectures
Architecture Applications
Two-tier C/S Legacy system applications where separating application processing and
architecture with data management is impractical.
thin clients Computationally-intensive applications such as compilers with little or
no data management.
Data-intensive applications (browsing and querying) with little or no
application processing.
Two-tier C/S Applications where application processing is provided by off-the-shelf
architecture with software (e.g. Microsoft Excel) on the client.
fat clients Applications where computationally-intensive processing of data (e.g.
data visualisation) is required.
Applications with relatively stable end-user functionality used in an
environment with well-established system management.
Three-tier or Large scale applications with hundreds or thousand s of clients
multi-tier C/S Applications where both the data and the application are volatile.
architecture Applications where data from multiple sources are integrated.
SWE 316 (072) Client-Server Architecture 15
16. Summary
Tow basic client-server architecture
2-tier
Thin client: all of the application processing and data
management is carried out on the server
Fat clients: run some or all of the application logic.
3-tier
Allows for better performance than a thin-client approach and is
simpler to manage than a fat-client approach.
SWE 316 (072) Client-Server Architecture 16