11 A.C.I.D. Properties Isolated • Modification of one data must be independent of another Transaction. [other wise outcome of result will be erroneous] Durable • When Transaction completed, modification performed must be permanent in the system.

12 A.C.I.D. Properties 12

NoSQL What is NoSQL?

14 What is NoSQL...??  Non-relational database management systems,  Different from traditional RDBMS in some significant ways.

16 What is NoSQL...??  Designed for  distributed data stores where  very large scale of data storing needs (for example Google or Facebook which collects terabits of data every day for their users).

17 What is NoSQL...??  These type of data storing may not require fixed schema, avoid join operations and typically scale horizontally.

18 Scaling...!!!!  Ability of a System to expand to meet business needs. Ex. Web application – allow more people to use web application  Vertical Scaling  Horizontal Scaling

20 Horizontal Scaling...!!!!  Scale Out - add more nodes to system. Ex. Add new computer to distributed software application. In NoSQL system, data store can be much faster as it takes advantage of “scaling out”

NoSQL Term NoSQL by Carlo Strozzi Year 1998

NoSQL Why is NoSQL?

23 Why NoSQL ?  In today’s time data is becoming easier to access and capture through third parties such as Facebook, Google+ and others.

25 Why NoSQL ?  To avail the above service properly, it is required to process huge amount of data.  Which SQL databases were never designed. The evolution of NoSql databases is to handle these huge data properly.

26 26

27 What’s there in NoSQL ?  Instead of using structured tables to store multiple related attributes in a row, NoSQL databases use the concept of a key/value store.

28 What’s there in NoSQL ?  No schema for the database.  Stores values for each provided key, distributes them across the database and then allows their efficient retrieval.

29 What’s there in NoSQL ?  Lack of a schema prevents complex queries and essentially prevents the use of NoSQL as a transactional database environment

34 CAP Theorem • When designing any distributed system. CAP theorem states that there are three basic requirements which exist in a special relation when designing applications for a distributed architecture.

35 CAP Theorem • Consistency - the data in the database remains consistent after the execution of an operation. For example after an update operation all clients see the same data.

36 CAP Theorem • Availability - the system is always on (service guarantee availability), no downtime.

37 CAP Theorem • Partition Tolerance - the system continues to function even the communication among the servers is unreliable, i.e. the servers may be partitioned into multiple groups that cannot communicate with one another.

38 CAP Theorem • In theoretically it is impossible to fulfill all 3 requirements • CAP provides the basic requirements for a distributed system to follow 2 of the 3 requirements

39 CAP Theorem • CA - Single site cluster, therefore all nodes are always in contact. When a partition occurs, the system blocks. • CP - Some data may not be accessible, but the rest is still consistent/accurate. • AP - System is still available under partitioning, but some of the data returned may be inaccurate.

40 CAP Theorem 40

NoSQL The BASE by Eric Brewer

42 The BASE  The CAP theorem states that a distributed computer system cannot guarantee all of the following three properties at the same time: Consistency Availability Partition tolerance

43 The BASE  A BASE system gives up on consistency.  Basically Available indicates that the system does guarantee availability, in terms of the CAP theorem.

44 The BASE  Soft state indicates that the state of the system may change over time, even without input. This is because of the eventual consistency model.

45 The BASE • Eventual consistency indicates that the system will become consistent over time, given that the system doesn't receive input during that time.

53 Categories of NoSQL database 3) Graph databases: Data is stored as a collection of nodes, where nodes are analogous to objects in a programming language. Nodes are connected using edges.

54 AllegroGraph, DEX, Neo4j, FlockDB, Sones GraphDB

55 Categories of NoSQL database 4) Key-value store: In Key-value-store category of NoSQL database, an user can store data in schema-less way. A key may be strings, hashes, lists, sets, sorted sets and values are stored against these keys.

56 Cassandra, Riak, Redis, memcached, BigTable etc.

57 Production deployment  There is a large number of companies using NoSQL.  Google, Facebook, Mozilla, Adobe, Foursquare, LinkedIn, Digg, McGraw-Hill Education, Vermont Public Radio

Seminar by Luca Cabibbo : Nosql db design-20140110

These presentations are classified and categorized, so you will always find everything clearly laid out and in context.
You are watching How to connect the NETGEAR Wi-Fi Range Extender presentation right now. We are staying up to date!