Inproceedings3466: Unterschied zwischen den Versionen
Cu3805 (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „{{Publikation Erster Autor |ErsterAutorNachname=Bermbach |ErsterAutorVorname=David }} {{Publikation Author |Rank=2 |Author=Steffen Müller }} {{Publikation Author…“) |
Cu3805 (Diskussion | Beiträge) |
||
Zeile 27: | Zeile 27: | ||
|Abstract=While database schema options in relational database management systems are few and have been studied for decades, little effort has so far been devoted to NoSQL column stores. Today, schema design for column stores is still based on the gut feeling of the application developer instead of being approached systematically. This is even more critical as "good" schemas in column stores do not only depend on the data model of the application but also on the queries on that data: Poor schema design will either lead to a situation where not all queries can be answered or where some queries will show really poor performance. In this paper, we propose a systematic and informed approach to database schema design in NoSQL column stores by means of automated schema generation and application-specific schema ranking. We also show, based on a use case, that the highest-ranked schema option of our approach is at least as good as the recommendation of column store experts. | |Abstract=While database schema options in relational database management systems are few and have been studied for decades, little effort has so far been devoted to NoSQL column stores. Today, schema design for column stores is still based on the gut feeling of the application developer instead of being approached systematically. This is even more critical as "good" schemas in column stores do not only depend on the data model of the application but also on the queries on that data: Poor schema design will either lead to a situation where not all queries can be answered or where some queries will show really poor performance. In this paper, we propose a systematic and informed approach to database schema design in NoSQL column stores by means of automated schema generation and application-specific schema ranking. We also show, based on a use case, that the highest-ranked schema option of our approach is at least as good as the recommendation of column store experts. | ||
|Forschungsgruppe=Effiziente Algorithmen | |Forschungsgruppe=Effiziente Algorithmen | ||
+ | }} | ||
+ | {{Forschungsgebiet Auswahl | ||
+ | |Forschungsgebiet=Cloud Computing | ||
}} | }} |
Version vom 14. Juli 2015, 07:19 Uhr
Informed Schema Design for Column Store-based Database Services
Informed Schema Design for Column Store-based Database Services
Published: 2015
Oktober
Buchtitel: IEEE International Conference on Service Oriented Computing & Applications (SOCA)
Verlag: IEEE
Erscheinungsort: Rome
Nicht-referierte Veröffentlichung
BibTeX
Kurzfassung
While database schema options in relational database management systems are few and have been studied for decades, little effort has so far been devoted to NoSQL column stores. Today, schema design for column stores is still based on the gut feeling of the application developer instead of being approached systematically. This is even more critical as "good" schemas in column stores do not only depend on the data model of the application but also on the queries on that data: Poor schema design will either lead to a situation where not all queries can be answered or where some queries will show really poor performance. In this paper, we propose a systematic and informed approach to database schema design in NoSQL column stores by means of automated schema generation and application-specific schema ranking. We also show, based on a use case, that the highest-ranked schema option of our approach is at least as good as the recommendation of column store experts.