CSC Unit - 1
CSC Unit - 1
CLIENT SERVER
COMPUTING
Unit I:
Client/Server Computing
UNIT -1 SYLLABUS
Client/Server Computing:
DBMS
DEFINITION
Client/server describes the
PEER-PEER NETWORK
Computer Network in which each
PEER-PEER NETWORK
DIS-ADVANTAGES
No
central server
No
centralization
Lacking
Back
Up
management
Accessibility
and security
CLIENT/SERVER ARCHITECTURE
The Client/Server architecture is based on
hardware and software components that
interacts to form a system. This system
includes three main components:
Clients
Servers
Communication middleware
CLIENT/SERVER ARCHITECTURE
- CLIENT
The client is any computer process
that requests services from the server.
The client is also known as the frontend- application, reflecting the fact
that the end user usually interacts with
the client process.
CLIENT/SERVER ARCHITECTURE
- SERVER
The server is any computer process
providing services to the clients. The
server is also known as the back-end
application, reflecting the fact that the
server
process
provides
the
background services for the client
process.
COMMUNICATION MIDDLEWARE:
MAINFRAME-CENTRIC
CLIENT/SERVER COMPUTING
MAINFRAME-CENTRIC
CLIENT/SERVER COMPUTING
Application
2
Application
3
INTELLIGENT CHARACTER
RECOGNITION (ICR)
ICR technology can be an extremely effective way
to automate the capture of data from a form,
without the need to key.
Current experience with this technique shows
accuracy rates greater than 99.5 percent for
typed forms and greater than 98.5 percent for
handwritten forms.
DOWNSIZING:
The
downward
migrations
of
business
applications are often from mainframes to PCs
due to low costing of workstation.
And also todays workstations are as powerful as
last decades mainframes.
The result of that is Clients having power at the
cost of less money, provides better performance
and then system offers flexibility to make other
purchase or to increase overall benefits.
RIGHTSIZING:
UPSIZING
The bottom-up trend of networking all the standalone PCs and workstations at the department or
work group level.
Early LANs were implemented to share hardware
(printers, scanners, etc.).
But now LANs are being implemented to share
data and applications in addition to hardware.
DOWNSIZING
Mainframes are being replaced by lesser
expensive PCs on networks. This is called
computer downsizing.
Companies implementing business process
reengineering
are
downsizing
organizationally. This is called business
downsizing.
All this would result in hundreds of smaller
systems, all communicating to each other
and serving the need of local teams as well
as individuals working in an organization.
This is called cultural downsizing.
CLIENT/SERVER DEVELOPMENT
TOOLS
By reusing the models previously built to
accomplish integration, we all benefit from cost
and risk reduction.
Reuse as much as possible to save development
costs, reduce risk, and provide the users with a
common "look and feel.
Object Technology based tools for client/server
development demands that proper standards be
put in place to support shared development,
reusable code, and interfaces to existing systems,
security, error handling, and an organizational
standard "look and feel."
ADVANTAGES OF CLIENT/SERVER
COMPUTING
Enhanced Data Sharing
Integrated Services
Sharing Resources Among Diverse
Platforms
Data Interchangeability and
Interoperability
Masked Physical Data Access
Location Independence of Data and
Processing
Centralized Management
ADVANTAGES OF CLIENT/SERVER
COMPUTING
Enhanced Data Sharing - the same data is
available with the same currency to all
designated users.
Integrated Services - In the client/server
model, all information that the client (user) is
entitled to use is available at the desktop. The
desktop toolse-mail, spreadsheet, presentation
graphics, and word processingare available and
can be used to deal with information provided by
corporate application and database servers
resident on the network.
Example
ADVANTAGES OF CLIENT/SERVER
COMPUTING
Sharing Resources Among Diverse Platforms , users may obtain client services and transparent
access to the services provided by database,
communications, and applications servers. ." An
event such as the push of a button, selection of a list
element, entry in a dialog box, scan of a bar code, or
flow of gasoline occurs without the application logic
being sensitive to the physical platforms.
Data Interchangeability and InteroperabilityAlmost all the development tools used for
client/server development expect to reference a
back-end database server accessed through SQL.
ADVANTAGES OF CLIENT/SERVER
COMPUTING
ADVANTAGES OF CLIENT/SERVER
COMPUTING
ADVANTAGES OF CLIENT/SERVER
COMPUTING
SUPPLIER
SUPP
SUPP
STATU
CITY
NUMBER
NAME
PART
PART
COLO
WEIGH
NUMBER
NAME
PART
DELIVERY
SUPP
NUMBER
PART NUMBER
QUANTITY
CITY
SUPP
STATU
CITY
NUMBER
NAME
S1
Jones
20
New York
S2
Black
30
Paris
S3
Smith
10
London
SUPPLIER
PART
PART
COLO
WEIGH
NUMBER
NAME
P1
Desk
Blue
20
London
P2
Monitor
Red
10
Paris
SUPP
PART NUMBER
QUANTITY
P1
200
NUMBER
S1
CITY
PART
DELIVERY
DBMS ARCHITECTURE
The Three-Schema Architecture
The goal of the three-schema architecture is to
separate the user applications and the physical
database
The internal level - describes the physical storage
structure of the database.
The conceptual level -concentrates on describing
entities, data types, relationships, user operations,
and constraints.
The external or view level schema describes the
part of the database that a particular user group is
interested in and hides the rest of the database from
that user group
DBMS ARCHITECTURE
DATA INDEPENDENCE
The concept of data independence- defined as
the capacity to change the schema at one level of a
database system without having to change the
schema at the next higher level
Logical data independence - capacity to change
the conceptual schema without having to change
external schemas or application programs
Physical data independence - the capacity to
change the internal schema without having to
change the conceptual (or external) schemas.
Changes to the internal schema may be needed
because some physical files had to be
reorganized
DATABASE LANGUAGES
DDL - For describing data and data structures a
suitable description tool, a data definition
language
(DDL), is needed. With this help a data scheme
can be defined and also changed later. Typical
DDL operations are:
Creation of tables and definition of attributes
(CREATE TABLE ...)
Change of tables by adding or deleting attributes
(ALTER TABLE )
Deletion of whole table including content (!)
(DROP TABLE )
DATABASE INTERFACES
Application poses with
the help of SQL, a
query to the database
system.
There,
the
corresponding answer
(result
set)
is
prepared and also
with the help of SQL
given back to the
application.
USER INTERFACES
Form-based Interfaces - can fill in all of the
fields and make new entries to the database or
only some of the fields to query the other ones.
Text-based Interfaces
To be able to administrate the database or for other
professional users there are possibilities to
communicate with the DBMS directly in the query
language (in code form) via an input/output
window.
FORM-BASED INTERFACES
TEXT-BASED INTERFACES