data management dilemma - size vs complexity

14
SIZE COMPLEXITY DATA MANAGEMENT DILEMMA www.Metasafe-Repository.com

Upload: reinhold-thurner

Post on 07-Apr-2017

26 views

Category:

Data & Analytics


3 download

TRANSCRIPT

Page 1: Data Management Dilemma - SIZE vs COMPLEXITY

SIZECOMPLEXITY

DATA MANAGEMENT DILEMMA

www.Metasafe-Repository.com

Page 2: Data Management Dilemma - SIZE vs COMPLEXITY

COM

PLEX

ITY

SIZE versus COMPLEXITY

EREntity-Relationship

SIZESIZERELATIONALTables/ColsRELATIONALTables/Cols

Page 3: Data Management Dilemma - SIZE vs COMPLEXITY

COM

PLEX

ITY

SIZE versus COMPLEXITYONE «data approach» does not fit ALL:

Both … HIGH RISK?EREntity-Relationship

Complexity is priority:Entity-Relationship is king

SIZERELATIONALTables/Cols

SIZE is priority:RELATIONAL is king

RELATIONALTables/Cols

Page 4: Data Management Dilemma - SIZE vs COMPLEXITY

TypesProperities

Bi-directionalRelationships

PropertiesDATAMODEL Types

Properities

Model EditorDesigner

The «Relational» Approach for large ApplicationsENTITY-RELATIONSHIP

DATA MODEL

Page 5: Data Management Dilemma - SIZE vs COMPLEXITY

TypesProperities

Bi-directionalRelationships

PropertiesDATAMODEL Types

Properities

Model EditorDesigner

The «Relational» Approach for large Applications

Table-B

Columns

RELATIONALDATABASEManagementSystem(DBMS)

SQL-Query Language

STORAGE

Table-AColumns

Tables - ColumnsMap Physical Storage(Buffers, Disks, Sectors…)

GAP

ENTITY-RELATIONSHIP DATA MODEL

RELATIONALDATABASE MODEL

Page 6: Data Management Dilemma - SIZE vs COMPLEXITY

TypesProperities

Bi-directionalRelationships

PropertiesDATAMODEL Types

Properities

Model EditorDesigner

The «Relational» Approach for large Applications

Optimizes for Speed and Size at the Expense of Complexity

Table-B

Columns

RELATIONALDATABASEManagementSystem(DBMS)

SQL-Query Language

STORAGE

Table-AColumns

Tables - ColumnsMap Physical Storage(Buffers, Disks, Sectors…)

GAP

MODEL isENTITY-RELATIONSHIP

IMPLEMENTATION isRELATIONAL

STEP (1) Create DataModelto deal with Complexity

Step (2) CONVERT DataModel to RELATIONAL Optimize for Speed/Size

BrowserData Editor

Import/ExportXLS, XML, PDF

(3) Develop TOOLS

Page 7: Data Management Dilemma - SIZE vs COMPLEXITY

TypesProperities

Bi-directionalRelationships

PropertiesDATAMODEL Types

Properities

Model EditorDesigner

The «Relational» Approach for large Applications

BrowserData Editor

Import/ExportXLS, XML, PDF

(3) D

evel

op T

OO

LS

Optimized for Speed and Size at the Expense of Complexity

Over Time DataModel OBSOLETE

Table-B

Columns

RELATIONALDATABASEManagementSystem(DBMS)

SQL-Query Language

STORAGE

Table-AColumns

Tables - ColumnsMap Physical Storage(Buffers, Disks, Sectors…)

- Model not tested / obsolete

- Structure GAP to DB

+ Speed, Size optimized

Page 8: Data Management Dilemma - SIZE vs COMPLEXITY

Metasafe – The “Entity-Relationship” Approach

Entity-AAttributes

Entity-BAttributes

Bi-directionalRelationshipsAttributes

ER-DATABASEManagementSystem(DBMS)

Java APIFramework

Model EditorDesigner

TypesProperities

Bi-directionalRelationshipsProperties

DATAMODEL Types

Properities

Java API / FrameworkAccess to ModelAccess to Data

Page 9: Data Management Dilemma - SIZE vs COMPLEXITY

Metasafe – The “Entity-Relationship” Approach

Entity-AAttributes

Entity-BAttributes

Bi-directionalRelationshipsAttributes

ER-DATABASEManagementSystem(DBMS)

Java APIFramework

Model EditorDesigner

TypesProperities

Bi-directionalRelationshipsProperties

DATAMODEL Types

Properities

Automatic MappingModel and Data

are always in sync

Page 10: Data Management Dilemma - SIZE vs COMPLEXITY

Metasafe – The “Entity-Relationship” ApproachACCESS-RIGHTS

TRANSACTIONS

Entity-AAttributes

Entity-BAttributes

Bi-directionalRelationshipsAttributes

ER-DATABASEManagementSystem(DBMS)erSQL-Query

Language

Java APIFramework

BrowserData Editor->Eclipse

Import/ExportXLS, XML, PDFXML/FO, BIRT

Model EditorDesigner

TypesProperities

Bi-directionalRelationshipsProperties

DATAMODEL Types

Properities

Access Rights + TransactionsMulti-UserAccess

Page 11: Data Management Dilemma - SIZE vs COMPLEXITY

GraphicalQuery-Editor

QUERY

ExecuteRuntime

Flexible Reporting with the erSQL Query Language Point&Click - Query-Editorfrom DataModel to Query

in easy steps

Query extracts structuredData and Metadata

Page 12: Data Management Dilemma - SIZE vs COMPLEXITY

GraphicalQuery-Editor

QUERY

ExecuteRuntime

BIRTReporting

StructuredFormattedPDF-File

Output to ExcelOutput to XML..

Flexible Reporting with the erSQL Query Language

Graphical Output

Advanced OutputIntegration with BIRT*)

Business Intelligent and Reporting Tool

Page 13: Data Management Dilemma - SIZE vs COMPLEXITY

Conclusion – ONE is not for ALL

Metasafe – ENTITY-RELATIONSHIP - Newcomer, No large Customerbase, physical Constraints (SIZE)+ DataModels tested, in Sync with DataBase, Basic Tool Set integrated+ Open / Controlled Access with powerful API and erSQL-Query> optimal 4 Development Prototypes and Applications with up to XX GB

Standard - RELATIONAL - Large ECO-System of DBMSs and Tools available - DataModel becomes obsolete, Difficulty with complex Data + DataBaseModel can be adapted to phsical Constraints > optimal 4 large Applications where SIZE and SPEED are Priority

Conclusion –> Both

Page 14: Data Management Dilemma - SIZE vs COMPLEXITY

Metasafe delivers – an integrated multifunctional SYSTEMGet started –> [email protected]