Exploring the Design Needs for the New Database Era EMMSAD2018, TALLINN 1

Transcription

1 Exploring the Design Needs for the New Database Era NOA ROY-HUBARA AND ARNON STURM EMMSAD2018, TALLINN 1

2 Introduction The database world has changed tremendously over the last decade. New technologies = new gaps. How do we choose the right database solution nowadays? How do we design databases nowadays? EMMSAD2018, TALLINN 2

3 Motivation When asking practitioners how do you choose a database for your application the answers varies: Agenda 50% Knowledge 30% Exploration 20% This might lead to a wrong decision regrading the database technology. EMMSAD2018, TALLINN 3

4 Research Question What database design methods exist today? How to choose the most fitting technology? What are the considerations when designing a database? EMMSAD2018, TALLINN 4

5 Background: Databases Relational, Object Oriented, NoSQL, NewSQL. NoSQL has four sub-types: Key-Value, Column Based, Document Based and Graphs. Known concepts of databases: Consistency, Integrity, Performance, Query options and Flexibility. EMMSAD2018, TALLINN 5

6 Trends EMMSAD2018, TALLINN 6

7 Database Design Traditional design has three steps: Conceptual modeling Logical modeling Physical modeling What does a good design method needs? Expressiveness Requirements of data, functionality and non functional properties Ease of use Guidelines Formality EMMSAD2018, TALLINN 7

8 Relational Database Design A known, mature and well researched process. Conceptual modeling: ERD, UML. Logical modeling: Suggest normalized tables. Physical design: actual tables on a chosen database (MSSQL, MySQL, etc), Views, etc. EMMSAD2018, TALLINN 8

9 Object Oriented Database Design Emerged at the early 1980 s. Share characteristics with programming object-oriented applications with common terms such as objects, encapsulation, inheritance, etc. Identifying classes, objects, the relations between them. Conceptual modeling can be done by UML. Logical and physical modeling are the same. EMMSAD2018, TALLINN 9

10 NoSQL Database Design 5 categories: 1. Design approaches for all NoSQL subtypes 2. Design approaches for Key-Value databases 3. Design approaches for Wide-Column Stores 4. Design approaches for Document stores 5. Design approaches for Graph databases Current research will assist in understanding needed aspects from new design methods. EMMSAD2018, TALLINN 10

11 NoSQL Database Design: Design approaches for all NoSQL subtypes Kaur and Rani: a review Expressiveness Guidelines - Formality - NoAM (Bugiotti et al.) Expressiveness Guidelines - Formality - 1. Kaur, K., Rani, R.: Modeling and querying data in NoSQL databases. In: IEEE International Conference on Big Data, pp. 1 7, October Bugiotti, F., Cabibbo, L., Atzeni, P., Torlone, R.: Database design for NoSQL systems. In: Yu, E., Dobbie, G., Jarke, M., Purao, S. (eds.) ER LNCS, vol. 8824, pp Springer, Cham (2014). EMMSAD2018, TALLINN 11

12 NoSQL Database Design: Design approaches for Key-Value stores Rossel and Manna Expressiveness Guidelines - Formality - 3. Rossel, G., Manna, A.: A modeling methodology for NoSQL key-value databases. Database Syst. J. 8(2), (2017) EMMSAD2018, TALLINN 12

13 NoSQL Database Design: Design approaches for Wide-Column stores KDM (Chebotko, Kashlev and Lu) Expressiveness Guidelines + Formality + NoSE (Mior, Aboulnaga and Liu) Expressiveness Guidelines + Formality + 4. Chebotko, A., Kashlev, A., Lu, S.: A big data modeling methodology for Apache Cassandra. In: IEEE International Congress on Big Data, pp , June Mior, M.J., Salem, K., Aboulnaga, A., Liu, R.: NoSE: schema design for NoSQL applications. IEEE Trans. Knowl. Data Eng. 29(10), (2017) EMMSAD2018, TALLINN 13

14 NoSQL Database Design: Design approaches for Wide-Column stores Boussahoua, Boussaid and Bentayeb. Expressiveness Guidelines - Formality - 6. Boussahoua, M., Boussaid, O., Bentayeb, F.: Logical schema for data warehouse on column-oriented NoSQL databases. In: Benslimane, D., Damiani, E., Grosky, W.I., Hameurlain, A., Sheth, A., Wagner, R.R. (eds.) DEXA LNCS, vol , pp Springer, Cham (2017). 4_20 EMMSAD2018, TALLINN 14

15 NoSQL Database Design: Design approaches for Document stores Vera et al. document database viewing Expressiveness Guidelines - Formality - Mason Expressiveness Guidelines - Formality - 7. Vera, H., Wagner Boaventura, M.H., Guimaraes, V., Hondo, F.: Data modeling for NoSQL document-oriented databases. In: CEUR Workshop Proceedings, vol. 1478, pp (2015) 8. Mason, R.T.: NoSQL databases and data modeling techniques for a document-oriented NoSQL database. In: Proceedings of Informing Science and IT Education Conference (InSITE), pp (2015) EMMSAD2018, TALLINN 15

16 NoSQL Database Design: Design approaches for Document stores Shin, Hwang and Jung. Expressiveness Guidelines + Formality - de Lima and dos Santos Mello Expressiveness Guidelines + Formality - 9. Shin, K., Hwang, C., Jung, H.: NoSQL database design using UML conceptual data model based on Peter Chen s framework. Int. J. Appl. Eng. Res. 12(5), (2017) 10. de Lima, C., dos Santos Mello, R.: A workload-driven logical design approach for NoSQL document databases. In: Proceedings of the 17th International Conference on Information Integration and Web-Based Applications and Services, p. 73. ACM, December 2015 EMMSAD2018, TALLINN 16

17 NoSQL Database Design: Design approaches for Graph databases De Virgilio, Maccioni and Torlone. Expressiveness Guidelines + Formality - UMLtoGraphDB (Daniel, Suny e, Cabot) Expressiveness Guidelines - Formality De Virgilio, R., Maccioni, A., Torlone, R.: Model-driven design of graph databases. In: Yu, E., Dobbie, G., Jarke, M., Purao, S. (eds.) ER LNCS, vol. 8824, pp Springer, Cham (2014) Daniel, G., Sunyé, G., Cabot, J.: UMLtoGraphDB: mapping conceptual schemas to graph databases. In: Comyn-Wattiau, I., Tanaka, K., Song, I.-Y., Yamamoto, S., Saeki, M. (eds.) ER LNCS, vol. 9974, pp Springer, Cham (2016). EMMSAD2018, TALLINN 17

18 NoSQL Database Design: Design approaches for Graph databases Akoka, Comyn-Wattiau and Prat. Expressiveness Guidelines + Formality - GDBS (Roy-Hubara et al.) Expressiveness Guidelines + Formality Akoka, J., Comyn-Wattiau, I., Prat, N.: A four V s design approach of NoSQL graph databases. In: de Cesare, S., Frank, U. (eds.) ER LNCS, vol , pp Springer, Cham (2017) Roy-Hubara, N., Rokach, L., Shapira, B., Shoval, P.: Modeling graph database schema. IT Prof. 6, (2017) EMMSAD2018, TALLINN 18

19 NewSQL Database Design NewSQL databases are stronger Relational databases. They support the same tabular structure, and same data types When designing a NewSQL database, it is probably preferable to use the same notions and methods that are done when creating a relational database. EMMSAD2018, TALLINN 19

20 Discussion Most methods uses a conceptual model, with different levels of expressiveness. Several methods uses query considerations: Their type (OLAP vs. OLTP) Their frequencies Their format NFR are hardly referred to. Most methods offer guidelines to a limited extent. Formality is addressed to a certain extent. EMMSAD2018, TALLINN 20

21 Discussion Things that has to be taken into account when designing a database, based on known methods and the suggested ones: Specify the data types and their relationships Estimate the five Vs for each of the above Analyze access patterns Assess workload Any design first step should be selecting the right technology based on the design and analysis of the application requirements! EMMSAD2018, TALLINN 21

22 Summary and Future Research The new era of databases requires rethinking of design methods. New aspects require further considerations that should be taken at early stages. A major issue - database technology is chosen a-priori. In the future we plan to further examine the design needs. We plan to address these needs within a comprehensive database design framework. EMMSAD2018, TALLINN 22

23 Thanks for listening! Questions? EMMSAD2018, TALLINN 23