DOCSLIB.ORG

DB2 and Nosql - the End of RelaOnal?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DB2 and Nosql - the End of Rela�Onal? DB2 and NoSQL - The end of relaonal? George Baklarz IBM Canada Lab Session Code: B08 Thursday, September 12 (11:15 am – 12:15 pm) | DB2 for Linux, Unix, and Windows 2 Agenda • Database Market • Databases • Applicaon APIs • NoSQL • Types of NoSQL Databases • Current Market Trends with NoSQL • JavaScript Object Notaon • What is it and Why do developers Like it • JSON Datastore in DB2 • MongoDB Query API • Java Programming API • JSON Wire-listener 3 The Database Market and Choice You are here 4 Database API Support Javascript Java PhP Python/Jython Ruby/JRuby Scala node.js JDBC API pureQuery node.js Zend node-odbc SqlAlchemy / Rails Lift API framework JSON Django Adapter Adapter adapters driver JSON API Python interpreter Ruby interpreter Hibernate c java c java OpenJPA DB2 CLI and ODBC driver DB2 JCC JDBC driver DB2 5 ADO.NET Support Application (ASP.NET) ADO.NET ODBC .NET OLE DB .NET Data Provider Data Provider Other .NET DB2 .NET Data Data Providers Provider IDS/DB2 ODBC IDS/DB2 OLE Driver Provider Informix DB2 DBMS DB DB Now supporting: Visual Studio 2012, .NET Framework 4.5, Entity Framework 4.3, Entity Framework 5.0 is delivered with DB2 10.5 6 What is NoSQL? Dominant Flavors • Key Value Stores 122+ NoSQL Database Hash table of keys, where the data part of Offerings Today! • key-value is in a binary object • Examples pure key-value stores : MemcacheD, REDIS, WebSphere eXtreme Scale • Document Stores • Stores documents made up of tagged elements, which have keys and document-like objects • Examples : MongoDB, couchDB • Column Family • Each storage block contains data from only one column/column set • Examples : HBase, Cassandra Motivation • Graph Store § Many apps need fewer database features (simplicity) • Key-values are related through graph structure § Need rapid application evolution/deployment, with minimal interaction with DBA • Common Model : RDF § Some apps need extremely high scale (e.g. Twitter) • Examples : Jena, Sesame § Need for a low-latency, low-overhead API to access data § Increasing use of distributed analytics 7 No SQL Market Data • 2011: Market Research Media noted worldwide NoSQL market was 2014 expected to reach ~$3.4B by 2018, generang $14B from 2013-2018 % NoSQL Enterprise Adoption with a CAGR of 21% 2010 2015 • Comparison: data implies NoSQL market ~$895M "MongoDB is the new MySQL." • MySQL in 2011 ~$100M "Current adoption of NoSQL in enterprises is 4% in 2010. expected to double by 2014, and grow to 20% by 2015. 10% of existing apps could move to NoSQL. [Sept 2011] "NoSQL is in its infancy, many immature with only community support and limited tool capability; however, expect to see a few used more widely during the next 5 years." 8 Hacker News Trends 9 The JSON-XML ShiN • Developers find it easier to move data back and forth without losing informaon in JSON vs. XML • XML is more powerful and more sophisMcated than JSON • BUT JSON found to be 'good enough' à It makes programming tasks easier • By the Mme RDBMS world got very sophisMcated with XML, developers had chosen JSON • Applicaon shid lead to emergence of database that store data in JSON (i.e. MongoDB) • JSON on the server side is appealing for developers using JSON on the client Mer side 10 Open APIs State of the Market • JSON is the new cool • XML declining: 5 years ago hardly any JSON • Why? JSON is: • Less verbose and smaller docs size • <Mytag>value</Mytag> vs. Mytag:value • Tightly integrated with JavaScript which has a lot of focus • Most new development tools support JSON and not XML • 50% of NoSQL Engines are for JSON Documents 11 New Era Applica4on Characteris4cs • Applicaons evolve rapidly as the needs for mobile and Web presence try to keep pace with internet user needs • Applicaon developers are increasingly looking for soluMons that allow nearly conMnuous integraon of applicaon changes • Amazon.com allows 1000’s of their developers to check in product code changes daily… • Developers resist soluMons that require delays to sync up with DBA change windows 12 NoSQL JSON Stores are Appealing to Developers • JSON schema can be evolved rapidly without intervenMon by DBAs or data modelers. • Objects like "shopping cart" in these applicaons really aren’t used outside the Web applicaon, so there is no need to interlock closely with the rest of the enterprise data model • JSON offers a very simple and elegant model for persisMng Java or JavaScript objects, without needing a heavy-weight persistence soluon like OpenJPA or Hibernate • Performance and scalability is very good for JSON • Store a single JSON document represenMng the object versus • Store "n" rows in relaonal as a "normalized" object 13 Typical JSON Open Source Datastore Aributes • Logging is oden turned off to improve performance • By default, no return code on insert (a.k.a. "fire and forget") • App must verify update was performed • Data is sharded for scalability • Shards are replicated asynchronously for availability • Queries to replica nodes can return back-level data someMmes… • No concept of commit or rollback • Each JSON update is independent • No document-level locking • App must manage a "revision" tag to detect document update conflicts • Applicaons have to implement compensaon logic to update mulMple documents with ACID properMes • JSON documents are stored in collecMons • But no "join" across collecMons • No document-level or tag-level security • No built-in temporal or geo-spaal query support 14 Data Access Example Using JavaScript and JSON • Relaonal representaon Lastname Firstname Street Jones Billy 123 Maple Drive • JSON representaon JSON_string = ‘{"Lastname":"Jones", "Firstname":"Billy", "Street":"123 Maple Drive"}’; " • Javascript data access var JSONrecord = JSON.parse(JSON_string); " l_name = JSONrecord.Lastname;" f_name = JSONrecord.Firstname;" l_street = JSONrecord.Street;" 15 Simple Database API for JSON • Insert a record, a blog post by Joe: "db.posts.insert({author:"Joe", date:"2012-04-20", post:"…"}) • Find all posts by Joe: "db.posts.find({author:"Joe"})" • Update date of Joe's post "db.posts.update({author:"Joe",{$set:{date:"2013-08-22"}})" • Delete all posts of Joe: "db.posts.remove({author:"Joe"})" • Remove the posts collecMon "db.posts.drop()" 16 The Guardian Move from Oracle to MongoDB • ExisMng system: Modern Java Applicaon using Load became an issue Spring, Hibernate, and Oracle RDBMS was difficult to scale • Problems: • Schema upgrades caused downMme • Complexity • Found 300 tables complex (imagine SAP) • 10,000 lines of Hibernate configuraon code found to be buggy • 1,000 domain objects for database mapping • 70,000 lines of domain object code, Mght binding to database • ORM did not really mask complexity • Database had strong influence on domain model, complex mapping joins Introduced memcached to patch up load problems • Required complex hibernate features, complex caching strategy, lots of opMmizaons, hand code complex queries in SQL • Load problems: introduced caching, and SOLR/ API to opMmize reads • Solved load problems, but increased complexity to 3 models: tables, objects, JSON API 17 The Guardian Move to MongoDB Found it a simple key store… too simple • First project: Migrate Oracle system with 3M users, complex PL-SQL • Embraced MongoDB: • Simple flexible schema with similar query and indexing to RDBMS • MulMple domain concepts expressed in single document • Can be designed in forwardly extensible way • Document oriented • Stores parsed JSON documents • Can express complex queries • Can be flexible about consistency • Malleable schema, can change at runMme • Can work at both large and small scales • Easy for developers to get going • Commercial support available (10Gen) • Produces a net reducMon in lines of code and complexity 18 DB2 JSON Support: Agility With a Trusted Founda4on • Interoperate seamlessly with modern applicaons • Flexible schemas allow rapid delivery of applicaons • Preserve tradiMonal DBMS capabiliMes, leverage exisMng skills and tools • MulM-statement TransacMons • Management / Operaons • Security • Scale, performance and high availability • Extend with advanced features (future) • Temporal semanMcs • Full Text search • MulM-collecMon joins • Combine with Enterprise RDBMS data 19 DB2 JSON API Technology Details • IBM provided Java Driver for JSON API • Java Driver supporMng JSON API for data access layer • TransacMons • Parametric SQL statements (Delete, select) • Temporal tables • CLP-Like Command Shell • Ad-hoc updates / queries • Administraon commands • Open Source Driver Wire Listener • Leverage NoSQL community drivers for data access layer 20 DB2 JSON Java API • Java Driver that translates API calls to SQL + funcon invoca:ons • Supports Transactions • Batches insertions Java Apps • Fire-forget inserts (fast) JSON API JSON • Indexing Command Shell • Time travel query JDBC Driver DRDA • Smart Query re-write • Java command line JSON_TABLE() JSON JSON_UPDATE() UDFs … JSON_VAL() - builtin, supports extraction of (SQL) DB2 Engine IoE w/ BLOB in the values from BSON expression 21 DB2 NoSQL/JSON API from Java /*Set up Conn. and Database handle*/ /* Use cursor to fetch back the JSON */ Context ctx = new InitialContext(); DataSource ds = DBCursor cursor = shop.find(new (DataSource)ctx.lookup("jdbc/myDB2"); BasicDBObject("customer", "Bill")); Connection conn = ds.getConnection(); try { Database db = new Database(conn); DBCollection shop = while(cursor.hasNext()) { db.getCollection("shop"); DBObject obj = cursor.next(); doSomething(obj); /*Create JSON objects and insert*/ } BasicDBObject cart = new } finally{ BasicDBObject();
Load more

Recommended publications
  • Not ACID, Not BASE, but SALT a Transaction Processing Perspective on Blockchains
    Not ACID, not BASE, but SALT A Transaction Processing Perspective on Blockchains Stefan Tai, Jacob Eberhardt and Markus Klems Information Systems Engineering, Technische Universitat¨ Berlin fst, je, [email protected] Keywords: SALT, blockchain, decentralized, ACID, BASE, transaction processing Abstract: Traditional ACID transactions, typically supported by relational database management systems, emphasize database consistency. BASE provides a model that trades some consistency for availability, and is typically favored by cloud systems and NoSQL data stores. With the increasing popularity of blockchain technology, another alternative to both ACID and BASE is introduced: SALT. In this keynote paper, we present SALT as a model to explain blockchains and their use in application architecture. We take both, a transaction and a transaction processing systems perspective on the SALT model. From a transactions perspective, SALT is about Sequential, Agreed-on, Ledgered, and Tamper-resistant transaction processing. From a systems perspec- tive, SALT is about decentralized transaction processing systems being Symmetric, Admin-free, Ledgered and Time-consensual. We discuss the importance of these dual perspectives, both, when comparing SALT with ACID and BASE, and when engineering blockchain-based applications. We expect the next-generation of decentralized transactional applications to leverage combinations of all three transaction models. 1 INTRODUCTION against. Using the admittedly contrived acronym of SALT, we characterize blockchain-based transactions There is a common belief that blockchains have the – from a transactions perspective – as Sequential, potential to fundamentally disrupt entire industries. Agreed, Ledgered, and Tamper-resistant, and – from Whether we are talking about financial services, the a systems perspective – as Symmetric, Admin-free, sharing economy, the Internet of Things, or future en- Ledgered, and Time-consensual.
    [Show full text]
  • MDA Process to Extract the Data Model from a Document-Oriented Nosql Database Amal Ait Brahim, Rabah Tighilt Ferhat, Gilles Zurfluh
    MDA process to extract the data model from a document-oriented NoSQL database Amal Ait Brahim, Rabah Tighilt Ferhat, Gilles Zurfluh To cite this version: Amal Ait Brahim, Rabah Tighilt Ferhat, Gilles Zurfluh. MDA process to extract the data model from a document-oriented NoSQL database. ICEIS 2019: 21st International Conference on Enterprise Information Systems, May 2019, Heraklion, Greece. pp.141-148, 10.5220/0007676201410148. hal- 02886696 HAL Id: hal-02886696 https://hal.archives-ouvertes.fr/hal-02886696 Submitted on 1 Jul 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Open Archive Toulouse Archive Ouverte OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible This is an author’s version published in: https://oatao.univ-toulouse.fr/26232 Official URL : https://doi.org/10.5220/0007676201410148 To cite this version: Ait Brahim, Amal and Tighilt Ferhat, Rabah and Zurfluh, Gilles MDA process to extract the data model from a document-oriented NoSQL database. (2019) In: ICEIS 2019: 21st International Conference on Enterprise Information Systems, 3 May 2019 - 5 May 2019 (Heraklion, Greece).
    [Show full text]
  • MDA Process to Extract the Data Model from Document-Oriented Nosql Database
    MDA Process to Extract the Data Model from Document-oriented NoSQL Database Amal Ait Brahim, Rabah Tighilt Ferhat and Gilles Zurfluh Toulouse Institute of Computer Science Research (IRIT), Toulouse Capitole University, Toulouse, France Keywords: Big Data, NoSQL, Model Extraction, Schema Less, MDA, QVT. Abstract: In recent years, the need to use NoSQL systems to store and exploit big data has been steadily increasing. Most of these systems are characterized by the property "schema less" which means absence of the data model when creating a database. This property brings an undeniable flexibility by allowing the evolution of the model during the exploitation of the base. However, query expression requires a precise knowledge of the data model. In this article, we propose a process to automatically extract the physical model from a document- oriented NoSQL database. To do this, we use the Model Driven Architecture (MDA) that provides a formal framework for automatic model transformation. From a NoSQL database, we propose formal transformation rules with QVT to generate the physical model. An experimentation of the extraction process was performed on the case of a medical application. 1 INTRODUCTION however that it is absent in some systems such as Cassandra and Riak TS. The "schema less" property Recently, there has been an explosion of data offers undeniable flexibility by allowing the model to generated and accumulated by more and more evolve easily. For example, the addition of new numerous and diversified computing devices. attributes in an existing line is done without Databases thus constituted are designated by the modifying the other lines of the same type previously expression "Big Data" and are characterized by the stored; something that is not possible with relational so-called "3V" rule (Chen, 2014).
    [Show full text]
  • What Is Nosql? the Only Thing That All Nosql Solutions Providers Generally Agree on Is That the Term “Nosql” Isn’T Perfect, but It Is Catchy
    NoSQL GREG SYSADMINBURD Greg Burd is a Developer Choosing between databases used to boil down to examining the differences Advocate for Basho between the available commercial and open source relational databases . The term Technologies, makers of Riak. “database” had become synonymous with SQL, and for a while not much else came Before Basho, Greg spent close to being a viable solution for data storage . But recently there has been a shift nearly ten years as the product manager for in the database landscape . When considering options for data storage, there is a Berkeley DB at Sleepycat Software and then new game in town: NoSQL databases . In this article I’ll introduce this new cat- at Oracle. Previously, Greg worked for NeXT egory of databases, examine where they came from and what they are good for, and Computer, Sun Microsystems, and KnowNow. help you understand whether you, too, should be considering a NoSQL solution in Greg has long been an avid supporter of open place of, or in addition to, your RDBMS database . source software. [email protected] What Is NoSQL? The only thing that all NoSQL solutions providers generally agree on is that the term “NoSQL” isn’t perfect, but it is catchy . Most agree that the “no” stands for “not only”—an admission that the goal is not to reject SQL but, rather, to compensate for the technical limitations shared by the majority of relational database implemen- tations . In fact, NoSQL is more a rejection of a particular software and hardware architecture for databases than of any single technology, language, or product .
    [Show full text]
  • Nosql Database Technology
    NoSQL Database Technology Post-relational data management for interactive software systems NOSQL DATABASE TECHNOLOGY Table of Contents Summary 3 Interactive software has changed 4 Users – 4 Applications – 5 Infrastructure – 5 Application architecture has changed 6 Database architecture has not kept pace 7 Tactics to extend the useful scope of RDBMS technology 8 Sharding – 8 Denormalizing – 9 Distributed caching – 10 “NoSQL” database technologies 11 Mobile application data synchronization 13 Open source and commercial NoSQL database technologies 14 2 © 2011 COUCHBASE ALL RIGHTS RESERVED. WWW.COUCHBASE.COM NOSQL DATABASE TECHNOLOGY Summary Interactive software (software with which a person iteratively interacts in real time) has changed in fundamental ways over the last 35 years. The “online” systems of the 1970s have, through a series of intermediate transformations, evolved into today’s web and mobile appli- cations. These systems solve new problems for potentially vastly larger user populations, and they execute atop a computing infrastructure that has changed even more radically over the years. The architecture of these software systems has likewise transformed. A modern web ap- plication can support millions of concurrent users by spreading load across a collection of application servers behind a load balancer. Changes in application behavior can be rolled out incrementally without requiring application downtime by gradually replacing the software on individual servers. Adjustments to application capacity are easily made by changing the number of application servers. But database technology has not kept pace. Relational database technology, invented in the 1970s and still in widespread use today, was optimized for the applications, users and inf- rastructure of that era.
    [Show full text]
  • SQL Vs Nosql: a Performance Comparison
    SQL vs NoSQL: A Performance Comparison Ruihan Wang Zongyan Yang University of Rochester University of Rochester [email protected] [email protected] Abstract 2. ACID Properties and CAP Theorem We always hear some statements like ‘SQL is outdated’, 2.1. ACID Properties ‘This is the world of NoSQL’, ‘SQL is still used a lot by We need to refer the ACID properties[12]: most of companies.’ Which one is accurate? Has NoSQL completely replace SQL? Or is NoSQL just a hype? SQL Atomicity (Structured Query Language) is a standard query language A transaction is an atomic unit of processing; it should for relational database management system. The most popu- either be performed in its entirety or not performed at lar types of RDBMS(Relational Database Management Sys- all. tems) like Oracle, MySQL, SQL Server, uses SQL as their Consistency preservation standard database query language.[3] NoSQL means Not A transaction should be consistency preserving, meaning Only SQL, which is a collection of non-relational data stor- that if it is completely executed from beginning to end age systems. The important character of NoSQL is that it re- without interference from other transactions, it should laxes one or more of the ACID properties for a better perfor- take the database from one consistent state to another. mance in desired fields. Some of the NOSQL databases most Isolation companies using are Cassandra, CouchDB, Hadoop Hbase, A transaction should appear as though it is being exe- MongoDB. In this paper, we’ll outline the general differences cuted in iso- lation from other transactions, even though between the SQL and NoSQL, discuss if Relational Database many transactions are execut- ing concurrently.
    [Show full text]
  • IBM Cloudant: Database As a Service Fundamentals
    Front cover IBM Cloudant: Database as a Service Fundamentals Understand the basics of NoSQL document data stores Access and work with the Cloudant API Work programmatically with Cloudant data Christopher Bienko Marina Greenstein Stephen E Holt Richard T Phillips ibm.com/redbooks Redpaper Contents Notices . 5 Trademarks . 6 Preface . 7 Authors. 7 Now you can become a published author, too! . 8 Comments welcome. 8 Stay connected to IBM Redbooks . 9 Chapter 1. Survey of the database landscape . 1 1.1 The fundamentals and evolution of relational databases . 2 1.1.1 The relational model . 2 1.1.2 The CAP Theorem . 4 1.2 The NoSQL paradigm . 5 1.2.1 ACID versus BASE systems . 7 1.2.2 What is NoSQL? . 8 1.2.3 NoSQL database landscape . 9 1.2.4 JSON and schema-less model . 11 Chapter 2. Build more, grow more, and sleep more with IBM Cloudant . 13 2.1 Business value . 15 2.2 Solution overview . 16 2.3 Solution architecture . 18 2.4 Usage scenarios . 20 2.5 Intuitively interact with data using Cloudant Dashboard . 21 2.5.1 Editing JSON documents using Cloudant Dashboard . 22 2.5.2 Configuring access permissions and replication jobs within Cloudant Dashboard. 24 2.6 A continuum of services working together on cloud . 25 2.6.1 Provisioning an analytics warehouse with IBM dashDB . 26 2.6.2 Data refinement services on-premises. 30 2.6.3 Data refinement services on the cloud. 30 2.6.4 Hybrid clouds: Data refinement across on/off–premises. 31 Chapter 3.
    [Show full text]
  • Top 5 Considerations When Evaluating Nosql Databases February 2015 Table of Contents
    A MongoDB White Paper Top 5 Considerations When Evaluating NoSQL Databases February 2015 Table of Contents Introduction 1 Data Model 2 Document Model 2 Graph Model 2 Key-Value and Wide Column Models 2 Query Model 3 Document Database 3 Graph Database 3 Key Value and Wide Column Databases 3 Consistency Model 4 Consistent Systems 4 Eventually Consistent Systems 4 APIs 4 Idiomatic Drivers 5 Thrift or RESTful APIs 5 Pluggable Storage API 5 Commercial Support and Community Strength 5 Commercial Support 5 Community Strength 5 Conclusion 6 We Can Help 6 Introduction Relational databases have a long-standing position in most Development teams have a strong say in the technology organizations, and for good reason. Relational databases selection process. This community tends to find that the underpin legacy applications that meet current business relational data model is not well aligned with the needs of needs; they are supported by an extensive ecosystem of their applications. Consider: tools; and there is a large pool of labor qualified to • Developers are working with new data types — implement and maintain these systems. structured, semi-structured, unstructured and But companies are increasingly considering alternatives to polymorphic data — and massive volumes of it. legacy relational infrastructure. In some cases the • Long gone is the twelve-to-eighteen month waterfall motivation is technical — such as a need to scale or development cycle. Now small teams work in agile perform beyond the capabilities of their existing systems — sprints, iterating quickly and pushing code every week while in other cases companies are driven by the desire to or two, even every day.
    [Show full text]
  • Nosql Database Evaluation Guide How Leading Nosql Databases Compare Across the Eight Core Requirements TABLE of CONTENTS Introduction
    NoSQL Database Evaluation Guide How Leading NoSQL Databases Compare Across the Eight Core Requirements TABLE OF CONTENTS Introduction Introduction 2 Digital Economy Overview 3 The business world is undergoing massive change as industry after industry shifts to the Digital Economy. It’s an economy powered by the Internet and other 21st-century technologies — the Data Access 5 cloud, mobile, social media, and big data. At the heart of every Digital Economy business are its web, mobile, and Internet of Things (IoT) applications: they’re the primary way companies interact Performance 6 with customers today, and how companies run more and more of their business. The experiences Scalability 7 that companies deliver via those apps largely determine how satisfied — and how loyal — customers will be. Availability 8 Building and running these web, mobile, and IoT applications has created a new set of technology Geographic 9 requirements. Enterprise architecture needs to be far more agile than ever before, and requires Distribution an approach to real-time data management that can accommodate unprecedented levels of scale, speed, and data flexibility. Relational databases are unable to meet these new requirements, and Big Data Integration 10 enterprises are therefore turning to NoSQL database technology. Administration 11 Three Phases of NoSQL Evolution and Adoption: From Grassroots to Mainstream Mobile 12 Enterprise adoption of NoSQL has unfolded in three overlapping phases. In phase I (which Conclusion 12 started around 2010), developers required flexibility to support the agile development of proof Checklist 13 of concepts and small applications. In phase II (which began around 2013), enterprises required performance, scalability, and availability to develop and/or migrate targeted mission-critical services.
    [Show full text]
  • Why Nosql? Your Database Options in the New Non-Relational World 2 Why Nosql?
    IBM Analytics April 2016 White paper Why NoSQL? Your database options in the new non-relational world 2 Why NoSQL? Contents A brief history of NoSQL NoSQL, also known as not only SQL or non-relational databases, 2 New types of apps are generating new types of data were specifically introduced to handle the rise in data types, 2 A brief history of NoSQL data access, and data availability needs brought on by the dot-com boom. 3 Types of NoSQL databases 4 Why consider NoSQL? Going back 20 years or so, when application architects and developers needed a data store for their applications, they were 5 Summary choosing among various relational databases. In fact, relational 5 Getting started with IBM Cloudant databases have been the de facto choice since the 1970s, as they have been the sole option available for both developers 5 For more information (because SQL is taught in computer science programs everywhere) and infrastructure teams (because of the well- understood tooling and predictable operational characteristics of RDBMSs). Some of the most popular are Oracle, MySQL, New types of apps are generating new SQL Server and IBM® DB2®. types of data The continual increase in web, mobile and IoT applications, However, when Internet applications and companies started alongside emerging trends shifting online consumer behavior exploding during the late 90s to early 2000s, applications went and new classes of data, is causing developers to reevaluate how from serving thousands of internal employees within their data is stored and managed. Today’s applications require a companies to having millions of users on the public Internet.
    [Show full text]
  • A Big Data Roadmap for the DB2 Professional
    A Big Data Roadmap For the DB2 Professional Sponsored by: align http://www.datavail.com Craig S. Mullins Mullins Consulting, Inc. http://www.MullinsConsulting.com © 2014 Mullins Consulting, Inc. Author This presentation was prepared by: Craig S. Mullins President & Principal Consultant Mullins Consulting, Inc. 15 Coventry Ct Sugar Land, TX 77479 Tel: 281-494-6153 Fax: 281.491.0637 Skype: cs.mullins E-mail: [email protected] http://www.mullinsconsultinginc.com This document is protected under the copyright laws of the United States and other countries as an unpublished work. This document contains information that is proprietary and confidential to Mullins Consulting, Inc., which shall not be disclosed outside or duplicated, used, or disclosed in whole or in part for any purpose other than as approved by Mullins Consulting, Inc. Any use or disclosure in whole or in part of this information without the express written permission of Mullins Consulting, Inc. is prohibited. © 2014 Craig S. Mullins and Mullins Consulting, Inc. (Unpublished). All rights reserved. © 2014 Mullins Consulting, Inc. 2 Agenda Uncover the roadmap to Big Data… the terminology and technology used, use cases, and trends. • Gain a working knowledge and definition of Big Data (beyond the simple three V's definition) • Break down and understand the often confusing terminology within the realm of Big Data (e.g. polyglot persistence) • Examine the four predominant NoSQL database systems used in Big Data implementations (graph, key/value, column, and document) • Learn some of the major differences between Big Data/NoSQL implementations vis-a-vis traditional transaction processing • Discover the primary use cases for Big Data and NoSQL versus relational databases © 2014 Mullins Consulting, Inc.
    [Show full text]
  • Data Modeling Guidelines for Nosql Document-Store Databases
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 9, No. 10, 2018 Data Modeling Guidelines for NoSQL Document-Store Databases Abdullahi Abubakar Imam1;a;b, Shuib Basri2;a, Rohiza Ahmad3;a, Junzo Watada4;a, Maria T. Gonzlez-Aparicio5;c, Malek Ahmad Almomani6;a aCIS Department, Universiti Teknologi PETRONAS, Bandar Seri Iskandar, 31570, Perak, Malaysia bCS Department, Ahmadu Bello University, Zaria-Nigeria cComputing Department, University of Oviedo Gijon, Spain Abstract—Good database design is key to high data avail- [11], developer autonomy [1], [12] and inadequate modeling ability and consistency in traditional databases, and numerous guidelines [13], have posed numerous challenges in NoSQL techniques exist to abet designers in modeling schemas appropri- schema best-practice implementation. This has increasingly led ately. These schemas are strictly enforced by traditional database to erroneous database modeling and designs [1], [14], [15], engines. However, with the emergence of schema-free databases [16], [17], which defeats the notion of robustness in NoSQL (NoSQL) coupled with voluminous and highly diversified datasets databases and results in the production of low-performance, (big data), such aid becomes even more important as schemas in NoSQL are enforced by application developers, which requires a non-secure and less-durable systems. high level of competence. Precisely, existing modeling techniques and guides used in traditional databases are insufficient for big- For example, consider the security aspect of NoSQL data storage settings. As a synthesis, new modeling guidelines for document-oriented databases. The databases offer a query NoSQL document-store databases are posed. These guidelines language or an Application Program Interface (API) that has cut across both logical and physical stages of database designs.
    [Show full text]