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/09/24 09:47] ezimanyi [Project] |
teaching:infoh415 [2021/09/26 11:10] ezimanyi [Topics for the current academic year] |
||
|---|---|---|---|
| Line 140: | 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>" for groups of 2 students and "<Technology> with <Tool1> and <Tool2>" for groups of 4 students. | + | Students, in groups of two or four students, 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. | ||
| + | |||
| + | 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. | ||
| + | |||
| + | The choice of topic and the application must be made in agreement with the lecturer. The topic should not be included in the program of the Master in Computer Science and Engineering. The project will be presented to the lecturer and the fellow students at the end of the semester. This presentation will be supported by a slideshow. A written report containing the contents of the presentation is also required. The presentation and the report will (1) explain the foundations of the technology chosen, (2) explain how these foundations are implemented by the database management system chosen and (3) illustrate all these concepts with the application implemented. | ||
| For 2-student group, the duration of the presentation is 30 minutes. It will structured in two parts of similar length | 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 technology | ||
| - | * An introduction to the tools assessing the advantages and disadvantages of the tool tested with an example application. | + | * An introduction to the tool illustrated with an example application assessing its advantages and disadvantages. |
| For 4-student group, the duration of the presentation is 45 minutes. It will structured in three parts of similar length | For 4-student group, the duration of the presentation is 45 minutes. It will structured in three parts of similar length | ||
| Line 152: | Line 156: | ||
| * An introduction to the two tools, each presented by each group | * 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. | * 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. | ||
| - | |||
| - | The choice of topic and the application must be made in agreement with the lecturer. The topic should not be included in the program of the Master in Computer Science and Engineering. The project will be presented to the lecturer and the fellow students at the end of the semester. This presentation will be supported by a slideshow. A written report containing the contents of the presentation is also required. The presentation and the report will (1) explain the foundations of the technology chosen, (2) explain how these foundations are implemented by the database management system chosen and (3) illustrate all these concepts with the application implemented. | ||
| The evaluation of the project focuses on the following criteria: | The evaluation of the project focuses on the following criteria: | ||
| Line 194: | Line 193: | ||
| * Datawarehouses and Apache Hive: Nicole Zafalón, Andrés Espinal | * Datawarehouses and Apache Hive: Nicole Zafalón, Andrés Espinal | ||
| * Distributed databases and SQL Server: Asha Seif, Kainaat Amjid | * Distributed databases and SQL Server: Asha Seif, Kainaat Amjid | ||
| + | * Distributed Databases with DynamoDB: Loïc Caudron, Matteo Snellings | ||
| * Document stores with CouchBase and CouchDB: Mohammadreza Amini, Ossoama Benaissa, Zheng Ren, Adriana Sirbu | * Document stores with CouchBase and CouchDB: Mohammadreza Amini, Ossoama Benaissa, Zheng Ren, Adriana Sirbu | ||
| + | * Document stores and Firestore: Luca De Santos, Sacha Keserovic | ||
| * Document stores and MongoDB: Hang Yu, Zhiyang Guo | * Document stores and MongoDB: Hang Yu, Zhiyang Guo | ||
| * In-memory databases and Memcached: Diogo Repas and Sandra Hillergren | * In-memory databases and Memcached: Diogo Repas and Sandra Hillergren | ||
| Line 205: | Line 206: | ||
| * Stream databases and Apache Kafka: Vlada Kylynnyk, Mahmut Asım Onat | * 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 | * 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 with Apache Solr and ElasticSearch: Pap Sanou, Szymon Swirydowicz, Alexandre Chapelle, Nicolas Dardenne |
| - | * Search engines and ElasticSearch: Alexandre Chapelle, Nicolas Dardenne | + | |
| * XML Databases and BaseX: Maxime Renversez, Mael Touret | * XML Databases and BaseX: Maxime Renversez, Mael Touret | ||