DOCSLIB.ORG

RELATIONAL to Nosql: GETTING STARTED from SQL SERVER

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
RELATIONAL to Nosql: GETTING STARTED from SQL SERVER RELATIONAL RELATIONALTO NoSQL: TO NoSQL: GETTING STARTED FROM SQL SERVER Getting Started From SQL Server RELATIONAL TO NoSQL: GETTING STARTED FROM SQL SERVER Why the shift to NoSQL? Customer loyalty and The business world is undergoing massive change as industry after industry shifts competitive advantage to the digital economy. It’s an economy powered by the internet and other 21st hinges on customer century technologies – the cloud, mobile, social media, and big data. At the heart experiences. of every digital economy business are its web, mobile, and Internet of Things (IoT) applications: They’re the primary way companies interact with customers Customers demand today, and how companies run more and more of their business. The experiences responsive, intelligent, and that companies deliver via those apps largely determine how satisfied – and how immersive apps. Building a great-looking app is just loyal – customers will be. the beginning. How are these applications different from legacy enterprise applications like ERP, HR, and financial accounting? Fundamentally, they are about customer interactions rather than transactions. As customers spend more and more time interacting than transacting, every interaction counts. They expect exceptional experiences every time, regardless of the device, location, or time. Customers demand responsive, intelligent, and immersive apps. Building a great-looking app is just the beginning. Liberating data fast, and at scale, makes all the difference. It’s where other legacy database technologies fall short. Today’s web, mobile, and IoT applications share one or more (if not all) of the following characteristics. They need to: • Focus on the overall customer, employee, and customer experience, not just capturing the transaction • Support large numbers of concurrent users (tens of thousands, perhaps millions) • Deliver highly responsive experiences to a globally distributed base of users • Be always available – no downtime • Handle semi- and unstructured data • Rapidly adapt to changing requirements with frequent updates and new features Building and running these web, mobile, and IoT applications has created a new set of technology requirements. The new enterprise technology architecture needs to be far more agile than ever before, and requires an approach to real-time data management that can accommodate unprecedented levels of scale, speed, and data variability. Relational databases are unable to meet these new requirements, and enterprises are therefore turning to NoSQL database technology. Consider just a few examples of Global 2000 enterprises that are deploying NoSQL for mission-critical applications that have been discussed in recent news reports: The shift from • Tesco, Europe’s #1 retailer, deploys NoSQL for eCommerce, product catalog, transactions to and other applications interactions requires a different kind of • Ryanair, the world’s busiest airline, uses NoSQL to power its mobile app database. serving over 3 million users Couchbase’s NoSQL Data Platform enables • Marriott deployed NoSQL to modernize its reservation system that books enterprises to deploy $38 billion annually solutions that provide more agility, better • Gannett, the #1 U.S. newspaper publisher, replaced SQL Server with NoSQL performance, and easier administration to power its digital publishing platform, Presto at lower cost. • GE is deploying NoSQL for its Predix platform to help manage the Industrial Internet • Cars.com, with over 30 million visits per month, replaced SQL Server with NoSQL to store customer and vehicle data At Couchbase, we’ve enabled hundreds of enterprises, as well as numerous growth companies and startups, to deploy NoSQL for better agility, performance, simpler maintenance, and lower costs. The goal of this paper is to help you introduce NoSQL into your infrastructure by highlighting lessons learned from enterprises that successfully adopted NoSQL. We’ll explore key considerations and strategies for transitioning to NoSQL, in particular, to a document database (Couchbase Server), with tips for moving from SQL Server and other relational databases. Note, there are use cases in which Couchbase can be used to replace existing infrastructure, as well as use cases where Couchbase can be used to complement existing relational technology by adding performance, agility, and polyglot persistence. We’ll start with recommendations for identifying and selecting the right application. Next, we’ll cover strategies for modeling relational data as documents, how to access them within your application, and how to migrate data from a relational database. Finally, we’ll highlight the basics of operating a NoSQL database in comparison to a relational database. Top 5 reasons companies replace SQL Server with a NoSQL database If you’re running into limits with Microsoft SQL Server (or other relational databases) – either in terms of rising costs and complexity, or in scaling to meet your requirements – this is the time to evaluate a NoSQL database. Many companies have chosen Couchbase Server either to augment Microsoft SQL Server and other relational databases, or in some cases replace them. Their top 5 reasons: Easier to scale Whether running on 3 nodes or hundreds – in 1 data center or many – Couchbase Server is based on a distributed architecture to scale on commodity hardware with ease, regardless of the operating system. 3 Better performance Couchbase Server features an integrated cache, memory-optimized indexes, and memory-to-memory replication to deliver consistent, high throughput with submillisecond response time, at any scale. Many enterprises have Up to 40x lower cost successfully introduced With subscriptions based on the number of instances, Couchbase Server typically NoSQL by identifying costs 5-40x less than SQL Server and its per-core based licensing – especially on a single application or servers with many cores. service to start with. Cross-platform Couchbase Server can be deployed on Windows or Linux (Red Hat, Ubuntu, Debian, and more), simplifying deployment and administration by decoupling the database from the operating system. Greater agility With a JSON-based data model and a SQL-based query language, Couchbase Server enables developers to build applications easier, faster, and without the need for complex object/relational mapping. Identifying the right application Many enterprises have successfully introduced NoSQL by identifying a single application or service to start with. It could be a new one that is being developed, or an existing application that’s being refactored. Examples include: • A high performance, highly available caching service • A small, independent application with a narrow scope • A logical or physical service within a large application • A global service that powers multiple applications Ideal candidates have one or more of the following characteristics or requirements: • Fast iteration – the data model needs to be modified continuously or on demand (e.g., to accommodate new preferences, new social media accounts, etc.). • Read and write JSON documents (semi-structured data) to/from web and mobile clients. • Provide low latency, high throughput access to data — e.g., users expect interactions to be instant, and waiting negatively impacts the experience (e.g., users abandon shopping carts) • Support thousands to millions of concurrent users — e.g., the number of users is increasing, sometimes exponentially, as when content goes viral • Users are not limited to a specific country or region — they’re everywhere • Users are not limited to specific hours — the service has to be available 24x7 • Store terabytes of data • Deploy in multiple data centers with an active/active configuration 4 Some common examples of good fits for NoSQL: • Product Catalog Service • Asset Tracking Service • Content Management Service • Application Configuration Service • Customer Management Service Couchbase Server is a • File or Streaming Metadata Service document database — data is stored in • Mobile Field Enablement Services JSON documents, not in tables. • Consumer-centric Mobile Services Every JSON document includes its own flexible Modeling and migrating your data schema, and it can be changed on demand Couchbase Server is a document database – data is stored in JSON documents, by changing the not in tables. While relational databases rely on an explicit predefined schema to document itself. describe the structure of data, document databases do not – JSON documents are self-describing. As such, every JSON document includes its own flexible schema, and it can be changed on demand by changing the document itself. Figure 1: Relational schema and data vs. self-describing JSON documents It’s important to understand that JSON documents are not limited to fields. They can include arrays and objects, and they can be nested, just like applications. For this reason, there is no “impedance mismatch” between application objects and JSON documents. Figure 2: Multiple tables vs. nested data with JSON documents 5 Just as every row in a table requires a primary key, every document requires an Object ID. Many applications rely on relational databases to automatically generate the primary key (for example, with the IDENTITY columns in Microsoft SQL Server). However, with document databases, applications should leverage natural keys where possible. In a relational database, primary keys are defined per table. It’s not uncommon NOTE: for the primary key of different rows in different tables to have
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]
  • Relational Database Design Chapter 7
    Chapter 7: Relational Database Design Chapter 7: Relational Database Design First Normal Form Pitfalls in Relational Database Design Functional Dependencies Decomposition Boyce-Codd Normal Form Third Normal Form Multivalued Dependencies and Fourth Normal Form Overall Database Design Process Database System Concepts 7.2 ©Silberschatz, Korth and Sudarshan 1 First Normal Form Domain is atomic if its elements are considered to be indivisible units + Examples of non-atomic domains: Set of names, composite attributes Identification numbers like CS101 that can be broken up into parts A relational schema R is in first normal form if the domains of all attributes of R are atomic Non-atomic values complicate storage and encourage redundant (repeated) storage of data + E.g. Set of accounts stored with each customer, and set of owners stored with each account + We assume all relations are in first normal form (revisit this in Chapter 9 on Object Relational Databases) Database System Concepts 7.3 ©Silberschatz, Korth and Sudarshan First Normal Form (Contd.) Atomicity is actually a property of how the elements of the domain are used. + E.g. Strings would normally be considered indivisible + Suppose that students are given roll numbers which are strings of the form CS0012 or EE1127 + If the first two characters are extracted to find the department, the domain of roll numbers is not atomic. + Doing so is a bad idea: leads to encoding of information in application program rather than in the database. Database System Concepts 7.4 ©Silberschatz, Korth and Sudarshan 2 Pitfalls in Relational Database Design Relational database design requires that we find a “good” collection of relation schemas.
    [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]
  • LIST of NOSQL DATABASES [Currently 150]
    Your Ultimate Guide to the Non - Relational Universe! [the best selected nosql link Archive in the web] ...never miss a conceptual article again... News Feed covering all changes here! NoSQL DEFINITION: Next Generation Databases mostly addressing some of the points: being non-relational, distributed, open-source and horizontally scalable. The original intention has been modern web-scale databases. The movement began early 2009 and is growing rapidly. Often more characteristics apply such as: schema-free, easy replication support, simple API, eventually consistent / BASE (not ACID), a huge amount of data and more. So the misleading term "nosql" (the community now translates it mostly with "not only sql") should be seen as an alias to something like the definition above. [based on 7 sources, 14 constructive feedback emails (thanks!) and 1 disliking comment . Agree / Disagree? Tell me so! By the way: this is a strong definition and it is out there here since 2009!] LIST OF NOSQL DATABASES [currently 150] Core NoSQL Systems: [Mostly originated out of a Web 2.0 need] Wide Column Store / Column Families Hadoop / HBase API: Java / any writer, Protocol: any write call, Query Method: MapReduce Java / any exec, Replication: HDFS Replication, Written in: Java, Concurrency: ?, Misc: Links: 3 Books [1, 2, 3] Cassandra massively scalable, partitioned row store, masterless architecture, linear scale performance, no single points of failure, read/write support across multiple data centers & cloud availability zones. API / Query Method: CQL and Thrift, replication: peer-to-peer, written in: Java, Concurrency: tunable consistency, Misc: built-in data compression, MapReduce support, primary/secondary indexes, security features.
    [Show full text]
  • High Performance with Distributed Caching
    High Performance with Distributed Caching Key Requirements For Choosing The Right Solution High Performance with Distributed Caching: Key Requirements for Choosing the Right Solution Table of Contents Executive summary 3 Companies are choosing Couchbase for their caching layer, and much more 3 Memory-first 4 Persistence 4 Elastic scalability 4 Replication 5 More than caching 5 About this guide 5 Memcached and Oracle Coherence – two popular caching solutions 6 Oracle Coherence 6 Memcached 6 Why cache? Better performance, lower costs 6 Common caching use cases 7 Key requirements for an effective distributed caching solution 8 Problems with Oracle Coherence: cost, complexity, capabilities 8 Memcached: A simple, powerful open source cache 10 Lack of enterprise support, built-in management, and advanced features 10 Couchbase Server as a high-performance distributed cache 10 General-purpose NoSQL database with Memcached roots 10 Meets key requirements for distributed caching 11 Develop with agility 11 Perform at any scale 11 Manage with ease 12 Benchmarks: Couchbase performance under caching workloads 12 Simple migration from Oracle Coherence or Memcached to Couchbase 13 Drop-in replacement for Memcached: No code changes required 14 Migrating from Oracle Coherence to Couchbase Server 14 Beyond caching: Simplify IT infrastructure, reduce costs with Couchbase 14 About Couchbase 14 Caching has become Executive Summary a de facto technology to boost application For many web, mobile, and Internet of Things (IoT) applications that run in clustered performance as well or cloud environments, distributed caching is a key requirement, for reasons of both as reduce costs. performance and cost. By caching frequently accessed data in memory – rather than making round trips to the backend database – applications can deliver highly responsive experiences that today’s users expect.
    [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]
  • Database Software Market: Billy Fitzsimmons +1 312 364 5112
    Equity Research Technology, Media, & Communications | Enterprise and Cloud Infrastructure March 22, 2019 Industry Report Jason Ader +1 617 235 7519 [email protected] Database Software Market: Billy Fitzsimmons +1 312 364 5112 The Long-Awaited Shake-up [email protected] Naji +1 212 245 6508 [email protected] Please refer to important disclosures on pages 70 and 71. Analyst certification is on page 70. William Blair or an affiliate does and seeks to do business with companies covered in its research reports. As a result, investors should be aware that the firm may have a conflict of interest that could affect the objectivity of this report. This report is not intended to provide personal investment advice. The opinions and recommendations here- in do not take into account individual client circumstances, objectives, or needs and are not intended as recommen- dations of particular securities, financial instruments, or strategies to particular clients. The recipient of this report must make its own independent decisions regarding any securities or financial instruments mentioned herein. William Blair Contents Key Findings ......................................................................................................................3 Introduction .......................................................................................................................5 Database Market History ...................................................................................................7 Market Definitions
    [Show full text]
  • Couchbase Vs Mongodb Architectural Differences and Their Impact
    MongoDB vs. Couchbase Server: Architectural Differences and Their Impact This 45-page paper compares two popular NoSQL offerings, diving into their architecture, clustering, replication, and caching. By Vladimir Starostenkov, R&D Engineer at Altoros Q3 2015 Table of Contents 1. OVERVIEW ......................................................................................................................... 3 2. INTRODUCTION ................................................................................................................. 3 3. ARCHITECTURE................................................................................................................. 4 4. CLUSTERING ..................................................................................................................... 4 4.1 MongoDB ............................................................................................................................................. 4 4.2 Couchbase Server .............................................................................................................................. 5 4.3 Partitioning .......................................................................................................................................... 6 4.4 MongoDB ............................................................................................................................................. 7 4.5 Couchbase Server .............................................................................................................................
    [Show full text]
  • Comparing Approaches: Analytic Workspaces and Materialized Views
    Comparing Materialized Views and Analytic Workspaces in Oracle Database 11g An Oracle White Paper March 2008 Comparing Materialized Views and Analytic Workspaces in Oracle Database 11g Introduction ....................................................................................................... 3 Fast Reporting – Comparing The Approaches............................................. 3 Overview of Materialized Views................................................................. 3 Overview of Analytic Workspaces............................................................. 4 Working Together in the Oracle Database ............................................... 6 Explanation of Data Used for this White Paper........................................... 6 Methodology for Designing and Building the Materialized Views........ 7 Manually Creating the Materialized View ............................................. 7 Generating Recommendations from the SQL Access Advisor ........ 9 Methodology for Defining the Analytic Workspace ............................. 10 Tools For Querying ........................................................................................ 15 Refreshing the Data ........................................................................................ 16 Refreshing Materialized Views.................................................................. 16 Refreshing Analytic Workspace Cubes.................................................... 17 Other Issues To Consider.............................................................................
    [Show full text]