Human Factors of XR: Using Human Factors to Design XR Systems
No sql
1.
2. Database Categories
RDBMS/OLTP
NO SQL/ Big data
DSS/OLAP/DW
RDBMS
MY SQL
MS SQL
DB2
NETEZZA
SAP HANA
ORACLE EXPRESS
MONOGO DB
HBASE
CASSANDRA
COUCHDB
ETL
Analytics, reporting,
grouping or
summarizing of data.
3. Why NoSQL?
• Nature of data. (Variety)
• High coding velocity and agility. (new columns and field can be added on the fly)
• High volume of semi and unstructured data.
• Distributed architecture (This will provide better speed).
• RDBMS was not able to cater todays request.
• RDBMs are too costly.
• No Fixed Schema
6. What is NoSQL? (Cont.)
• 3rd Generation database.
• NOT Only SQL
• Non relational
• Distributed architecture
• Open source
• Horizontal scaling
• Easy and simple to use.
7. Benefits of NoSQL?
• Can handle Big Data. (Large volumes of structured, semi structured
and unstructured data)
12. CAP Theorem
CAP Theorem states there are 3 basic requirements which exist in a special
relation when designing applications for a distributed architecture.
• Data in the database remains constant after the execution of an operation. For example after an update
operation all clients see same data.Consistency:
• This means system is always on.Availability:
• This means system continues to function even the communication among system is unreliable. i.e.
servers may be partitioned into multiple groups that cannot communicate with one another.
• Or in other words out of 20 machines if 2 machines are down still I should be able to respond to clients.
Partition Tolerance:
14. BASE (Gives up on consistency)
Basically
Available
It does guarantee
availability it terms of
CAP theorem.
Soft State
Sate of the system may
change over time, even
without input. This is
because eventual
consistency model.
Eventual
consistency
System will be
consistent over time,
given that system
doesn't receive input
during that time.