Presentasi sedang didownload. Silahkan tunggu

Presentasi sedang didownload. Silahkan tunggu

No SQL Database Astharina W7408040036 Archi W 7408040048 Mas Dodik7408040059.

Presentasi serupa


Presentasi berjudul: "No SQL Database Astharina W7408040036 Archi W 7408040048 Mas Dodik7408040059."— Transcript presentasi:

1 No SQL Database Astharina W Archi W Mas Dodik

2 Outlines Apa itu No Sql Database ? Sejarah dan perkembangan Mengapa Menggunakan No Sql Database Klasifikasi No SQL Database Perbedaan SQL dan No SQL Database Etc.

3 Apa Itu No SQL Database Dapat juga disebut “Not Only SQL” adalah sistem manajemen database alternatif yang berbeda jauh dari model tradisional dari sistem manajemen database relasional (RDBMS) ataupun sistem manajemen database berbasis object(ODBMS). Penyimpanan data ini tidak memerlukan skema tabel tetap, biasanya menghindari joins operation dan skala horizontal, merupakan open source, cara penyimpanannya- pun tidak memerlukan inisialisasi terlebih dahulu. Dalam arti luas,cara penyimpanan data yang tidak menggunakan sql atau database relasional untuk menyimpan data. Di Populerkan oleh website besar seperti Google dan Facebook.

4 Sejarah dan Perkembangan NoSql Coined in 1998 by Carlos Strozzi to describe a database that did not expose a SQL interface In 2008, Eric Evans reintroduced the term to describe the growing non-RDBMS movement Popularized by large web sites such as Google, Facebook and Digg

5 Sejarah dan Perkembangan NoSql - Perkembangan dari situs media sosial (Facebook, Twitter) dengan kebutuhan data yang besar. - Kebutuhan akan penyimpanan data yang besar di situs web besar seperti Google, Yahoo ( Banyak data yang tidak file ). - Munculnya solusi berbasis cloud seperti Amazon S3 (solusi penyimpanan yang sederhana) - Untuk tipe data dinamis dengan seringnya perubahan skema. - Komunitas open-source.

6 Sejarah dan Perkembangan NoSql Ada tiga bahasan besar yang mendorong perkembangan NoSql : – BigTable (Google) – Dynamo (Amazon) – CAP Theorem

7 No Sql Database Karakteristik Large data volumes – Google’s “big data” Queries need to return answers quickly Mostly query, few updates Asynchronous Inserts & Updates Schema-less ACID transaction properties are not needed BASE transaction CAP Theorem Open source development

8 Transactions – ACID Properties Atomic – All of the work in a transaction completes (commit) or none of it completes Atomic – All of the work in a transaction completes (commit) or none of it completes Consistent – A transaction transforms the database from one consistent state to another consistent state. Consistency is defined in terms of constraints. Consistent – A transaction transforms the database from one consistent state to another consistent state. Consistency is defined in terms of constraints. Isolated – The results of any changes made during a transaction are not visible until the transaction has committed. Isolated – The results of any changes made during a transaction are not visible until the transaction has committed. Durable – The results of a committed transaction survive failures Durable – The results of a committed transaction survive failures

9 BASE Transactions Acronym contrived to be the opposite of ACID Acronym contrived to be the opposite of ACID – Basically Available, – Soft state, – Eventually Consistent Characteristics Characteristics – Weak consistency – stale data OK – Availability first – Best effort – Approximate answers OK – Aggressive (optimistic) – Simpler and faster

10 Keuntungan Cheap, easy to implement (open source) Data are replicated to multiple nodes (therefore identical and fault-tolerant) and can be partitioned – Down nodes easily replaced – No single point of failure Easy to distribute Don't require a schema Can scale up and down Relax the data consistency requirement (CAP)

11 NoSQL Products Cassandra CouchDB Hadoop & Hbase MongoDB StupidDB Etc.

12 Perbandingan Beberapa Aplikasi NoSQL DataBase

13

14

15 Klasifikasi No Sql Database Discussing NoSQL databases is complicated because there are a variety of types: Column Store – Each storage block contains data from only one column Document Store – stores documents made up of tagged elements Key-Value Store – Hash table of keys

16 Klasifikasi No Sql Database XML Databases Graph Databases Codasyl Databases Object Oriented Databases Distributed Peer Stores

17 2 Garis Besar NoSql NoSQL solutions fall into two major areas: – Key/Value or ‘the big hash table’. Amazon S3 (Dynamo) Voldemort Scalaris – Schema-less which comes in multiple flavors, column- based, document-based or graph-based. Cassandra (column-based) CouchDB (document-based) Neo4J (graph-based) HBase (column-based)

18 Key/Value Pros: – very fast – very scalable – simple model – able to distribute horizontally Cons: - many data structures (objects) can't be easily modeled as key value pairs

19 Schema-Less Pros: - Schema-less data model is richer than key/value pairs - eventual consistency - many are distributed - still provide excellent performance and scalability Cons: - typically no ACID transactions or joins

20 Perbedaan Dengan Database Relasional Relational – Insert data $sql = "INSERT INTO `$tbl` SET `login` = 'coba1', `password` = '0c50a2d250b30bf01aa0fabf782cb448', ` ` = mysql_query($sql); No Sql (MongoDB) – Insert data db.mahasiswa.save({nama:’FadliSaldi’,NPM:’ ′,jurus an:’Sistem Informasi’,Fakultas:’Ilmu Komputer’})

Presentasi serupa


Iklan oleh Google