Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Building on Multi-Model Databases

677 vues

Publié le

What’s the problem? The data is in silos. Business and IT are both demanding a unified view of data to help provide solutions to today’s business challenges, but you can’t use the tools and technologies that created the problem to solve the problem. Enter the Multi-Model database. In this session John Biedebach introduces a trusted and secure approach to data integration using Multi-Model databases. The data we want to integrate has already been modeled, so we’ll discuss how to load information as-is into a Multi-Model database to leverage the models that already exist in the data. We’ll then apply our own models to our data in place to rapidly deliver answers to business questions while providing value from harmonized information directly to consumers. We’ll also discuss the characteristics of a Multi-Model database and the benefits of a Multi-Model approach, including:

How to get unified views across disparate data models and formats within a single database
The benefits of a single product vs multi-product Multi-Model approach to data integration
The importance of agility in data access and delivery through APIs, interfaces, and indexes
How to scale a multi-model database while still providing ACID capabilities and security
How to determine where a multi-model database fits in your existing architecture

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Building on Multi-Model Databases

  1. 1. © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Building on Multi-Model Databases John Biedebach Solution Director, MarkLogic john.biedebach@marklogic.com 972-841-6060
  2. 2. SLIDE: 2 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Agenda  How to get unified views across disparate data models and formats within a single database  The benefits of a single product vs multi-product Multi-Model approach to data integration  The importance of agility in data access and delivery through APIs, interfaces, and indexes  How to scale a multi-model database while still providing ACID capabilities and security  How to determine where a multi-model database fits in your existing architecture
  3. 3. SLIDE: 3 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. http://www.oreilly.com/data/free/building- on-multi-model-databases.csp MORE INFO
  4. 4. SLIDE: 4 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Hollerith Tabulator - 1890
  5. 5. SLIDE: 5 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. IBM Punch Card
  6. 6. SLIDE: 6 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Mainframes
  7. 7. SLIDE: 7 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. EF Codd
  8. 8. SLIDE: 8 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Relational Databases  Relational Databases earn the name because prior to using them, you must define how the data is “related”
  9. 9. SLIDE: 9 © COPYRIGHT 2016 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. The Problem With the Relational Approach The Business Changes, The Requirements Change, The Source Data Changes 1 Take a Current State Snapshot Design the New Data Model Perform ETL Create the Indexes 2 3 4 Build the Application 5 Restart Process 6
  10. 10. SLIDE: 10 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Simple Transaction
  11. 11. SLIDE: 11 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Simple Transaction Transaction Detail Transaction Header StoreProduct
  12. 12. SLIDE: 12 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Hierarchical Data Model  Document-centric database - Supports any-structured data via hierarchical data model - Stores compressed binary trees Document Title Author Section Section Section Section Section First Last Metadata Transaction Detail Customer Store Product NamePrice Phone Address
  13. 13. SLIDE: 13 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Transaction <root> <header> <date>2017-01-05</date> <store>321</store> </header> <detail> <item>Spaghetti Sauce</item> <qty>1</qty> <price unit=”usd”>8.00</price> <item>Garlic</item> ... </detail> </root>
  14. 14. SLIDE: 14 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. The Document Model  More natural and human-readable  Heterogeneous data is okay (schema- agnostic)  Query across data harmoniously (e.g., search for zip code, “94111”, returns both records)  Group documents into collections (e.g., create a collection for each source system)  Insert/update/delete documents in a single transaction – even if it changes the schema { "Customer_ID": 1001, "Fname": "Paul", "Lname": "Jackson", "Phone": "415-555-1212", "SSN": "123-45-6789", "Addr": "123 Avenue ", "City": "Someville", "State": "CA", "Zip": 94111 } { "Cust_ID" : 2001 , "Given_Name" : "Karen" , "Family_Name" : "Bender" , "Shipping_Address" : { "Street" : "324 Some Road" , "City" : "San Francisco" , "State" : "CA" , "Postal" : "94111" , "Country" : "USA" } , "Billing_Address" : { "Street" : "847 Another Ave" , "City" : "San Carlos" , "State" : "CA" , "Postal" : "94070" , "Country" : "USA" } } JSON DOCUMENTS
  15. 15. SLIDE: 15 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  16. 16. SLIDE: 16 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  17. 17. SLIDE: 17 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  18. 18. SLIDE: 18 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  19. 19. SLIDE: 19 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. 2 3 1 4 1 Ingest Data As-Is 2 Access the Data 4 Operationalize 3 Harmonize & Enrich the Data
  20. 20. SLIDE: 20 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  21. 21. SLIDE: 21 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. 2 3 1 4 1 Ingest Data As-Is 2 Access the Data 4 Operationalize 3 Harmonize & Enrich the Data
  22. 22. SLIDE: 22 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  23. 23. SLIDE: 23 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Data Lineage
  24. 24. SLIDE: 24 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Harmonization
  25. 25. SLIDE: 25 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Harmonization
  26. 26. SLIDE: 26 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Multi-Model  Document (XML or JSON)
  27. 27. SLIDE: 27 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  28. 28. SLIDE: 28 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  29. 29. SLIDE: 29 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Multi-Model  Document (XML or JSON)  Geospatial
  30. 30. SLIDE: 30 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Joins
  31. 31. SLIDE: 31 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. RDF Triples Subject Predicate Object John IsMember PreSales John IsSub Field_Org John Field_OrgInfer:
  32. 32. SLIDE: 32 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. RDF Triples Subject Predicate Object John IsMember PreSales Derek IsMember PreSales Derek IsManager PreSales
  33. 33. SLIDE: 33 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  34. 34. SLIDE: 34 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  35. 35. SLIDE: 35 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Multi-Model  Document (XML or JSON)  Geospatial  RDF Triples
  36. 36. SLIDE: 36 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.
  37. 37. SLIDE: 37 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Multi-Model  Document (XML or JSON)  Geospatial  RDF Triples (Semantic Data)  Other Data: - Social Media - Videos, Photos - Binary Documents OTHER METHODS REST APIs, Java Client API, Node.js Client API, Java / .NET XCC JSON XML SEMANTIC DATA GEOSPATIAL DATA BINARY Multi-Model
  38. 38. SLIDE: 38 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Agenda  How to get unified views across disparate data models and formats within a single database  The benefits of a single product vs multi-product Multi-Model approach to data integration  The importance of agility in data access and delivery through APIs, interfaces, and indexes  How to scale a multi-model database while still providing ACID capabilities and security  How to determine where a multi-model database fits in your existing architecture
  39. 39. SLIDE: 39 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. JAVASCRIPT XQUERY SPARQL SQL TRANSACTIONAL APPS ANALYTICAL APPS Reference Architecture JSON XML RDF GEO Ingest BINARY DATA INGESTION DATA STORAGE, MANAGEMENT, AND SEARCH APPLICATIONS EVALUATION LAYER (E-NODES) DATA LAYER (D-NODES) INDEXES, SECURITY, MONITORING, MANAGEMENT DATA ACCESS DOWNSTREAM SYSTEMS REST API JAVA API NODE.JS API
  40. 40. SLIDE: 40 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Flexible Deployment  Write the application once, run it anywhere  Operate in the cloud  Operate on-premises CLOUD PHYSICAL / VIRTUAL DEPLOY
  41. 41. SLIDE: 41 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. ACID Transactions  100% ACID Transactions, not eventually or strongly consistent  Enables transactional/operational apps (e.g. e-commerce solutions)  Implemented using Multi-Version Concurrency Control (MVCC)
  42. 42. SLIDE: 42 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Certified, Granular Security  RBAC at the sub-document level  Automatic security indexing enforced at the database level for ALL data access  Common Criteria Security Certification PROVENANCEAVAILABILITY CERTIFIED AUTHENTICITYINTEGRITY CONFIDENTIALITY Common Criteria
  43. 43. SLIDE: 43 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. BITEMPORAL CERTIFIED SECURITY ACID TRANSACTIONS FLEXIBLE DEPLOYMENT SCALABILITY & ELASTICITY HA/DR TIERED STORAGE Enterprise Requirements for Operational Systems Capabilities Required Must Never Lose Data Must Deploy in Any Environment Must Be Cost Effective Must Be Secure Must Address Industry Compliance Requirements Must Scale Up & Down
  44. 44. SLIDE: 44 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Agenda  How to get unified views across disparate data models and formats within a single database  The benefits of a single product vs multi-product Multi-Model approach to data integration  The importance of agility in data access and delivery through APIs, interfaces, and indexes  How to scale a multi-model database while still providing ACID capabilities and security  How to determine where a multi-model database fits in your existing architecture
  45. 45. SLIDE: 45 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Is Multi-Model Right For You? Good Fits  Disparate Data  Changing Schema  Multiple Data Types  Hard to Model  Multiple Targets  Master Data Mgmt Poor Fits  Great Fit for Relational  Heavy Reliance on Traditional BI Tools  Lack of Institutional Willingness
  46. 46. SLIDE: 46 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Mythbusters  Multi-Model is not secure  Multi-Model is not good for transactions  Multi-Model is hard  Multi-Model does not run in the cloud
  47. 47. SLIDE: 47 © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. http://www.oreilly.com/data/free/building- on-multi-model-databases.csp MORE INFO
  48. 48. © COPYRIGHT 2017 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Building on Multi-Model Databases John Biedebach Solution Director, MarkLogic john.biedebach@marklogic.com 972-841-6060

×