DOCSLIB.ORG

Databases Theoretical Introduction Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Databases Theoretical Introduction Contents Databases Theoretical Introduction Contents 1 Databases 1 1.1 Database ................................................ 1 1.1.1 Terminology and overview .................................. 1 1.1.2 Applications .......................................... 2 1.1.3 General-purpose and special-purpose DBMSs ........................ 2 1.1.4 History ............................................ 2 1.1.5 Research ........................................... 6 1.1.6 Examples ........................................... 6 1.1.7 Design and modeling ..................................... 7 1.1.8 Languages ........................................... 9 1.1.9 Performance, security, and availability ............................ 10 1.1.10 See also ............................................ 12 1.1.11 References .......................................... 12 1.1.12 Further reading ........................................ 13 1.1.13 External links ......................................... 14 1.2 Schema migration ........................................... 14 1.2.1 Risks and Benefits ...................................... 14 1.2.2 Schema migration in agile software development ...................... 14 1.2.3 Available Tools ........................................ 15 1.2.4 References .......................................... 15 1.3 Star schema .............................................. 16 1.3.1 Model ............................................ 16 1.3.2 Benefits ............................................ 16 1.3.3 Disadvantages ........................................ 17 1.3.4 Example ........................................... 17 1.3.5 See also ............................................ 17 1.3.6 References .......................................... 17 1.3.7 External links ......................................... 17 2 Not Only SQL 18 2.1 CAP .................................................. 18 2.1.1 Science and medicine ..................................... 18 2.1.2 Computing .......................................... 18 i ii CONTENTS 2.1.3 Organisations ......................................... 18 2.1.4 Companies .......................................... 18 2.1.5 Projects, programs, policies .................................. 19 2.1.6 Military ............................................ 19 2.1.7 Certifications ......................................... 19 2.1.8 Other ............................................. 19 2.1.9 See also ............................................ 19 2.2 Eventual consistency .......................................... 19 2.2.1 Conflict resolution ....................................... 19 2.2.2 Strong eventual consistency .................................. 20 2.2.3 See also ............................................ 20 2.2.4 References .......................................... 20 2.3 Object-relational impedance mismatch ................................ 20 2.3.1 Mismatches .......................................... 20 2.3.2 Solving impedance mismatch ................................. 21 2.3.3 Contention .......................................... 22 2.3.4 Philosophical differences ................................... 23 2.3.5 References .......................................... 25 2.3.6 External links ......................................... 25 2.4 Object database ............................................ 25 2.4.1 Overview ........................................... 25 2.4.2 History ............................................ 25 2.4.3 Timeline ........................................... 26 2.4.4 Adoption of object databases ................................. 27 2.4.5 Technical features ....................................... 27 2.4.6 Standards ........................................... 27 2.4.7 Comparison with RDBMSs .................................. 27 2.4.8 See also ............................................ 28 2.4.9 References .......................................... 28 2.4.10 External links ......................................... 28 2.5 NoSQL ................................................ 28 2.5.1 History ............................................ 29 2.5.2 Types and examples of NoSQL databases .......................... 29 2.5.3 Performance ......................................... 31 2.5.4 Handling relational data ................................... 31 2.5.5 ACID and JOIN Support ................................... 31 2.5.6 See also ............................................ 32 2.5.7 References .......................................... 32 2.5.8 Further reading ........................................ 33 2.5.9 External links ......................................... 33 2.6 Key-value database .......................................... 33 CONTENTS iii 2.6.1 Types and notable examples ................................. 33 2.6.2 References .......................................... 34 2.6.3 External links ......................................... 35 2.7 Document-oriented database ..................................... 35 2.7.1 Documents .......................................... 35 2.7.2 Comparison with relational databases ............................. 37 2.7.3 Implementations ....................................... 38 2.7.4 See also ............................................ 38 2.7.5 Notes ............................................. 38 2.7.6 References .......................................... 38 2.7.7 Further reading ........................................ 38 2.7.8 External links ......................................... 38 2.8 NewSQL ................................................ 38 2.8.1 History ............................................ 38 2.8.2 Systems ............................................ 39 2.8.3 See also ............................................ 39 2.8.4 References .......................................... 39 3 ACID 40 3.1 ACID ................................................. 40 3.1.1 Characteristics ........................................ 40 3.1.2 Examples ........................................... 40 3.1.3 Implementation ........................................ 41 3.1.4 See also ............................................ 42 3.1.5 References .......................................... 42 3.2 Consistency (database systems) .................................... 42 3.2.1 As an ACID guarantee .................................... 42 3.2.2 As a CAP trade-off ...................................... 43 3.2.3 See also ............................................ 43 3.2.4 References .......................................... 43 3.3 Durability (database systems) ..................................... 43 3.3.1 See also ............................................ 43 4 Isolation 44 4.1 Serializability ............................................. 44 4.1.1 Database transaction ..................................... 44 4.1.2 Correctness .......................................... 44 4.1.3 View and conflict serializability ............................... 46 4.1.4 Enforcing conflict serializability ................................ 46 4.1.5 Distributed serializability ................................... 48 4.1.6 See also ............................................ 49 4.1.7 Notes ............................................. 49 iv CONTENTS 4.1.8 References .......................................... 49 4.2 Isolation (database systems) ...................................... 49 4.2.1 Concurrency control ..................................... 50 4.2.2 Isolation levels ........................................ 50 4.2.3 Default isolation level ..................................... 51 4.2.4 Read phenomena ....................................... 51 4.2.5 Isolation Levels, Read Phenomena and Locks ........................ 52 4.2.6 See also ............................................ 52 4.2.7 References .......................................... 52 4.2.8 External links ......................................... 53 4.3 Database transaction .......................................... 53 4.3.1 Purpose ............................................ 53 4.3.2 Transactional databases .................................... 53 4.3.3 Object databases ....................................... 54 4.3.4 Distributed transactions .................................... 54 4.3.5 Transactional filesystems ................................... 54 4.3.6 See also ............................................ 54 4.3.7 References .......................................... 54 4.3.8 Further reading ........................................ 54 4.3.9 External links ......................................... 55 4.4 Transaction processing ........................................ 55 4.4.1 Description .......................................... 55 4.4.2 Methodology ......................................... 55 4.4.3 ACID criteria ......................................... 56 4.4.4 Benefits ............................................ 56 4.4.5 Implementations ....................................... 57 4.4.6 References .......................................... 57 4.4.7 External links ......................................... 57 4.4.8 Further reading ........................................ 57 5 Atomicity 58 5.1 Journaling file system ......................................... 58 5.1.1 Rationale ........................................... 58 5.1.2 Techniques .......................................... 58 5.1.3 Alternatives .......................................... 59 5.1.4 See also ............................................ 59 5.1.5 References .........................................
Load more

Recommended publications
  • Cryonics Magazine, Q1 2001
    SOURCE FEATURES PAGE Fred Chamberlain Glass Transitions: A Project Proposal 3 Mike Perry Interview with Dr. Jerry Lemler, M.D. 13 Austin Esfandiary A Tribute to FM-2030 16 Johnny Boston FM & I 18 Billy H. Seidel the ALCOR adventure 39 Natasha Vita-More Considering Aesthetics 45 Columns Book Review: Affective Computing..................................41 You Only Go Around Twice .................................................42 First Thoughts on Last Matters............................................48 TechNews.......................................................................51 Alcor update - 19 The Global Membership Challenge . 19 Letter from Steve Bridge . 26 President’s Report . 22 “Last-Minute” Calls . 27 Transitions and New Developments . 24 Alcor Membership Status . 37 1st Qtr. 2001 • Cryonics 1 Alcor: the need for a rescue team or even for ingly evident that the leadership of The Origin of Our Name cryonics itself. Symbolically then, Alcor CSC would not support or even would be a “test” of vision as regards life tolerate a rescue team concept. Less In September of 1970 Fred and extension. than one year after the 1970 dinner Linda Chamberlain (the founders of As an acronym, Alcor is a close if meeting, the Chamberlains severed all Alcor) were asked to come up with a not perfect fit with Allopathic Cryogenic ties with CSC and incorporated the name for a rescue team for the now- Rescue. The Chamberlains could have “Rocky Mountain Cryonics Society” defunct Cryonics Society of California forced a five-word string, but these three in the State of Washington. The articles (CSC). In view of our logical destiny seemed sufficient. Allopathy (as opposed and bylaws of this organization (the stars), they searched through star to Homeopathy) is a medical perspective specifically provided for “Alcor catalogs and books on astronomy, wherein any treatment that improves the Members,” who were to be the core of hoping to find a star that could serve as prognosis is valid.
    [Show full text]
  • Delivering Oracle Compatibility
    DELIVERING ORACLE COMPATIBILITY A White Paper by EnterpriseDB www.EnterpriseDB.com TABLE OF CONTENTS Executive Summary 4 Introducing EnterpriseDB Advanced Server 6 SQL Compatibility 6 PL/SQL Compatibility 9 Data Dictionary Views 11 Programming Flexibility and Drivers 12 Transfer Tools 12 Database Replication 13 Enterprise-Class Reliability and Scalability 13 Oracle-Like Tools 14 Conclusion 15 Downloading EnterpriseDB 15 EnterpriseDB EXECUTIVE SUMMARY Enterprises running Oracle® are generally interested in alternative databases for at least three reasons. First, these enterprises are experiencing budget constraints and need to lower their database Total Cost of Ownership (TCO). Second, they are trying to gain greater licensing flexibility to become more agile within the company and in the larger market. Finally, they are actively pursuing vendors who will provide superior technical support and a richer customer experience. And, subsequently, enterprises are looking for a solution that will complement their existing infrastructure and skills. The traditional database vendors have been unable to provide the combination of all three benefits. While Microsoft SQL ServerTM and IBM DB2TM may provide the flexibility and rich customer experience, they cannot significantly reduce TCO. Open source databases, on the other hand, can provide the TCO benefits and the flexibility. However, these open source databases either lack the enterprise-class features that today’s mission critical applications require or they are not equipped to provide the enterprise-class support required by these organizations. Finally, none of the databases mentioned above provide the database compatibility and interoperability that complements their existing applications and staff. The fear of the costs of changing databases, including costs related to application re-coding and personnel re-training, outweigh the expected savings and, therefore, these enterprises remain paralyzed and locked into Oracle.
    [Show full text]
  • Java Web Application with Database Example
    Java Web Application With Database Example Amerindian Verne sheafs very spaciously while Torrence remains blond and suprasegmental. Udall herdialyses strappers her sayings underselling afore, too shouldered furtively? and disciplinal. Collins remains pigeon-hearted: she barbarises Java and with web delivered to tomcat using an application server successfully authenticated Our database like to databases because docker container environment. Service to mask the box Data JPA implementation. Here is one example application by all credits must create. Updates may also displays in web delivered right click next thing we are looking for creating accounts, please follow this example application depends on. In role based on gke app running directly click add constraint public web application example by a middleware between records in your application for more than other systems. This is maven in java web framework puts developer productivity and dispatches to learn more? Now we tie everything is web application example? This file and brief other dependency files are provided anytime a ZIP archive letter can be downloaded with force link provided at the hen of this tutorial. Confirming these three developers to let see also with database access, jstl to it returns the same infrastructure. What database web container takes care of java and examples. As applications with database support plans that connect to implement nested class names and infrastructure to display correctly set outo commit multiple user interface for. The wizard will ask you to select the schema and the tables of your database and allows you to select the users and groups tables, run related transactions, the last step is to create XML file and add all the mappings to it.
    [Show full text]
  • An Efficient Concurrency Control Technique for Mobile Database Environment by Md
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Global Journal of Computer Science and Technology (GJCST) Global Journal of Computer Science and Technology Software & Data Engineering Volume 13 Issue 2 Version 1.0 Year 2013 Type: Double Blind Peer Reviewed International Research Journal Publisher: Global Journals Inc. (USA) Online ISSN: 0975-4172 & Print ISSN: 0975-4350 An Efficient Concurrency Control Technique for Mobile Database Environment By Md. Anisur Rahman Dhaka University of Engineering & Technology Gazipur, Bangladesh Abstract - Day by day, wireless networking technology and mobile computing devices are becoming more popular for their mobility as well as great functionality. Now it is an extremely growing demand to process mobile transactions in mobile databases that allow mobile users to access and operate data anytime and anywhere, irrespective of their physical positions. Information is shared among multiple clients and can be modified by each client independently. However, for the assurance of timely access and correct results in concurrent mobile transactions, concurrency control techniques (CCT) happen to be very difficult. Due to the properties of Mobile databases e.g. inadequate bandwidth, small processing capability, unreliable communication, mobility etc. existing mobile database CCTs cannot employ effectively. With the client-server model, applying common classic pessimistic techniques of concurrency control (like 2PL) in mobile database leads to long duration Blocking and increasing waiting time of transactions. Because of high rate of aborting transactions, optimistic techniques aren`t appropriate in mobile database as well. This paper discusses the issues that need to be addressed when designing a CCT technique for Mobile databases, analyses the existing scheme of CCT and justify their performance limitations.
    [Show full text]
  • ACID Compliant Distributed Key-Value Store
    ACID Compliant Distributed Key-Value Store #1 #2 #3 Lakshmi Narasimhan Seshan ,​ Rajesh Jalisatgi ,​ Vijaeendra Simha G A # ​ ​ ​ ​1l​ [email protected] # ​2r​ [email protected] #3v​ [email protected] Abstract thought that would be easier to implement. All Built a fault-tolerant and strongly-consistent key/value storage components run http and grpc endpoints. Http endpoints service using the existing RAFT implementation. Add ACID are for debugging/configuration. Grpc Endpoints are transaction capability to the service using a 2PC variant. Build used for communication between components. on the raftexample[1] (available as part of etcd) to add atomic Replica Manager (RM): RM is the service discovery transactions. This supports sharding of keys and concurrent transactions on sharded KV Store. By Implementing a part of the system. RM is initiated with each of the transactional distributed KV store, we gain working knowledge Replica Servers available in the system. Users have to of different protocols and complexities to make it work together. instantiate the RM with the number of shards that the user wants the key to be split into. Currently we cannot Keywords— ACID, Key-Value, 2PC, sharding, 2PL Transaction dynamically change while RM is running. New Replica ​ ​ Servers cannot be added or removed from once RM is I. INTRODUCTION ​ up and running. However Replica Servers can go down Distributed KV stores have become a norm with the and come back and RM can detect this. Each Shard advent of microservices architecture and the NoSql Leader updates the information to RM, while the DTM revolution. Initially KV Store discarded ACID properties leader updates its information to the RM.
    [Show full text]
  • Lecture 15: March 28 15.1 Overview 15.2 Transactions
    CMPSCI 677 Distributed and Operating Systems Spring 2019 Lecture 15: March 28 Lecturer: Prashant Shenoy 15.1 Overview This section covers the following topics: Distributed Transactions: ACID Properties, Concurrency Control, Serializability, Two-Phase Locking 15.2 Transactions Transactions are used widely in databases as they provide atomicity (all or nothing property). Atomicity is the property in which operations inside a transaction all execute successfully or none of the operations execute. Thus, if a process crashes during a transaction, all operations that happened during that transaction must be undone. Transactions are usually implemented using locks. Without locks there would be interleaving of operations from two transactions, causing overwrites and inconsistencies. It has to look like all instructions/operations of one transaction are executed at once, while ensuring other external instructions/operations are not executing at the same time. This is especially important in real-world applications such as banking applications. 15.2.1 ACID: Most transaction systems will provide the following properties • Atomicity: All or nothing (all instructions execute or none; cannot have some instructions execute and some do not) • Consistency: Transaction takes system from one consistent (valid) state to another • Isolated: Transaction executes as if it is the only transaction in the system. Ensures that the concurrent execution of transactions results in a system state that would be obtained if transactions were executed sequentially (serializability).
    [Show full text]
  • Resume of Dr. Michael J. Bisconti
    Table of Contents This file contains, in order: Time Savers Experience Matrix Resume _________________________ 1 Time Savers There are a number of things we can do to save everyone’s time. In addition to resume information there are a number of common questions that employers and recruiters have. Here is an FAQ that addresses these questions. (We may expand this FAQ over time.) Frequently Asked Questions 1099 Multiple Interviewers Severance Pay Contract End Date Multiple Interviews Technical Exam Contract Job Need/Skill Assessment Interview Temporary Vs. Permanent Contract Rate Payment Due Dates U.S. Citizenship Drug Testing Permanent Job W2 Face-to-face Interview Phone Interview Word Resume Job Hunt Progress Salary Are you a U.S. citizen? Yes. Do you have a Word resume? Yes, and I also have an Adobe PDF resume. Do you prefer temporary (contract) or permanent employment? Neither, since, in the end, they are equivalent. Will you take a drug test? 13 drug tests taken and passed. Do you work 1099? Yes, but I give W2 payers preference. Do you work W2? Yes, and I work 1099 as well but I give W2 payers preference. How is your job search going? See 1.2 Job Hunt Progress. What contract rate do you expect? $65 to $85/hr. W2 and see the 2.5 Quick Rates Guide. What salary do you expect? 120k to 130k/yr. and see the 2.5 Quick Rates Guide. When do you expect to be paid? Weekly or biweekly and weekly payers will be given preference. Will you do a face-to-face interview? Yes, but I prefer a Skype or equivalent interview because gas is so expensive and time is so valuable.
    [Show full text]
  • Serving the Boaters of America PROLOG P/R/C Greg Scotten, SN
    Volume 2, Issue 2 May 2012 Marketing and Public Relations, The Art and Science of Creating LINKS (Click on selected Link) a Call to Action and Causing a Change. The United States Power Squadrons PR Contest Forms Boating Safety Centennial Anniversary Articles Cabinet Serving the Boaters of America PROLOG P/R/C Greg Scotten, SN The United States Power Squadrons is Inside this issue: celebrating 100 years of community Jacksonville Sail & Power service on 1 February 2014. Your Squadron to conduct a celebratory USPS Centennial 1 squadron needs to be part of that boat parade on the St. John’s important Centennial event which is a River. national milestone. To celebrate this Bright Ideas 2 national milestone, several projects are The Power Squadrons Flag and underway and a national anniversary Etiquette Committee has designed Importance of 3 a unique boat Ensign, which Squadron Editors web page will post exciting activities and information. The Power Squadrons’ emphasizes the event, and is to be MPR Committee 3 Ship Store will be featuring items with flown on members’ vessels in 2013 Mission the 100th Anniversary Logo. An and 2014. A special new Power anniversary postal commemorative is Squadrons logo has been under discussion. All levels of the distributed and is available on line. organization are planning local 2012 Governing 4 A year long ceremonial activity is community activities. Board planned. At the 2013 Annual The precise anniversary day is Sunday, Meeting Governing Board, full sized anniversary Ensigns will be Hands-on Training 6 2 February 2014. But because the Governing Board at the Annual Meeting presented to each of the thirty- two districts.
    [Show full text]
  • Postfix-Cyrus-Web-Cyradm-HOWTO
    Postfix-Cyrus-Web-cyradm-HOWTO Luc de Louw luc at delouw.ch Revision History Revision 1.2.6 2004-03-30 Revised by: ldl Added minor additions and corrected to amavisd-new, corrected cronjob-time for freshclam Revision 1.2.5 2004-03-28 Revised by: ldl Added Anti-Virus and SPAM methods (amavisd-new, spamassassin, clamav), updated cyrus-imapd section with update instructions, added instruction to restrict imapd admin access. Revision 1.2.4 2003-11-30 Revised by: ldl Input from English proofreading, minor correction and enhancements from user-input, updated software mentioned in the HOWTO Revision 1.2.3 2003-03-24 Revised by: ldl Some minor correction and enhancements from user-input, updated software mentioned in the HOWTO Revision 1.2.2 2003-02-14 Revised by: ldl Lots of grammar and typos fixed. Some corrections to the pam_mysql Makefile Revision 1.2.1 2003-02-12 Revised by: ldl Non-official test-release: Added lots of fixes and updates. Added OpenSSL and more pam related stuff. Revision 1.2.0 2002-10-16 Revised by: ldl Added lot of user requests, updated the software mentioned in the HOWTO Revision 1.1.7 2002-10-15 Revised by: ldl Added Michael Muenz’ hints for SMTP AUTH, corrected ca-cert related mistake, improved SGML code (more metadata), updated the software mentioned in the document. Revision 1.1.6 2002-06-14 Revised by: ldl Added sasl_mech_list: PLAIN to imapd.conf, added web-cyradm mailinglist, added more to web-cyradm Revision 1.1.5 2002-06-11 Revised by: ldl Added new SQL query to initialize web-cyradm to have full data integrity in the MySQL Database, mysql-mydestination.cf reported to be operational as expected.
    [Show full text]
  • Toward an Automated Vulnerability Comparison of Open Source IMAP Servers Chaos Golubitsky – Carnegie Mellon University
    Toward an Automated Vulnerability Comparison of Open Source IMAP Servers Chaos Golubitsky – Carnegie Mellon University ABSTRACT The attack surface concept provides a means of discussing the susceptibility of software to as-yet-unknown attacks. A system’s attack surface encompasses the methods the system makes available to an attacker, and the system resources which can be used to further an attack. A measurement of the size of the attack surface could be used to compare the security of multiple systems which perform the same function. The Internet Message Access Protocol (IMAP) has been in existence for over a decade. Relative to HTTP or SMTP, IMAP is a niche protocol, but IMAP servers are widely deployed nonetheless. There are three popular open source UNIX IMAP servers – UW-IMAP, Cyrus, and Courier-IMAP – and there has not been a formal security comparison between them. In this paper, I use attack surfaces to compare the relative security risks posed by these three products. I undertake this evaluation in service of two complementary goals: to provide an honest examination of the security postures and risks of the three servers, and to advance the study of attack surfaces by performing an automated attack surface measurement using a methodology based on counting entry and exit points in the code. Introduction Contributions and Roadmap System administrators frequently confront the The paper makes two major contributions. First, problem of selecting a software package to perform a I undertake an in-depth discussion of the relative secu- desired function. Many considerations affect this deci- rity postures of the three major open source IMAP sion, including functionality, ease of installation, soft- servers in use today.
    [Show full text]
  • Unravel Data Systems Version 4.5
    UNRAVEL DATA SYSTEMS VERSION 4.5 Component name Component version name License names jQuery 1.8.2 MIT License Apache Tomcat 5.5.23 Apache License 2.0 Tachyon Project POM 0.8.2 Apache License 2.0 Apache Directory LDAP API Model 1.0.0-M20 Apache License 2.0 apache/incubator-heron 0.16.5.1 Apache License 2.0 Maven Plugin API 3.0.4 Apache License 2.0 ApacheDS Authentication Interceptor 2.0.0-M15 Apache License 2.0 Apache Directory LDAP API Extras ACI 1.0.0-M20 Apache License 2.0 Apache HttpComponents Core 4.3.3 Apache License 2.0 Spark Project Tags 2.0.0-preview Apache License 2.0 Curator Testing 3.3.0 Apache License 2.0 Apache HttpComponents Core 4.4.5 Apache License 2.0 Apache Commons Daemon 1.0.15 Apache License 2.0 classworlds 2.4 Apache License 2.0 abego TreeLayout Core 1.0.1 BSD 3-clause "New" or "Revised" License jackson-core 2.8.6 Apache License 2.0 Lucene Join 6.6.1 Apache License 2.0 Apache Commons CLI 1.3-cloudera-pre-r1439998 Apache License 2.0 hive-apache 0.5 Apache License 2.0 scala-parser-combinators 1.0.4 BSD 3-clause "New" or "Revised" License com.springsource.javax.xml.bind 2.1.7 Common Development and Distribution License 1.0 SnakeYAML 1.15 Apache License 2.0 JUnit 4.12 Common Public License 1.0 ApacheDS Protocol Kerberos 2.0.0-M12 Apache License 2.0 Apache Groovy 2.4.6 Apache License 2.0 JGraphT - Core 1.2.0 (GNU Lesser General Public License v2.1 or later AND Eclipse Public License 1.0) chill-java 0.5.0 Apache License 2.0 Apache Commons Logging 1.2 Apache License 2.0 OpenCensus 0.12.3 Apache License 2.0 ApacheDS Protocol
    [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]