This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
teaching:infoh415 [2021/08/20 21:55] ezimanyi [Links] |
teaching:infoh415 [2021/09/24 09:47] ezimanyi [Project] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== INFO-H-415: Advanced Databases ====== | ====== INFO-H-415: Advanced Databases ====== | ||
| + | |||
| + | ===== Last important announcment ==== | ||
| + | |||
| + | 21/09/2021: | ||
| + | Hello everyone, | ||
| + | |||
| + | The first exercise session will take place Thursday from 14:00-16:00 in the UB4.130 computer room. It is however strongly advised to bring your own computer and to install the required applications as indicated on the webpage of the exercise sessions (https://cs.ulb.ac.be/public/teaching/infoh415/tp, Before Session 1). | ||
| + | |||
| + | See you on Thursday, | ||
| + | |||
| + | Gilles | ||
| ===== Lecturer ===== | ===== Lecturer ===== | ||
| Line 97: | Line 108: | ||
| * IBM, A Matter of Time: Temporal Data Management in DB2 for z/OS. ({{teaching:infoh415:a_matter_of_time.pdf|version pdf}}) | * IBM, A Matter of Time: Temporal Data Management in DB2 for z/OS. ({{teaching:infoh415:a_matter_of_time.pdf|version pdf}}) | ||
| ===== Links ===== | ===== Links ===== | ||
| - | * Temporal databases | ||
| - | * [[http://timecenter.cs.aau.dk/|TimeCenter]], an international research centre for temporal databases. | ||
| - | * [[http://www.timeconsult.com/Software/Software.html|TimeDB]], a temporal relational database | ||
| * Spatial databases | * Spatial databases | ||
| - | * [[https://postgis.net/workshops/postgis-intro/|Introduction to PostGIS]] | + | * [[https://postgis.net/workshops/postgis-intro/|Introduction to PostGIS]] |
| + | * [[https://learn.crunchydata.com/postgis|Crunchy Data Interactive PostGIS Learning Portal]] | ||
| * Spatio-temporal (or mobility) databases | * Spatio-temporal (or mobility) databases | ||
| * [[https://mobilitydb.com/|MobilityDB]] | * [[https://mobilitydb.com/|MobilityDB]] | ||
| Line 108: | Line 117: | ||
| * [[http://www.objectstore.com/datasheet/index.ssp|ObjectStore]], an object database | * [[http://www.objectstore.com/datasheet/index.ssp|ObjectStore]], an object database | ||
| * [[http://www.objectivity.com|Objectivity]], an object database | * [[http://www.objectivity.com|Objectivity]], an object database | ||
| - | * [[http://sourceforge.net/projects/ozone/|Ozone]], an object database | ||
| * Post-relationnal databases | * Post-relationnal databases | ||
| - | * [[http://www.fresher.com/|Matisse]] | ||
| * [[http://www.intersystems.com/cache/index.html|Caché]] | * [[http://www.intersystems.com/cache/index.html|Caché]] | ||
| Line 133: | Line 140: | ||
| */ | */ | ||
| - | Students, in groups of two, will realize a project in a topic relevant to advanced databases. Examples of topics are given in the next section of this document. Please notice that the template for these topics is "<Technology> and <Tool>". | + | Students, in groups of two, will realize a project in a topic relevant to advanced databases. Examples of topics are given in the next section of this document. Please notice that the template for these topics is "<Technology> and <Tool>" for groups of 2 students and "<Technology> with <Tool1> and <Tool2>" for groups of 4 students. |
| Each group will study a database technology and illustrate it with an application developed in a database management system to be chosen (e.g., SQL Server, PostgreSQL, MongoDB, etc.). The topic should be addressed in a technical way, to explain the foundations of the underlying technology. The application must use the chosen technology. | Each group will study a database technology and illustrate it with an application developed in a database management system to be chosen (e.g., SQL Server, PostgreSQL, MongoDB, etc.). The topic should be addressed in a technical way, to explain the foundations of the underlying technology. The application must use the chosen technology. | ||
| + | |||
| + | For 2-student group, the duration of the presentation is 30 minutes. It will structured in two parts of similar length | ||
| + | * An introduction to the technology | ||
| + | * An introduction to the tools assessing the advantages and disadvantages of the tool tested with an example application. | ||
| + | |||
| + | For 4-student group, the duration of the presentation is 45 minutes. It will structured in three parts of similar length | ||
| + | * An introduction to technologies presented jointly by the two groups | ||
| + | * An introduction to the two tools, each presented by each group | ||
| + | * A common assessment of the advantages and disadvantages of both tools tested in a common example application. | ||
| + | |||
| It is important to understand that the objective of the project is NOT about developing an application with GUI. The objective is to benchmark the proposed tool in relation to the database requirements of your application. Therefore, it is necessary to determine the set of queries and updates that your application requires and do a benchmark with, e.g., 1K, 10K, 100K, and 1M "objects" (rows, documents, nodes, etc. depending on the technology used) to determine if the tool shows a linear or exponential behavior. As usual when performing benchmarks, the queries and updates are executed n times (e.g., 6 times where the first execution is not considered because it is different from the others since the cache structures must be filled) and the average of the execution times is computed. A comparison with traditional relational technology must be provided to show that the chosen tool is THE technology of choice for your application, better than all other alternatives, and that it will perform correctly when the system is deployed at full scale. | It is important to understand that the objective of the project is NOT about developing an application with GUI. The objective is to benchmark the proposed tool in relation to the database requirements of your application. Therefore, it is necessary to determine the set of queries and updates that your application requires and do a benchmark with, e.g., 1K, 10K, 100K, and 1M "objects" (rows, documents, nodes, etc. depending on the technology used) to determine if the tool shows a linear or exponential behavior. As usual when performing benchmarks, the queries and updates are executed n times (e.g., 6 times where the first execution is not considered because it is different from the others since the cache structures must be filled) and the average of the execution times is computed. A comparison with traditional relational technology must be provided to show that the chosen tool is THE technology of choice for your application, better than all other alternatives, and that it will perform correctly when the system is deployed at full scale. | ||
| Line 163: | Line 180: | ||
| * Multi-model databases and MarkLogic | * Multi-model databases and MarkLogic | ||
| * NewSQL databases and VoltDB | * NewSQL databases and VoltDB | ||
| - | * Object-oriented databases and db4o, ObjectBox, Perst | + | * Object-oriented databases and ObjectBox, Perst |
| * Real-time databases and Firebase | * Real-time databases and Firebase | ||
| * Search engines and Solr, ElasticSearch, Sphinx ... | * Search engines and Solr, ElasticSearch, Sphinx ... | ||
| Line 173: | Line 190: | ||
| ===== Topics for the current academic year ===== | ===== Topics for the current academic year ===== | ||
| - | * <TBD> | + | * Cloud databases and Microsoft Azure SQL: Davide Rendina, Margarita Hernandez |
| + | * Column stores and Cassandra: Md Jamiur Rahman Rifat, Khushnur Binte Jahangir | ||
| + | * Datawarehouses and Apache Hive: Nicole Zafalón, Andrés Espinal | ||
| + | * Distributed databases and SQL Server: Asha Seif, Kainaat Amjid | ||
| + | * Document stores with CouchBase and CouchDB: Mohammadreza Amini, Ossoama Benaissa, Zheng Ren, Adriana Sirbu | ||
| + | * Document stores and MongoDB: Hang Yu, Zhiyang Guo | ||
| + | * In-memory databases and Memcached: Diogo Repas and Sandra Hillergren | ||
| + | * Key-value databases with Cloud bigtable and Redis: Luiz Fonseca, Zyrako Musaj, Yanjian Zhang and Zhicheng Luo | ||
| + | * Multimedia databases and Oracle: Wassim Belgada, Imestir Ibrahim | ||
| + | * NewSQL databases and VoltDB: Nabil Souissi | ||
| + | * Object-oriented databases with ObjectBox and Perst: Filip Sotiroski, Niccolo Morabito, Andrea Gonzato, Pietro Ferrazi | ||
| + | * Real-time databases and Firebase: Himanshu Choudhary, Sergio Postigo, Tejaswini dhuppad | ||
| + | * Spatial raster databases and Rasdaman: Adam Broniewski, Victor Divi | ||
| + | * Stream databases and Apache Kafka: Vlada Kylynnyk, Mahmut Asım Onat | ||
| + | * Time series databases with Influx DB and Kdb+: Mohammad Zain Abbas, Muhammad Ismail, Yi Wu, Chonghan Li | ||
| + | * Search engines and Apache Solr: Pap Sanou, Szymon Swirydowicz | ||
| + | * Search engines and ElasticSearch: Alexandre Chapelle, Nicolas Dardenne | ||
| + | * XML Databases and BaseX: Maxime Renversez, Mael Touret | ||