Chapter 3. Database Architectures and the Web Transparencies



Similar documents
Chapter 3. Database Environment - Objectives. Multi-user DBMS Architectures. Teleprocessing. File-Server

Interna'onal Standards Ac'vi'es on Cloud Security EVA KUIPER, CISA CISSP HP ENTERPRISE SECURITY SERVICES

Data Management in the Cloud: Limitations and Opportunities. Annies Ductan

Cloud Compu)ng in Educa)on and Research

ICS 434 Advanced Database Systems

Tier Architectures. Kathleen Durant CS 3200

Clusters in the Cloud

Project Overview. Collabora'on Mee'ng with Op'mis, Sept. 2011, Rome

ITS Strategic Plan Enabling an Unbounded University

Data Center Evolu.on and the Cloud. Paul A. Strassmann George Mason University November 5, 2008, 7:20 to 10:00 PM

CHAPTER 8 CLOUD COMPUTING

Solving today's challenges with Oracle SOA Suite, and Oracle Coherence

Networked Virtual Spaces and Clouds. Magda El Zarki UC Irvine

Security Issues in Cloud Computing

Introduc)on to the IoT- A methodology

Return on Experience on Cloud Compu2ng Issues a stairway to clouds. Experts Workshop Nov. 21st, 2013

RESTful or RESTless Current State of Today's Top Web APIs

Understanding Cloud Compu2ng Services. Rain in business success with amazing solu2ons in Cloud technology

Project Por)olio Management

Experiments on cost/power and failure aware scheduling for clouds and grids

Migrating to Hosted Telephony. Your ultimate guide to migrating from on premise to hosted telephony.

The Role of Nutanix in the Public /Private / Hybrid Cloud Spectrum

benefit of virtualiza/on? Virtualiza/on An interpreter may not work! Requirements for Virtualiza/on 1/06/15 Which of the following is not a poten/al

Motivation Definitions EAI Architectures Elements Integration Technologies. Part I. EAI: Foundations, Concepts, and Architectures

What is Middleware? Software that functions as a conversion or translation layer. It is also a consolidator and integrator.

Objectives. Distributed Databases and Client/Server Architecture. Distributed Database. Data Fragmentation

CS 5150 So(ware Engineering System Architecture: Introduc<on

Cloud Computing and Government Services August 2013 Serdar Yümlü SAMPAŞ Information & Communication Systems

So#ware Defined Radio (SDR) Architecture and Systems Issues

Service Oriented Architecture

Distributed System Principles

Case Studies in Solving Testing Constraints using Service Virtualization

CS 4604: Introduc0on to Database Management Systems

資 料 倉 儲 (Data Warehousing)

Introduction to Engineering Using Robotics Experiments Lecture 18 Cloud Computing

EAI. Op'mizing your integra'on cost. Sunil Kumar Pandey Persistent Systems Ltd. Session: 20188

Connec(ng to the NC Educa(on Cloud

SOA and Cloud in practice - An Example Case Study

Contact Center Rou,ng Strategies for Improving Customer Experience

Open- Xchange OXtender for cpanel

Overview of SOTI.

JOURNAL OF OBJECT TECHNOLOGY

Texas Digital Government Summit. Data Analysis Structured vs. Unstructured Data. Presented By: Dave Larson

Cloud Compu)ng: Overview & challenges. Aminata A. Garba

A Study on Service Oriented Network Virtualization convergence of Cloud Computing

IT Infrastructure and Emerging Technologies

SCADA Cloud Computing

Distributed Systems Architectures

VALLIAMMAI ENGINEERING COLLEGE SRM NAGAR, KATTANKULATHUR DEPARTMENT OF COMPUTER APPLICATIONS SUBJECT : MC7502 SERVICE ORIENTED ARCHITECTURE

Telephone Related Queries (TeRQ) IETF 85 (Atlanta)

Effec%ve AX 2012 Upgrade Project Planning and Microso< Sure Step. Arbela Technologies

Big Data. The Big Picture. Our flexible and efficient Big Data solu9ons open the door to new opportuni9es and new business areas

Leveraging the Hybrid Cloud For Complete Data Protec:on. Private Public Managed

Chapter 2 Database System Concepts and Architecture

Graduate Systems Engineering Programs: Report on Outcomes and Objec:ves

ORACLE APPLICATION EXPRESS 5.0

Cluster, Grid, Cloud Concepts

HOLACONF - Cloud Forward 2015 Conference From Distributed to Complete Computing HAMZA. in collaboration SAHLI with

Service Oriented Architectures

A Generic Database Web Service

Legacy Archiving How many lights do you leave on? September 14 th, 2015

Modernizing EDI: How to Cut Your Migra6on Costs by Over 50%

Cloud Compu)ng. Yeow Wei CHOONG Anne LAURENT

Microsoft Training and Certification Guide. Current as of December 31, 2013

How the ersa Problem became the ersa Solu3on. Why a network and network security is impera3ve for ersa s NeCTAR cloud. Paul Bartczak Infrastructure

Business Con*nuity with Docker

SDN Controller Requirement

Transcription:

Week 2: Chapter 3

Chapter 3 Database Architectures and the Web Transparencies

Database Environment - Objec<ves The meaning of the client server architecture and the advantages of this type of architecture for a DBMS. The difference between two- <er, three- <er and n- <er client server architectures. About cloud compu<ng and data as a service (DaaS) and database as a service (DBaaS). SoKware components of a DBMS. 3

Database Environment - Objec<ves The purpose of a Web service and the technological standards used to develop a Web service. The meaning of service- oriented architecture (SOA). The difference between distributed DBMSs, and distributed processing. The architecture of a data warehouse. About cloud compu<ng and cloud databases. The sokware components of a DBMS. 4

Mul<- user DBMS Architectures The common architectures that are used to implement mul<- user database management systems: Teleprocessing File- Server Client- Server 5

File- Server File- server is connected to several worksta<ons across a network. Database resides on file- server. DBMS and applica<ons run on each worksta<on. Disadvantages include: Significant network traffic. Copy of DBMS on each worksta<on. Concurrency, recovery and integrity control more complex. 6

Teleprocessing One computer with a single CPU and a number of terminals. Processing performed within the same physical computer. User terminals are typically dumb, incapable of func<oning on their own, and cabled to the central computer. 7

File- Server Architecture In a file- server environment, the processing is distributed about the network, typically a local area network (LAN). 8

Tradi<onal Two- Tier Client- Server Client (<er 1) manages user interface and runs applica<ons. Server (<er 2) holds database and DBMS. Advantages include: wider access to exis<ng databases; increased performance; possible reduc<on in hardware costs; reduc<on in communica<on costs; increased consistency. 9

Tradi<onal Two- Tier Client- Server 10

Alterna<ve Client- Server Topologies 11

Tradi<onal Two- Tier Client- Server 12

Three- Tier Client- Server 13

Web 3- Tier 14

Mobile 3- Tier 15

n- Tier Client- Server (e.g. 4- Tier) The three- <er architecture can be expanded to n <ers, with addi<onal <ers providing more flexibility and scalability. Applica<ons servers host API to expose business logic and business processes for use by other applica<ons. 16

N- Tier 17

First Genera3on web 18

Second Genera3on web 19

RIA Web Applica<ons HTML5 + CSS3 + JavaScript + JavaScript frameworks jquery jquery Mobile AngularJS Sencha EXT- JS SmartClient D3 Dart GWT (Google Web Toolkit) JavaFX 20

Middleware Middleware is a generic term used to describe sokware that mediates with other sokware and allows for communica<on between disparate applica<ons in a heterogeneous system. The need for middleware arises when distributed systems become too complex to manage efficiently without a common interface. 21

22

Middleware Remote Procedure Call (RPCs) Client makes calls to procedures running on remote systems. Message Oriented Middleware (MOM) Messages sent to the client are collected and stored un3l they are acted upon, while the client con3nues with other processing. Object Request Broker (ORB) This type of middleware makes it possible for applica3ons to send objects and request services in an object- oriented system. SQL- oriented Data Access middleware between applica3ons and database servers. 23

The Na<onal Ins<tute of Standards and Technology (NIST) provided a defini<on. Defined as A model for enabling ubiquitous, convenient, on- demand network access to a shared pool of configurable compu<ng resources (e.g. networks, servers, storage, applica<ons, and services) that can be rapidly provisioned and released with minimal management effort or service provider interac<on. 24

Transac<on Processing Monitor as middle <er of 3- <er client- server 25

Web Services and Service- Oriented Architectures Web service is a sokware system designed to support interoperable machine- to- web service machine interac<on over a network. Web services share business logic, data, and processes through a programma<c interface across a network. Developers can add the Web service to a Web page (or an executable program) to offer specific func<onality to users. 26

Web Services and Service- Oriented Architectures UDDI (Universal Discovery, Descrip3on, and Integra3on) protocol is a plaworm independent, XML- based registry for businesses to list themselves on the Internet. 27

Distributed DBMSs 28

Data Warehousing A data warehouse was deemed the solu<on to meet the requirements of a system capable of suppor<ng decision making, receiving data from mul<ple opera<onal data sources. 29

Cloud Compu<ng The Na<onal Ins<tute of Standards and Technology (NIST) provided a defini<on. Defined as A model for enabling ubiquitous, convenient, on- demand network access to a shared pool of configurable compu<ng resources (e.g. networks, servers, storage, applica<ons, and services) that can be rapidly provisioned and released with minimal management effort or service provider interac<on. 30

Cloud Compu<ng Key Characteris<cs On- demand self- service Consumers can obtain, configure and deploy cloud services without help from provider. Broad network access Accessible from anywhere, from any standardized placorm (e.g. desktop computers, laptops, mobile devices). 31

Data Warehousing / icloud 32

Data Warehousing / icloud 33

Cloud Compu<ng Comparison of Services Models 34

Cloud- based database solu<ons Mul<- tenant cloud database- shared server, separate database server process architecture. 35

Cloud- based database solu<ons Mul<- tenant cloud database- shared DBMS server, separate databases. 36

Cloud- based database solu<ons Mul<- tenant cloud database- shared DBMS server, separate databases. 37

Cloud- based database solu<ons Mul<- tenant cloud database shared database, separate schema architecture. 38

Components of a DBMS Query processor. Database manager (DM) File manager DML Recovery manager Buffer manager 39

Components of a DBMS 40

Components of Database Manager (DM) 41

In Class Qs 3.1 3.5 42

HWK 3.7 3.14 43