• Non ci sono risultati.

Database co op eration: classication and middlew are to ols

N/A
N/A
Protected

Academic year: 2021

Condividi "Database co op eration: classication and middlew are to ols"

Copied!
18
0
0

Testo completo

(1)

Database co op eration: classi cation and middlew are to ols

PaoloAtzeniUniversita'diRomaTre,Italyincooperationwith

Luca Cabibb o

and

Gianni Mecca

[atzeni,cabibbo,mecca]@inf.uniroma3.ithttp://poincare.inf.uniroma3.it:8080

PaoloAtzeni|CAiSE*971

Outline

introduction

classi cationcriteria

classi cation

architecturaltechniques

architecturesandmiddlewaretools

conclusionanddiscussion

PaoloAtzeni|CAiSE*972

introduction

classi cationcriteria

classi cation

architecturaltechniques

architecturesandmiddlewaretools

conclusionanddiscussion

PaoloAtzeni|CAiSE*973

Focus

databasecooperation

bridgethegapbetweenmethodologiesandtools

classi cationofapplications

implementationarchitectures

PaoloAtzeni|CAiSE*974

(2)

Sp eci c framew ork

contractwithAIPA(NationalAuthorityinItalyforComputinginthePublicAdministration)

AIPAispromotingaNationalnetwork:\theInternetoftheItaliangovernmentandadministrationoces"

AIPAwantedtogiveguidelinestothevariousbranchesonhowtoexploitthenetworkandpromotecooperation

PaoloAtzeni|CAiSE*975

General framew ork

theneedforintegratingapplicationsariseseverywhere,stimulatedbythedevelopmentofnetworks

{

integration(orinteraction)ofcomponentsdevelopedseparately,fortechnical,organizational,ortemporalreasons

{

cooperationofpreviouslyseparateprocesses(processreengineering)

{

cooperationofindependentcompanies(ormergesthereof)

PaoloAtzeni|CAiSE*976

Levels of interaction



connectivit y

:systemsandnetworksexchangepacketsofinformation(inInternet,withTCP/IP)



interop erabilit y

:systemsandnetworksinteractbymeansofstandardservices(inInternet,standardprotocolsaboveTCP/IP)



co op eration

:applicationsoverdi erentsystemsinteractwithoneanother;attheextremelevel,distributedapplicationscoordinateexistinglocalapplications

PaoloAtzeni|CAiSE*977

Interop erabilit yservices

 letransfer(ftp)

virtualterminal(telnet)

electronicmail(X.400orESMTP/MIME)

directoryservice(X.500)

WWW(http)

PaoloAtzeni|CAiSE*978

(3)

Co op eration of Info rmation Systems

requiresthatthecooperatingsystemso erapplicationservices

ithappenswhensystemsmakeuseofapplicationserviceso eredbyothersystems

cooperatingsystems\sharegoals"

amajorfeature:\continuouschange"

PaoloAtzeni|CAiSE*979 introduction

classi cationcriteria

classi cation

architecturaltechniques

architecturesandmiddlewaretools

conclusionanddiscussion

PaoloAtzeni|CAiSE*9710

First level classi cation

twoformsofcooperation(noclearcut,indeed)



data-o riented

:datainasystemisvisible/accessibletoothersystems



pro cess-o rie nted

:systemso erservices,exchangemessages,(ordata,documents),triggeractivities

PaoloAtzeni|CAiSE*9711

Pro cess-o riented co op eration

exchangeofmessagesanddocuments;simplecooperation;satis edwithinteroperabilityservices

structuredexchangeofmessagesanddocuments;morecomplexcooperation;satis edwithEDIservicesandsophisticatedmailers

cooperatingprocesses:composedofactivitiesofindependentsubjectsthatcooperate;complexcooperation;solution(?):work owmanagementsystems

PaoloAtzeni|CAiSE*9712

(4)

Co op eration: requirements

actualcooperationinvolvessystemsthatare

distributed

heterogeneous

autonomous

PaoloAtzeni|CAiSE*9713

Distribution

cooperationmeansthatwehavemultiplesystems;datacooperationmeansthatwehavemultipledatabasesthathandledata

asopposedtousualdistributeddatabases,heredistributionisnotadesigndecision,butafact,duetothepreexistenceofthecooperatingdatabases

distributionmayrangefromdi erentdatabasesonthesamemachinetodatabasesspreadoverageographicnetwork

PaoloAtzeni|CAiSE*9714

Heterogeneit y

manyaspects

di erencesinthecomputingenvironment(hardware,operatingsystem,networksoftware)

di erencesinthedatabasemanagementsystem:

{

di erentdatamodel(relational,hierararchical,OO, les,...)

{

detailsinthesamedatamodel(versionsoftherelationalmodel:types,constraints,...)

{

di erentlanguages(SQLandQBE,versionsofSQL,...)

semanticheterogeneity:di erencesinthemeaningofdata

PaoloAtzeni|CAiSE*9715

Autonomy

Absenceofacommon(orcoordinated)controloverthevarioussystems:\distributionofcontrol"Technicalaspects:

designautonomy:thevarioussystemsarebuiltindependently,withdi erentchoicesformanyaspects(thusinducingheterogeneity)

serviceautonomy:decisiononifandhowcooperationisestablished(whatservicesareo ered)

executionautonomy:cooperationdoesnotinterferewith\private"operations;cooperatingoperationsareexecutedunderlocalcontrolPaoloAtzeni|CAiSE*9716

(5)

Distribution, Heterogeneit y,Autonomy

Classi cationcriteria?No,sinceinthecooperationweshouldbereadytotacklehighlydistributed,heterogeneous,andautonomoussystemsConstraints?Probablyyes,atleastintheworstcaseDe cienciestoovercome?Possibly,ifthereissomecoordinatingauthority:cooperationcanstimulatereengineering(reducingthedegreesofheterogeneity,autonomy,anddistribution)

PaoloAtzeni|CAiSE*9717

The \ideal goal"

completedatabasefeaturesinanintegratedframework(inordertodevelopecient/e ectivecooperativeapplications):

{

\integrateddatabase"

{

queryandtransactioncapabilities

{

absenceofredundancy(andinconsitency)

ho wever

currenttechnologydoesnotreallysupportthis(atbestrequirese ortandmoney)

PaoloAtzeni|CAiSE*9718

New classi cation criteria for data-o riented co op eration

degreeoftransparencyofcomponentdata

complexityofoperations

levelofliveliness(orup-to-dateness,asopposedtoobsolescenceorlatency)ofdata

PaoloAtzeni|CAiSE*9719

Transpa rency

measures the need for hiding distribution and heterogeneit y of comp onent systems in adata-o riented co op eration

+integrationofcomponentdatabases:thecooperativeapplicationneedstoseeone(virtual)database,o eringanintegratedschema(orsetoffunctions)

-itisacceptablethateachcomponentdatabaseo ersasetofservices:eachcooperativeapplicationisresponsibleforaccessing,integrating,transformingthevariouspiecesofdata

PaoloAtzeni|CAiSE*9720

(6)

Complexit yof op erations

measures the need for co ordination in the execution of op erations (queries and transactions)

+complexoperations(queriesandupdates):joinoflargerelations(fromdi erentdatabases)ortransactionswithmultipleupdatesindi erentdatabases;requirenontrivialmanagement

-simpleoperations(forexampleread-only,orlocal);donotrequirespeci csupport

PaoloAtzeni|CAiSE*9721

Liveliness of data

measures the need for actual availabilit yof current data

+on-lineaccesstotheprimarycopyofdata:\accessofactualdatawhereitis"|theoriginalgoalofintegrateddatabases?

-accesstocopies,withacontrolleddegreeofobsolescenceNote:thiscriterioncanbeappliedindependentlytothevariouscomponents

PaoloAtzeni|CAiSE*9722

introduction

classi cationcriteria

classi cation

architecturaltechniques

architecturesandmiddlewaretools

conclusionanddiscussion

PaoloAtzeni|CAiSE*9723

A classi cation for data-o riented co op eration

thereisnoneedtoconsiderallcombinations:

{

thecriteriaarenotindependent:ahighdegreeofcomplexityrequiresanintegrationinfrastructure,thatis,itrequiresahighdegreeoftransparency;

{

somecasesaremarginalorsubsumed

majorclasses

{ multidatabases

:transparency,complexity,up-to-dateness

{ data warehouses

:transparency,complexity

{ local info rmation systems with external data

:varyingdegreeofup-to-datenessPaoloAtzeni|CAiSE*9724

(7)

Multidatabases

intheidealcase,thereisahighdegreeoftransparency,complexity,up-to-dateness

thereisa

global

systemthatintegratesservices:livedataisdirectlyaccessedinatransparentandecientway

methodologiesandtoolsforintegration(ofschemes,data,languages)areneeded

PaoloAtzeni|CAiSE*9725

Multidatabase

DBDBDB LocalMgrLocalMgrLocalMgr PPPPPPPP client

 clientExporterExporterExporter , , , , , , , ,

@ @ @ @ @ @ @ @ GlobalMgr HHHHHHH

 clientclient

PaoloAtzeni|CAiSE*9726

Five-level architecture for federated database systems

DB rrrDB LocalSchemaLocalSchema HHHHHH

 clientclientComponentSchComponentSch @ @@

, ,, ExportSchemaExportSchemaExportSchema   





XXXXXXXXXXXXXXXXX

HHHHHHHHH FederatedSchemaFederatedSchema @ @ @ @@

HHHHHHHHH

, , , ,, ExternalSchExternalSchExternalSch client

@ @ @@ client

@ @ @@ client

, , ,, client

PaoloAtzeni|CAiSE*9727

Three-level architecture for traditional database systems

DB InternalSchema LogicalSchema HHHHHHHH

 ExternalSchemaExternalSchemaExternalSchema @ @@ , ,, clientclientclientclient

PaoloAtzeni|CAiSE*9728

(8)

Data W arehouse

dataareintegratedo -lineandstoredinanewdatabase(the

data warehouse

)

typicalapplications:decisionsupport(formarketing,sales, nancialanalysis),investigation,summarization

greatinterestinthemarketplace(OLAP,datacube,multidimensionaldatabases,extractors,replicators)

PaoloAtzeni|CAiSE*9729

Data W arehousing app roach

DBDBDB LocalMgrLocalMgrLocalMgr PPPPPPPP client

 clientExtractorExtractorExtractor 

XXXXXXXX Integrator DataWarehouse DWMgr HHHHH

 clientclient

PaoloAtzeni|CAiSE*9730

OPERATIONALDBDATAWAREHOUSEapplicationorientedsubjectorientedservestheoperationlevelservesthemanagersleveldetaileddataalsosummarized,withtimeseriesaccessedaunitatatimeaccessedasetatatimenonredundantdataredundantdatacurrentvaluesovertimeand/ortimeseriesvarieswithtimeisnotupdatedusedstandardlyusedcasuallyrequirementsknownapriorinotknownaprioriperformancesensitiveperformancerelaxedtransactiondrivenanalysisdrivenconcurrencycontrolneedednoneedhighavailabilityrelaxedavailabilitystaticstructure exiblestructuresmallamountofdataperoplargeamountofdata

PaoloAtzeni|CAiSE*9731

Advantages of W arehouses wrt Multidatabases

on-lineaccessinqueryprocessingcanbeslow:itcompeteswithoperationalactivities

primarysourcesmaybeunavailable

complexrestructuringandaggregationmaybeneeded(andprimarysourcesmaybeheterogeneous)

PaoloAtzeni|CAiSE*9732

(9)

Advantages of Multidatabases wrt W arehouses

sometimesaccesstocurrent(primary)dataisessential

primarydatamaychangerapidly

cansupportunpredictedqueries

PaoloAtzeni|CAiSE*9733

A prop osed architecture for DW

operationaldata

enterprisewarehousedata(granular,subjectoriented,historical)

\DataMarts:"departmentaldata(aggregated,themeoriented)

individual(temporary,adhoc,problem-based)Littleredundancyamongthelevels.

PaoloAtzeni|CAiSE*9734

(anaside)

Data Mining

Twogoalsoverlarge(derived)setsofdata:

 ndrelationships

makeforecasts

PaoloAtzeni|CAiSE*9735 Dataminingisusefulforprovidinginformationofvarioustypes:

classes:groupobjectsonthebasisofproperties

clusters:\unpredicted"categories

associations:correlationsbetweendi erentevents

sequences:speci cpatterns,forexampleintime-series

forecasts

similarsequences

PaoloAtzeni|CAiSE*9736

(10)

No clea rcut

Inacomplexsystemtheremaybe

datawhoseup-to-datenessisessential

datawhoseprimarycopyisexpensivetoaccess(wrttotheactualneedforup-to-dateness)

datathatarealwaysaggregatedinthesamewayTherefore,wecouldneedanintegrationofreplicatedandprimarydata

PaoloAtzeni|CAiSE*9737

An intermediate solution

DBDB LocalMgrLocalMgr PPPPPPP clientExporterExporter

DBDB LocalMgrLocalMgr  clientExtractorExtractor 

HHHH Integrator DW DWMgr

                

PPPPPPPPP GlobalMgr HHHHHH

 clientclient

PaoloAtzeni|CAiSE*9738

Lo cal Info rmation Systems with external data

usefulifasystemhastoaccessexporteddatafromanothersystem

theapplicationhastoincludethemanagementofintegration,translation,accesscontrol

meaningfulonlywithsimpleoperations

datacanbeprimaryorreplicated

PaoloAtzeni|CAiSE*9739

The application do es the integration

DB LocalMgr PPPPPPP clientExporterDB LocalMgr

DBDB LocalMgrLocalMgr  clientExtractorExtractor 

HHHH Integrator DW DWMgr

, , , , , , , , , , , , , , , , ,,

            

PPPPPPPPP client

PaoloAtzeni|CAiSE*9740

(11)

introduction

classi cationcriteria

classi cation

architecturaltechniques

architecturesandmiddlewaretools

conclusionanddiscussion

PaoloAtzeni|CAiSE*9741

Architectures for data-o riented co op eration

multi-levelclient-serverarchitectures

withmiddlewaretoolsfor

{

complexintegrationor

{

basiccooperationinterfaces

PaoloAtzeni|CAiSE*9742

Tw o-level Client/Server architecture



client

:presentation(interface,graphics,somelocalprocessing)



server

:applicationlogicanddataaccess

PaoloAtzeni|CAiSE*9743

Three-level Client/Server architecture

(basicidea)



client

:presentation(interface,graphics,somelocalprocessing)



intermediate server

:applicationlogic



back-end server

:datamanagement

PaoloAtzeni|CAiSE*9744

(12)

Bene ts of three-level Client/Server architecture

theapplicationprogram,thespeci canddelicatepartofeachapplication,isseparatedfrombothUIandDB

theDBisnotexposed

scalabilityand exibilityofcomponents:nothin/fatclientdoubt

modularity:reasonableencapsulationoflegacyapplications

PaoloAtzeni|CAiSE*9745

Multi-level Client/Server architecture



client

:presentation(interface,graphics,somelocalprocessing)



intermediate server

:encapsulation(onanopensystem)ofheterogeneous(possiblylegacy)applications



back-end server

:theencapsulatedapplication(withthedataserver)Therecanbemultiple,intermediateservers(andeventheback-endservermaybeaC/Ssystem)

PaoloAtzeni|CAiSE*9746

Basic techniques for Client/Server data co op eration

on-linedatatransfer

o -linedatatransfer

on-linemessageexchange

o -linemessageexchange

on-linedataaccess

PaoloAtzeni|CAiSE*9747

On-line data transfer

DBDB ApplicationApplication

Gateway @

@

@

@

@

@

@

@ @ @ @ @ @ @ @

PaoloAtzeni|CAiSE*9748

(13)

On-line data transfer: Gatew ays

allowapplicationsforonedatabasetoaccessdataoveranotherdatabase

therearedi erentlevelsoftransparency

typically,theclientmakesuseofSQL

availableintherelationalworldandtoaccesslegacyDBsfromrelationalapplications

 exible(ifauthorized,allowaccesstothewholeDB),althoughsometoolsallowread-onlyaccess

ratherinecient(theserverhastoexecutecasualqueries)PaoloAtzeni|CAiSE*9749

O -line data transfer

DBDB ApplicationApplication

Replicator

, , , , , , ,,

@ @ @ @ @ @ @@

PaoloAtzeni|CAiSE*9750

O -line data transfer

dataareextractedfromoneDB,transformed,andstoredinanother

ad-hocsolutionshavebeenusedfordecades

recentinterestinreplicationandwarehousingtools

toolsfor

{

extraction(incremental,withchangedetection)

{

translation,integration,cleaning,aggregation

{

OLAPprocessing

PaoloAtzeni|CAiSE*9751

On-line message exchange

DBDB ApplicationApplication

Interface

PaoloAtzeni|CAiSE*9752

(14)

On-line message exchange

function-orientedinterface:remoteprocedurecall(RPC)

theclientinvokestheexecutionofaprogramontheserverandgetstheresults

veryroughextreme:screen-scrapers

storedproceduresinDBMSoropensystemsAPIsindistributedenvironments

modernevolution:object-orientedservices

widelyusedintraditionalTPmonitorsandinmoremoderndistributedobjecttechnologiesPaoloAtzeni|CAiSE*9753

O -line message exchange

DBDB ApplicationApplication Queuemanager

PaoloAtzeni|CAiSE*9754

O -line message exchange

function-orientedagain(typically),butasynchronous

atoolhandlesqueuesofmessages(message-orientedmiddleware)

toleratesunavailabilityofserverconnection

PaoloAtzeni|CAiSE*9755

On-line data access

DB Application client(browser) WebserverandCGI

PaoloAtzeni|CAiSE*9756

(15)

On-line data access database access through WWW

verycommon(anduseful)instructuredWWWservers

InternetvsIntranet

allowsthewidedisseminationofinformation

PaoloAtzeni|CAiSE*9757 introduction

classi cationcriteria

classi cation

architecturaltechniques

architecturesandmiddlewaretools

conclusionanddiscussion

PaoloAtzeni|CAiSE*9758

Architectures for data co op eration

Basedon

elementarytools

DatabaseGatewayServersorDistributedDBMSswithgateways

DataWarehousingtools

DistributedTransactionMonitors

ObjectRequestBrokers

integratedtools

PaoloAtzeni|CAiSE*9759

Architectures based on Database Gatew ay Server or Distributed DBMS with gatew ays

DBDB ApplicationApplicationIntegrator

,

,

,

,

,

,

,

, @

@

@

@

@

@

@

@ Application

PaoloAtzeni|CAiSE*9760

(16)

Architectures based on Data W arehousing to ols

DBDB ApplicationApplication

,

,

, @

@

@ Integrator DW Application

PaoloAtzeni|CAiSE*9761

Architectures based on Distributed TP Monito rs or Object Request Brok ers

DBDB ApplicationApplicationIntegrator Application

PaoloAtzeni|CAiSE*9762

Transaction Pro cessing Monito rs

traditionalTPMonitors:ecient(queuemgmt)andreliable(correcttransactions)accessfromremoteterminals

distributedTPMonitors:ecientandreliableaccesstoremoteservicesinadistributedenvironment

currently,thisisnotacompletedistributedcomputationenvironment

PaoloAtzeni|CAiSE*9763

Object Request Brok ers

general-purposedistributedcomputingarchitecture

object-oriented:objectinterfacesareusedbyclientsthatdon'tseeimplementations

donotallowcompletedatabasetransparency

couldbeintegratedwithtoolsthatsupporttransactionmanagement

PaoloAtzeni|CAiSE*9764

(17)

Integrated Tools

provideasuiteoffeatures

oftenobject-based

ofteno erbothdevelopmentandexecutionsupport

PaoloAtzeni|CAiSE*9765

Architectures based on Integrated Tools

DBDB ApplicationApplicationIntegrator

DW ,

,

,

,

,

,

,

, @

@

@

@

@

@

@

@ Application

PaoloAtzeni|CAiSE*9766

introduction

classi cationcriteria

classi cation

architecturaltechniques

architecturesandmiddlewaretools

conclusionanddiscussion

PaoloAtzeni|CAiSE*9767

Conclusions

cooperationcaninvolveverydi erentneedsandsomanyalternativesexist

carefulevaluationofcostsandbene tsofthearchitecture:somesoultionsarecomplexandexpensive

cooperationdoesnotrequiremigrationnorreengineering

cooperationcanstimulateandencouragemigrationandreengineering:itallowsanincremental,low-riskapproachtomigration

PaoloAtzeni|CAiSE*9768

(18)

General References

P.Atzeni,L.Cabibbo,G.Mecca.Databasecooperation:classi cationandmiddlewaretools.Draft.Soonavalaibleathttp://poincare.inf.uniroma3.it:8080

G.DeMichelisetal.Cooperativeinformationsystems:Amanifesto.ToappearinCooperativeInformationSystems:Trends&Directions,M.PapazogluandG.Schlageter(eds),AcademicPress,1997.

M.L.BrodieandM.Stonebraker.MigratingLegacySystems:Gateways,Interfaces&theIncrementalApproach.MorganKau man,LosAltos,1995.

W.Kim,editor.ModernDatabaseSystems:theObjectModel,Interoperability,andBeyond.ACMPressandAddisonWesley,1995.

J.A.Larson.DatabaseDirections.PrenticeHall,1995.

P.A.Bernstein.Middleware:Amodelfordistributedsystemservices.CACM39,2,Feb.1996,86{98.

W.H.Inmon.BuildingtheDataWarehouse,SecondEdition.JohnWiley,1996

OMG.OMAExecutiveOverview.http://www.omg.org/omaov.htm

OMG.SuggestedReadings.http://www.omg.org/suggrdgs.htm

A.P.ShethandJ.A.Larson.Federateddatabasesystemsformanagingdistributed,heterogeneous,andautonomousdatabases.ACMComputingSurveys,22(3):183{236,September1990.

UCSMessagingTeamUCSTechKnowShare:APrimeronMiddleware,IndianaUniversity,http://msgwww.ucs.indiana.edu/messaging/infoshare/middleware.htmlPaoloAtzeni|CAiSE*9769

References to to ols and pro ducts

M.L.BrodieandM.Stonebraker.MigratingLegacySystems:Gateways,Interfaces&theIncrementalApproach.MorganKau man,LosAltos,1995,Chapter10.

Websitesofallproductvendors

DBMS1996Buyer'sGuideandClient/ServerSourcebook.Middleware,Connectivity,andInternetTools.http://www.dbmsmag.com/pcmidcon.html

UCSMessagingTeamUCSTechKnowShare:APrimeronMiddleware,IndianaUniversity,http://msgwww.ucs.indiana.edu/messaging/infoshare/middleware.html

PaoloAtzeni|CAiSE*9770

Riferimenti

Documenti correlati

Data Base and Data Mining Group of Politecnico di

From: Tan,Steinbach, Kumar, Introduction to Data Mining, McGraw Hill 2006.. DB M

 “A big data architecture is designed to handle the ingestion, processing, and analysis of data that is too large or complex for traditional

// By default, the MLlib decision tree algorithm considers only the content // of the features attribute to predict the value of the label attribute. // The other attributes are

▪ For each record, the value of the new column is the original string associated with the value of the input numerical column.  Has also all the columns of the

Database and data mining group, Politecnico di Torino.. DataBase an d Data Mining Group of Po litecnico d

Adattato da Golfarelli, Rizzi,”Data warehouse, teoria e pratica della progettazione”, McGraw Hill 2006 Standardizzazione nome: Elena.

The first lower molar of specimens previously classified on the basis of tooth wear were decalcified and dissected so that the number of annual growth rings