To see the other types of publications on this topic, follow the link: NoSQL.
Dissertations / Theses on the topic 'NoSQL'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'NoSQL.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Souza, Jane Adriana. "NoSQL2 : administrando banco de dados NoSQL com a linguagem SQL." reponame:Repositório Institucional da UnB, 2016. http://repositorio.unb.br/handle/10482/22948.
Full textAbstract:
Dissertação (mestrado)—Universidade de Brasília, Instituto de Ciências Exatas, Departamento de Ciência da Computação, 2016.Submitted by Albânia Cézar de Melo (albania@bce.unb.br) on 2017-02-15T12:23:44Z No. of bitstreams: 1 2016_JaneAdrianaSouza.pdf: 1805634 bytes, checksum: be4f8c819c44b36ff04c685db1485101 (MD5)
Approved for entry into archive by Raquel Viana(raquelviana@bce.unb.br) on 2017-03-17T17:00:26Z (GMT) No. of bitstreams: 1 2016_JaneAdrianaSouza.pdf: 1805634 bytes, checksum: be4f8c819c44b36ff04c685db1485101 (MD5)
Made available in DSpace on 2017-03-17T17:00:26Z (GMT). No. of bitstreams: 1 2016_JaneAdrianaSouza.pdf: 1805634 bytes, checksum: be4f8c819c44b36ff04c685db1485101 (MD5)
Nos últimos anos, novos modelos de banco de dados, chamados NoSQL (Not Only SQL) estão sendo considerados alternativas para a gestão de grandes volumes de dados - Big Data, pois gerenciam e armazenam os dados de forma eficiente, possuem alta escalabilidade, disponibilidade e desempenho satisfatório. A administração de bancos de dados implica na execução de tarefas, tais como criação de bases e objetos, atribuição de privilégios, realização de backups, dentre outras atividades. A execução dessas tarefas de administração em bancos de dados NoSQL exige um maior nível de conhecimento por parte dos administradores de bancos de dados (DBA), e expõe questões relacionadas à falta de familiaridade desses profissionais nos ambientes NoSQL. De forma a contribuir nesse campo de estudo, a presente dissertação apresenta a solução NoSQL2 para execução de tarefas de administração, usando a linguagem SQL (Structured Query Language), que funciona em diferentes Sistemas Gerenciadores de Bancos de Dados (SGBD) NoSQL. O NoSQL2 permite aos DBAs se desvincularem das particularidades de formas de acesso de cada NoSQL, pois disponibiliza recursos para conversão de comandos da sintaxe SQL para a sintaxe proprietária do banco de dados NoSQL.
New database models, called NoSQL (Not Only SQL) are considered appropriate alternatives for managing and storing Big Data due to their efficiency, high scalability, availability and performance. Database administration effects tasks such as creating databases and objects, attributing priorities and performing backups. The execution of these tasks, in NoSQL databases, require that DBA (database administrators) have a high level of knowledge, and often exposes problems with the DBA unfamiliarity of the NoSQL environments. In order to contribute to the scholarship in this field, this paper presents the middleware NoSQL2 to perform management tasks using the SQL language, which runs on different NoSQL databases. The NoSQL2 allows DBA to disassociate themselves from the particularities of access forms of each NoSQL, since provides resources for converting SQL commands to the proprietary NoSQL database syntax.
2
Erven, Gustavo Cordeiro Galvão van. "MDG-NoSQL : modelo de dados para bancos NoSQL baseados em grafos." reponame:Repositório Institucional da UnB, 2015. http://dx.doi.org/10.26512/2015.03.D.18992.
Full textAbstract:
Dissertação (mestrado)—Universidade de Brasília, Instituto de Ciências Exatas, Departamento de Ciência da Computação, 2015.Submitted by Raquel Viana (raquelviana@bce.unb.br) on 2015-11-03T18:43:12Z No. of bitstreams: 1 2015_GustavoCordeiroGalvãoVanErven.pdf: 2937303 bytes, checksum: afdc1b126b59eacc4b9a3b62bc412d1b (MD5)
Approved for entry into archive by Marília Freitas(marilia@bce.unb.br) on 2015-12-20T16:23:49Z (GMT) No. of bitstreams: 1 2015_GustavoCordeiroGalvãoVanErven.pdf: 2937303 bytes, checksum: afdc1b126b59eacc4b9a3b62bc412d1b (MD5)
Made available in DSpace on 2015-12-20T16:23:49Z (GMT). No. of bitstreams: 1 2015_GustavoCordeiroGalvãoVanErven.pdf: 2937303 bytes, checksum: afdc1b126b59eacc4b9a3b62bc412d1b (MD5)
Os bancos de dados em grafo vêm se tornando populares juntamente com as demais iniciativas NoSQL. Porém, os bancos de dados em grafos não possuem uma notação padrão. Sendo assim, o presente trabalho agrupa diversas notações e propostas de modelagem em grafos, construindo um novo modelo, chamado de Modelo de Dados para Bancos NoSQL Baseados em Grafos (MDG-NoSQL), com recursos para agrupar em uma notação as características dos bancos de dados em grafos. Esse modelo foi validado utilizando a implementação de um banco de dados de vínculos societários de empresas, combinados com os relacionamentos dessas pessoas jurídicas com os processos de compras, também chamadas de licitações, junto ao Governo Federal (Banco de Vínculos Simpli_cado para Licitações e Sociedades). Esse estudo de caso foi direcionado para auxiliar na detecção de fraudes em processos licitatórios que, além de ser diretamente aplicável a vários órgãos de controle, perícia e inteligência em âmbito nacional, permite extrair fundamentos extens íveis a outros problemas com modelagens de vínculos.
Currently, Graph Databases are becoming popular along with other NoSQL initiatives. Thus, researchers and companies have been developing data models to manipulate information as graphs However, there is no standard notation involves several features and structures of the graph databases. This model introduces several notations and concepts for building a new graph data model, called Data Model for NoSQL Graph Databases (GDM-NoSQL). The GDM-NoSQL was veri_ed through a database for investigate relationships between companies and people as well as information about the procurements that these companies participated in with the Federal Government. This database was designed to facilitate the process of searching for frauds and to be used on multiple contexts, i.e. several di_erent national agencies. Finally, the designed model was implemented in both a relational and a graph database in order to validate the hypothesis that writing relationships is simpler and more e_cient in graph models than relational databases.
3
Santos, Nuno Filipe Vieira dos. "Context storage using NoSQL." Master's thesis, Universidade de Aveiro, 2011. http://hdl.handle.net/10773/7586.
Full textAbstract:
Mestrado em Engenharia de Computadores e TelemáticaThis thesis proposes the usage of an upcoming new breed of databases, called NoSQL, for the storage and management of context information, in a context management architecture based on XCoA (XMPP-based Context Architecture). In this context management architecture all context information is published on a central component called Context Broker, and stored for further requisition, processing and analysis. Due to the high number of published context data, traditional databases quickly develop serious performance limitations, which in turn may jeopardize the XMPP protocol’s efficiency; alternatively, NoSQL databases show serious performance improvements in the storage and management of large-scale data sets. This thesis presents a study of the several available NoSQL solutions, and presents the advantages and disadvantages of the usage of a specific solution in this type of problem.
O presente trabalho propõe o uso de uma nova geração de bases de dados, denominadas NoSQL, para o armazenamento e gestão de informação de contexto, assente numa arquitectura de gestão contexto baseada em XCoA (XMPP-based Context Architecture). Nesta arquitectura de gestão de contexto toda a informação de contexto é publicada num componente central, denominado Context Broker, e armazenada para posterior requisição, processamento e análise. Dado o elevado volume de informação de contexto publicada, as bases de dados tradicionais rapidamente apresentam limitações de desempenho, que por sua vez poem em causa a eficiência do funcionamento do protocolo XMPP; pelo contrário, as bases de dados NoSQL apresentam serias melhorias de desempenho na gestão de bases de dados de grande dimensão. Este trabalho estuda várias soluções NoSQL existentes, e apresenta as vantagens e desvantagens do uso de uma solução específica neste tipo de problema.
4
Bergquist, Jan-Halvard, Fredrik Lindgren, and Linda Nguyen. "NoSQL! : Med rätt att finnas?" Thesis, Örebro universitet, Handelshögskolan vid Örebro Universitet, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-42574.
Full text
5
Заворотна, М. Г. "Высокопроизводительные нереляционные базы данных NOSQL." Thesis, Kharkiv National University of Radio Electronics, 2018. http://openarchive.nure.ua/handle/document/7846.
Full textAbstract:
The current relational database management systems are debugged mechanisms created for storing data and building queries to them. Since the creation of the data, the systems have become more sophisticated in terms of security and operability. As progress does not stand still, the amount of useful information in the world is steadily increasing, remaining, or becoming impossible. To solve these tasks and process the flow, structured and unstructured data of huge data, NoSQL approaches were created for the implementation of database stores.
6
Persson, Ragnvald. "NoSQL-databaser i socialt nätverk." Thesis, Malmö universitet, Fakulteten för teknik och samhälle (TS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20692.
Full textAbstract:
Syftet med studien är att göra en fördjupning inom NoSQL-databaser och undersöka vilka uppgifter som de olika NoSQL-grupperna passar bäst till i ett socialt nätverk, som t.ex. Facebook och Twitter. Det finns fyra olika typer av NoSQL-databaser: kolumndatabaser, grafdatabaser, nyckelvärdedatabaser och dokumentdatabaser. Frågan är vilken NoSQL-databas ska man välja till en viss uppgift i ett givet socialt nätverk. När man ska utveckla ett socialt nätverk, som kräver lagring av data, är det viktigt att känna till vilken typ av databas som bör användas till en vis typ av uppgift. För att få svar på frågorna har det gjorts en undersökning över vad tidigare forskning har kommit fram till. Det har även gjorts en praktisk studie med alla fyra NoSQL-grupper i ett experiment med lagring av användaruppgifter, meddelanden och vänner.The purpose of the study is to deepen within NoSQL databases and investigate what tasks the different NoSQL groups fit best in a social network, such as Facebook and Twitter. The data is, for example, about the storage of personal data or social networking. There are four different types of NoSQL databases: column databases, graph databases, key value databases and document databases. The question is which NoSQL database should be chosen for a particular task in a given social network. When developing a social network that requires data storage, it is important to know what kind of database should be used for a certain type of task.In order to answer the questions, an investigation has been made of what previous research has reached. There has also been a practical study of all four NoSQL groups in an experiment with storing user information, messages and friends.
7
Hesselryd, Jonas. "En utredning av NoSQL för iipax." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-70154.
Full textAbstract:
NoSQL är ett omtalat ämne just nu. Det finns mycket som talar för att det ska lösa de problem relationsdatabaser lider av. Exempelvis onödigt resurskräavande system eller svårt att konvertera mellan olika format på data. Att lösa dessa problem är något Ida Infront är intresserade av för lagringen i deras ärendehanteringsplattform iipax. Uppgiften är att ta reda på vad NoSQL-begreppet faktiskt innebär och utvärdera utvalda databaser mot Ida Infront och iipax krav. Problemet har angripits genom en litteraturstudie av NoSQL för att sedan undersöka tre databaser: Neo4J, CouchDB och Cassandra. Implementationerna har undersökts för att ge en bättre bild av vad NoSQL innebär i praktiken. Resultatet av arbetet är att NoSQL är ett väldigt diffust begrepp där många är oense om vad som gäller. Det är några olika typer av databaser som räknas till NoSQL men de i sig är ingen definition av begreppet. Olika typer som ofta nämns är dokument, graf och kolumndatabaser. När det kommer till de specifika databaserna ser de ut att ha spännande egenskaper som kan passa iipax, till exempel bra datamodell eller stöd för fulltextindexering. Slutligen kan det sägas att Neo4J i dagsläget ser ut som den bästakandidaten för lagringen i iipax.
8
Björklund, Anna. "NoSQL Database for Software Project Data." Thesis, Umeå universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-43838.
Full textAbstract:
The field of databases have exploded in the last couple of years. New architectures try to meet the need to store more and more data and new kinds of data. The old relational model is no longer the only way and the NoSQL movement is not a trend but a new way of making the database fit the data, not the other way around.This master thesis report aims to find an efficient and well designed solution for storing and retrieving huge amounts of software project data at Tieto. It starts by looking at different architectures and trying three to see if any of them can solve the problem. The three databases selected are the relational database PostgreSQL, the graph database Neo4j and the key value store Berkeley DB. These are all implemented as a Web service and time is measured to find out which, if any, can handle the data at Tieto. In the end it is clear that the best database for Tieto is Berkeley DB. Even if Neo4j is almost as fast, it is still new and not as mature as Berkeley DB.
9
Панферова, И. Ю. "Модели построения мобильной NOSQL базы данных." Thesis, НТМТ, 2015. http://openarchive.nure.ua/handle/document/8318.
Full text
10
Mendoza, Jayo Rubén Gilmar, and Castro José Gabriel Medina. "NoSQL: futuro de almacenamiento de datos." Bachelor's thesis, Universidad Peruana de Ciencias Aplicadas (UPC), 2015. http://hdl.handle.net/10757/552364.
Full textAbstract:
The current existence of a behavior or prejudice that indicates that the non-relational model-oriented databases are not competitive compared to the relational model, associated with the lack of interest or lack of education for it professionals on the benefits of NoSQL solutions, and, because, considering that the non-relational model-oriented databases systems just are not in a phase of initiation, they have generated the dilemma that produces is research. The research project seeks to generate a comparative analysis between the relational data model and relational enabling to contribute to a point of view concerning the potential of the NoSQL. This triggered the generation of the proposed migration procedure relational data model to the non-relational and from that reveal the management involved in the development of prototype migration tool based on an experimental architecture outlined in the proposal (RoboSQL) and Finally, benchmarking resulting response time and scalability. The contribution becomes the comparative analysis of data models, which allows a useful reference for translation into relational terminology to non-relational by determining equivalences and differences. This was from the standard properties in data models: structure, constraints and operations. Comparing indicators response time, through a case by case scenarios, reveal that a NoSQL, in most contexts, it is more optimal for their inherent characteristics and performance that has on a given environment. On the side of scalability, evidenced by the variances of data loading and hardware, turned out to be outstanding product NoSQL to their relational counterparts.La actual existencia de un comportamiento o prejuicio que indica que las bases de datos orientadas al modelo no relacional no son competitivas frente al modelo relacional, así como el desinterés o la carencia de educación de los profesionales de tecnologías de la información (TI) en cuanto a los beneficios de las soluciones NoSQL han generado el dilema que produce está investigación. A esto se le suma el considerar que los sistemas de bases de datos orientados al modelo no relacional recién se encuentran en una fase de iniciación. El proyecto de investigación busca generar un análisis comparativo entre el modelo de datos relacional y no relacional que permita contribuir a engrandecer un punto de vista relacionado a las potencialidades de las NoSQL. Se hizo la propuesta de procedimiento de migración del modelo de datos relacional hacia el no relacional y a partir de este revelar la gestión involucrada en el desarrollo de la herramienta prototipo de migración (RoboSQL) basada en una arquitectura experimental expuesta en la propuesta y, finalmente, el benchmarking resultante de tiempo de respuesta y escalabilidad. El aporte se constituye en el análisis comparativo de modelos de datos, el cual permite tener una referencia útil para la traslación de terminología relacional hacia la no relacional a través de la determinación de equivalencias y diferencias. Ello fue a partir de las propiedades estándares en los modelos de datos: estructura, restricciones y operaciones. Los indicadores de comparación de tiempo de respuesta, a través de escenarios en una casuística, revelan que una NoSQL, en la mayoría de contextos, es más óptima por sus características inherentes y el desempeño que tiene sobre un determinado ambiente. Por el lado de la escalabilidad, evidenciada a través de las varianzas de carga de datos y hardware, resultó ser sobresaliente el producto NoSQL ante su contraparte relacional.
Tesis
11
Wong, Leung. "Analysis of NoSQL Storage in the Cloud." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-89990.
Full textAbstract:
Data storage is essential in many Internet services today. As the amountof generated data increases every day a way to store is needed. Relationaldatabases do not handle continuous growing data well. An option to it is touse NoSQL. XDIN Link¨ping is interested in developing an Internet serviceowhich uses non-relational type of data storage to store structured data. Thedata should be accessible to members of the service. The data storage doesnot make any assumption on what type of data is stored. Instead tags thatare attached to each entity are used to verify what type of data it is stored.This thesis provides a description of what NoSQL is and along with it theproposed database designs. Further it aims to investigate if it is reasonableto create a web service which uses NoSQL as the backend storage.
12
Rafique, Ansar. "Evaluating NOSQL Technologies for Historical Financial Data." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-193564.
Full textAbstract:
Today, when businesses and organizations are generating huge volumes of data; the applications like Web 2.0 or social networking requires processing of petabytes of data. Stock Exchange Systems are among the ones that process large amount of quotes and trades on a daily basis. The limited database storage ability is a major bottleneck in meeting up the challenge of providing efficient access to information. Further to this, varying data are the major source of information for the financial industry. This data needs to be read and written efficiently in the database; this is quite costly when it comes to traditional Relational Database Management System. RDBMS is good for different scenarios and can handle certain types of data very well, but it isn’t always the perfect choice. The existence of innovative architectures allows the storage of large data in an efficient manner. “Not only SQL” brings an effective solution through the provision of an efficient information storage capability. NOSQL is an umbrella term for various new data store. The NOSQL databases have gained popularity due to different factors that include their open source nature, existence of non-relational data store, high-performance, fault-tolerance, and scalability to name a few. Nowadays, NOSQL databases are rapidly gaining popularity because of the advantages that they offer compared to RDBMS. The major aim of this research is to find an efficient solution for storing and processing the huge volume of data for certain variants. The study is based on choosing a reliable, distributed, and efficient NOSQL database at Cinnober Financial Technology AB. The research majorly explores NOSQL databases and discusses issues with RDBMS; eventually selecting a database, which is best suited for financial data management. It is an attempt to contribute the current research in the field of NOSQL databases which compares one such NOSQL database Apache Cassandra with Apache Lucene and the traditional relational database MySQL for financial management. The main focus is to find out which database is the preferred choice for different variants. In this regard, the performance test framework for a selected set of candidates has also been taken into consideration.
13
Pretorius, Dawid Johannes. "NoSQL database considerations and implications for businesses." Thesis, Stellenbosch : Stellenbosch University, 2013. http://hdl.handle.net/10019.1/85727.
Full textAbstract:
Thesis (MComm)--Stellenbosch University, 2013.ENGLISH ABSTRACT: NoSQL databases, a new way of storing and retrieving data, can provide businesses with many benefits, although they also pose many risks for businesses. The lack of knowledge among decision-makers of businesses regarding NoSQL databases can lead to risks left unaddressed and missed opportunities. This study, by means of an extensive literature review, identifies the key drivers, characteristics and benefits of a NoSQL database, thereby providing a clear understanding of the subject. The business imperatives related to NoSQL databases are also identified and discussed. This can help businesses to determine whether a NoSQL database might be a viable solution, and to align business and information technology (IT) objectives. The key strategic and operational IT risks are also identified and discussed, based on the literature review. This can help business to ensure that the risks related to the use of NoSQL databases are appropriately addressed. Lastly, the identified risks were mapped to the processes of COBIT (Control Objectives for Information and Related Technology) to inform a business of the highest risk areas and the associated focus areas.
AFRIKAANSE OPSOMMING: NoSQL databasisse, 'n nuwe manier om data te stoor en herwin, het die potensiaal om baie voordele vir besighede in te hou, maar kan ook baie risiko's teweeg bring. Gebrekkige kennis onder besigheidsbesluitnemers oor NoSQL databasisse kan lei tot onaangespreekte risiko’s en verlore geleenthede. Hierdie studie, deur middel van 'n uitgebreide literatuuroorsig, identifiseer die sleutel eienskappe, kenmerke en voordele van 'n NoSQL databasis, om sodoende 'n duidelike begrip van die onderwerp te verkry. Die besigheidsimperatiewe wat verband hou met NoSQL databasisse is ook geïdentifiseer en bespreek. Dit kan besighede help om te bepaal of 'n NoSQL databasis 'n werkbare oplossing kan wees, asook sake- en inligtingstegnologie (IT) doelwitte in lyn met mekaar bring. Na aanleiding van die literatuurstudie is die sleutel-strategiese en operasionele IT-risiko's geïdentifiseer en bespreek. Dit kan help om aan besighede sekerheid te verskaf dat die risiko's wat verband hou met die gebruik van NoSQL databasisse toepaslik aangespreek word. Laastens is die geïdentifiseerde risiko's gekoppel aan die prosesse van COBIT om 'n besigheid van die hoë-risiko areas en die gepaardgaande fokusareas in te lig.
14
Ben, Hamadou Hamdi. "Querying heterogeneous data in NoSQL document stores." Thesis, Toulouse 3, 2019. http://www.theses.fr/2019TOU30146.
Full textAbstract:
La problématique de cette thèse porte sur l'interrogation de données hétérogènes dans les systèmes de stockage "not-only SQL" (noSQL) orientés documents. Ces derniers ont connu un important développement ces dernières années en raison de leur capacité à gérer de manière flexible et efficace d'importantes masses de documents. Ils reposent sur le principe "schema-less" consistant à ne plus considérer un schéma unique pour un ensemble de données, appelé collection de documents. Cette flexibilité dans la structuration des données complexifie l'interrogation pour les utilisateurs qui doivent connaître l'ensemble des différents schémas des données manipulées lors de l'écriture de requêtes. Les travaux développés dans cette thèse sont menés dans le cadre du projet neoCampus. Ils se focalisent sur l'interrogation de documents structurellement hétérogènes, en particulier sur le problème de schémas variables. Nous proposons la construction d'un dictionnaire de données qui permet de retrouver tous les schémas des documents. Chaque clef, entrée du dictionnaire, correspond à un chemin absolu ou partiel existant dans au moins un document de la collection. Cette clef est associée aux différents chemins absolus correspondants dans l'ensemble de la collection de documents. Le dictionnaire est alors exploité pour réécrire de manière automatique et transparente les requêtes des utilisateurs. Les requêtes utilisateurs sont établies sur la base des clés du dictionnaire (chemins partiels ou absolus) et sont automatiquement réécrites en exploitant le dictionnaire afin de prendre en compte l'ensemble des chemins absolus existants dans les documents de la collection. Dans cette thèse, nous menons une étude de l'état de l'art des travaux s'attachant à résoudre l'interrogation de documents structurellement hétérogènes, et nous en proposons une classification. Ensuite, nous comparons ces travaux en fonction de critères qui permettent de positionner et différencier notre contribution. Nous définissions formellement les concepts classiques liés aux systèmes orientés documents (document, collection, etc), puis nous étendons cette formalisation par des concepts supplémentaires : chemins absolus et partiels, schémas de document, dictionnaire. Pour la manipulation et l'interrogation des documents, nous définissons un noyau algébrique minimal fermé composé de cinq opérateurs : sélection, projection, des-imbrication (unnest), agrégation et jointure (left-join). Nous définissons chaque opérateur et expliquons son évaluation par un moteur de requête classique. Ensuite, nous établissons la réécriture de chacun des opérateurs à partir du dictionnaire. Nous définissons le processus de réécriture des requêtes utilisateurs qui produit une requête évaluable par un moteur de requête classique en conservant la logique des opérateurs classiques (chemins inexistants, valeurs nulles). Nous montrons comment la réécriture d'une requête initialement construite avec des chemins partiels et/ou absolus permet de résoudre le problème d'hétérogénéité structurelle des documents. Enfin, nous menons des expérimentations afin de valider les concepts formels que nous introduisons tout au long de cette thèse. Nous évaluons la construction et la maintenance du dictionnaire en changeant la configuration en termes de nombre de structures par collection étudiée et de taille de collection. Puis, nous évaluons le moteur de réécriture de requêtes en le comparant à une évaluation de requête dans un contexte sans hétérogénéité structurelle puis dans un contexte de multi-requêtes. Toutes nos expérimentations ont été menées sur des collection synthétiques avec plusieurs niveaux d'imbrications, différents nombres de structure par collection, et différentes tailles de collections. Récemment, nous avons intégré notre contribution dans le projet neOCampus afin de gérer l'hétérogénéité lors de l'interrogation des données de capteurs implantés dans le campus de l'université Toulouse III-Paul SabatierThis thesis discusses the problems related to querying heterogeneous data in document-oriented systems. Document-oriented "not-only SQL" (noSQL) storage systems have undergone significant development in recent years due to their ability to manage large amounts of documents in a flexible and efficient manner. These systems rely on the "schema-less" concept where no there is no requirement to consider a single schema for a set of data, called a collection of documents. This flexibility in data structures makes the query formulation more complex and users need to know all the different schemas of the data manipulated during the query formulation. The work developed in this thesis subscribes into the frame of neOCampus project. It focuses on issues in the manipulation and the querying of structurally heterogeneous document collections, mainly the problem of variable schemas. We propose the construction of a dictionary of data that makes it possible to find all the schemas of the documents. Each key, a dictionary entry, corresponds to an absolute or partial path existing in at least one document of the collection. This key is associated to all the corresponding absolute paths throughout the collection of heterogeneous documents. The dictionary is then exploited to automatically and transparently reformulate queries from users. The user queries are formulated using the dictionary keys (partial or absolute paths) and are automatically reformulated using the dictionary to consider all the existing paths in all documents in the collection. In this thesis, we conduct a state-of-the-art survey of the work related to solving the problem of querying data of heterogeneous structures, and we propose a classification. Then, we compare these works according to criteria that make it possible to position our contribution. We formally define the classical concepts related to document-oriented systems (document, collection, etc). Then, we extend this formalisation with additional concepts: absolute and partial paths, document schemas, dictionary. For manipulating and querying heterogeneous documents, we define a closed minimal algebraic kernel composed of five operators: selection, projection, unnest, aggregation and join (left join). We define each operator and explain its classical evaluation by the native document querying engine. Then we establish the reformulation rules of each of these operators based on the use of the dictionary. We define the process of reformulating user queries that produces a query that can be evaluated by most document querying engines while keeping the logic of the classical operators (misleading paths, null values). We show how the reformulation of a query initially constructed with partial and/or absolute paths makes it possible to solve the problem of structural heterogeneity of documents. Finally, we conduct experiments to validate the formal concepts that we introduce throughout this thesis. We evaluate the construction and maintenance of the dictionary by changing the configuration in terms of number of structures per collection studied and collection size. Then, we evaluate the query reformulation engine by comparing it to a query evaluation in a context without structural heterogeneity and then in a context of executing multiple queries. All our experiments were conducted on synthetic collections with several levels of nesting, different numbers of structures per collection, and on varying collection sizes. Recently, we deployed our contributions in the neOCampus project to query heterogeneous sensors data installed at different classrooms and the library at the campus of the university of Toulouse III-Paul Sabatier
15
Bacchiani, Lorenzo. "Sistemi NoSQL Lite: studio approfondito su Couchbase Lite." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2018.
Find full text
16
Höggren, Lindahl Patrik, and Klas Tärnström. "Utvecklares upplevda problematik vid användande av NoSQL-databaser." Thesis, Örebro universitet, Handelshögskolan vid Örebro Universitet, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-56967.
Full text
17
Nilsson, Christoffer, and John Bengtson. "Storage and Transformation for Data Analysis Using NoSQL." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-142004.
Full textAbstract:
It can be difficult to choose the right NoSQL DBMS, and some systems lack sufficient research and evaluation. There are also tools for moving and transforming data between DBMS' in order to combine or use different systems for different use cases. We have described a use case, based on requirements related to the quality attributes Consistency, Scalability, and Performance. For the Performance attribute, focus is fast insertions and full-text search queries on a large dataset of forum posts. The evaluation was performed on two NoSQL DBMS' and two tools for transforming data between them. The DBMS' are MongoDB and Elasticsearch, and the transformation tools are NotaQL and Compose's Transporter. The purpose is to evaluate three different NoSQL systems, pure MongoDB, pure Elasticsearch and a combination of the two. The results show that MongoDB is faster when performing simple full-text search queries, but otherwise slower. This means that Elasticsearch is the primary choice regarding insertion and complex full-text search query performance. MongoDB is however regarded as a more stable and well-tested system. When it comes to scalability, MongoDB is better suited for a system where the dataset increases over time due to its simple addition of more shards. While Elasticsearch is better for a system which starts off with a large amount of data since it has faster insertion speeds and a more effective process for data distribution among existing shards. In general NotaQL is not as fast as Transporter, but can handle aggregations and nested fields which Transporter does not support. A combined system using MongoDB as primary data store and Elasticsearch as secondary data store could be used to achieve fast full-text search queries for all types of expressions, simple and complex.
18
Yin, Suna. "Creating NoSQL Database Functionality on the SensibleThings Platform." Thesis, Mittuniversitetet, Avdelningen för informations- och kommunikationssystem, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-25504.
Full text
19
Nygaard, Knut, and Eivind Siqveland Larsen. "Automatic scaling and maintenance of a NoSQL database." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2014. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-26758.
Full textAbstract:
NoSQL databases often support scalability and high availability. We address Voldemort, which is a popular, highly available NoSQL database that can be run on several nodes. Voldemort can be cumbersome to setup and maintain. As clusters grow in size, scaling into hundreds of nodes, management and administrative tasks become increasingly complex. We have therefore focused on automating management of a running cluster of nodes.We have migrated the configuration storage of the Voldemort database from local XML files on disk to global objects using Apache ZooKeeper.Using native tools and ZooKeeper coordination, we have implemented a fault tolerant, redundant management service. The service manages node discovery, configuration generation and propagation. It also has components for live monitoring and adjustment of responsibility to match each nodes available system resources.
20
Ogunyadeka, Adewole C. "Transactions and data management in NoSQL cloud databases." Thesis, Oxford Brookes University, 2016. https://radar.brookes.ac.uk/radar/items/c87fa049-f8c7-4b9e-a27c-3c106fcda018/1/.
Full textAbstract:
NoSQL databases have become the preferred option for storing and processing data in cloud computing as they are capable of providing high data availability, scalability and efficiency. But in order to achieve these attributes, NoSQL databases make certain trade-offs. First, NoSQL databases cannot guarantee strong consistency of data. They only guarantee a weaker consistency which is based on eventual consistency model. Second, NoSQL databases adopt a simple data model which makes it easy for data to be scaled across multiple nodes. Third, NoSQL databases do not support table joins and referential integrity which by implication, means they cannot implement complex queries. The combination of these factors implies that NoSQL databases cannot support transactions. Motivated by these crucial issues this thesis investigates into the transactions and data management in NoSQL databases. It presents a novel approach that implements transactional support for NoSQL databases in order to ensure stronger data consistency and provide appropriate level of performance. The novelty lies in the design of a Multi-Key transaction model that guarantees the standard properties of transactions in order to ensure stronger consistency and integrity of data. The model is implemented in a novel loosely-coupled architecture that separates the implementation of transactional logic from the underlying data thus ensuring transparency and abstraction in cloud and NoSQL databases. The proposed approach is validated through the development of a prototype system using real MongoDB system. An extended version of the standard Yahoo! Cloud Services Benchmark (YCSB) has been used in order to test and evaluate the proposed approach. Various experiments have been conducted and sets of results have been generated. The results show that the proposed approach meets the research objectives. It maintains stronger consistency of cloud data as well as appropriate level of reliability and performance.
21
El, Malki Mohammed. "Modélisation NoSQL des entrepôts de données multidimensionnelles massives." Thesis, Toulouse 2, 2016. http://www.theses.fr/2016TOU20139/document.
Full textAbstract:
Les systèmes d’aide à la décision occupent une place prépondérante au sein des entreprises et des grandes organisations, pour permettre des analyses dédiées à la prise de décisions. Avec l’avènement du big data, le volume des données d’analyses atteint des tailles critiques, défiant les approches classiques d’entreposage de données, dont les solutions actuelles reposent principalement sur des bases de données R-OLAP. Avec l’apparition des grandes plateformes Web telles que Google, Facebook, Twitter, Amazon… des solutions pour gérer les mégadonnées (Big Data) ont été développées et appelées « Not Only SQL ». Ces nouvelles approches constituent une voie intéressante pour la construction des entrepôts de données multidimensionnelles capables de supporter des grandes masses de données. La remise en cause de l’approche R-OLAP nécessite de revisiter les principes de la modélisation des entrepôts de données multidimensionnelles. Dans ce manuscrit, nous avons proposé des processus d’implantation des entrepôts de données multidimensionnelles avec les modèles NoSQL. Nous avons défini quatre processus pour chacun des deux modèles NoSQL orienté colonnes et orienté documents. De plus, le contexte NoSQL rend également plus complexe le calcul efficace de pré-agrégats qui sont habituellement mis en place dans le contexte ROLAP (treillis). Nous avons élargis nos processus d’implantations pour prendre en compte la construction du treillis dans les deux modèles retenus.Comme il est difficile de choisir une seule implantation NoSQL supportant efficacement tous les traitements applicables, nous avons proposé deux processus de traductions, le premier concerne des processus intra-modèles, c’est-à-dire des règles de passage d’une implantation à une autre implantation du même modèle logique NoSQL, tandis que le second processus définit les règles de transformation d’une implantation d’un modèle logique vers une autre implantation d’un autre modèle logiqueDecision support systems occupy a large space in companies and large organizations in order to enable analyzes dedicated to decision making. With the advent of big data, the volume of analyzed data reaches critical sizes, challenging conventional approaches to data warehousing, for which current solutions are mainly based on R-OLAP databases. With the emergence of major Web platforms such as Google, Facebook, Twitter, Amazon...etc, many solutions to process big data are developed and called "Not Only SQL". These new approaches are an interesting attempt to build multidimensional data warehouse capable of handling large volumes of data. The questioning of the R-OLAP approach requires revisiting the principles of modeling multidimensional data warehouses.In this manuscript, we proposed implementation processes of multidimensional data warehouses with NoSQL models. We defined four processes for each model; an oriented NoSQL column model and an oriented documents model. Each of these processes fosters a specific treatment. Moreover, the NoSQL context adds complexity to the computation of effective pre-aggregates that are typically set up within the ROLAP context (lattice). We have enlarged our implementations processes to take into account the construction of the lattice in both detained models.As it is difficult to choose a single NoSQL implementation that supports effectively all the applicable treatments, we proposed two translation processes. While the first one concerns intra-models processes, i.e., pass rules from an implementation to another of the same NoSQL logic model, the second process defines the transformation rules of a logic model implementation to another implementation on another logic model
22
Agena, Barbara Tieko. "Acesso a dados baseado em ontologias com NoSQL." Universidade de São Paulo, 2017. http://www.teses.usp.br/teses/disponiveis/45/45134/tde-23012018-132444/.
Full textAbstract:
O acesso a dados baseado em ontologia (OBDA, de Ontology-Based Data Access) propõe facilitar ao usuário acesso a dados sem o conhecimento específico de como eles estão armazenados em suas fontes. Para isso, faz-se uso de uma ontologia como camada conceitual de alto nível, explorando sua capacidade de descrever o domínio e lidar com a incompletude dos dados. Atualmente, os sistemas NoSQL (Not Only SQL) estão se tornando populares, oferecendo recursos que os sistemas de bancos de dados relacionais não suportam. Desta forma, surgiu a necessidade dos sistemas OBDA se moldarem a estes novos tipos de bancos de dados. O objetivo desta pesquisa é propor uma arquitetura nova para sistemas OBDA possibilitando o acesso a dados em bancos de dados relacionais e bancos de dados NoSQL. Para tal, foi proposta a utilização de um mapeamento mais simples responsável pela comunicação entre ontologia e bancos de dados. Foram construídos dois protótipos de sistemas OBDA para sistemas NoSQL e sistemas de bancos de dados relacional para uma validação empírica da arquitetura proposta neste trabalho.Ontology-based data access (OBDA) proposes to facilitate user access to data without specific knowledge of how they are stored in their sources. For this, an ontology is used as a high level conceptual layer, exploring its capacity to describe the domain and deal with the incompleteness of the data. Currently, NoSQL (Not Only SQL) systems are becoming popular, offering features that relational database systems do not support. In this way, the need arose for shaping OBDA systems to deal with these new types of databases. The objective of this research is to propose a new architecture for OBDA systems allowing access to data in relational databases and NoSQL databases. For this, we propose the use of a simpler mapping responsible for the communication between ontology and databases. Two OBDA system prototypes were constructed: one for NoSQL systems and one for relational database systems for an empirical validation.
23
Ait, Ouassarah Azhar. "ADI : A NoSQL system for bi-temporal databases." Thesis, Lyon, 2016. http://www.theses.fr/2016LYSEI046/document.
Full textAbstract:
La complexité et la dynamique de l'environnement dans lequel évolue chaque entreprise requiert de la part de ses managers la capacité de prendre des décisions pertinentes dans un laps de temps très court afin de s'accroître. Pour cela, l'analyse des données générées par l'activité de l'entreprise peut être une précieuse source d'information. L'Intelligence Opérationnelle (IO) est une classe de systèmes d'aide à la décision permettant aux managers d'avoir une très bonne compréhension de la situation de l'entreprise, à travers l'analyse de l'activité passée et présente. Dans ce contexte, les notions de temps et de traçabilité sont primordiales dans la compréhension de l'évolution de l'activité de l'entreprise à travers le temps. Dans cette thèse, nous présentons Axway Decision Insight (ADI), une solution d'IO développée par Axway. Son composant clé est un SGBD orienté-colonnes et bi-temporel développé en interne par l'entreprise pour répondre aux besoins spécifiques de l'IO. Ses capacités bi-temporelles lui permettent de gérer nativement aussi bien l'évolution des données dans la réalité modélisée (temps de validité) que l'évolution des données dans la base de données (temps de transaction). Nous commencerons par présenter la solution ADI en nous focalisant sur deux éléments importants: 1) l'interface graphique qui permet la conception et l'utilisation d'ADI sans écrire la moindre ligne de code. 2) L'approche adoptée pour modéliser les données bi-temporelles. Ensuite, nous présenterons un benchmark bi-temporel destiné ADI.Après cela, nous présenterons deux optimisations pour ADI. La première permet de pré-calculer et matérialiser les opérations d'agrégation, ce qui permet de réduire le temps nécessaire à la mise à jour de interface graphique d'ADI. La deuxième optimisation ordonne l'exécution des opérateurs de jointure des plans de requêtes en utilisant un modèle coût basé sur des statistiques sur des données bi-temporelles. Pour ces optimisations, nous avons effectué des expérimentations en utilisant notre benchmark, et qui ont démontré leurs intérêtsNowadays, every company is operating in very dynamic and complex environments which require from its managers to have a deep understanding of its business in order to take rapid and relevant decisions, and thus maintain or improve their company's activities. They can rely on analyzing the data deluge generated by the company's activities. A new class of systems has emerged in the decision support system galaxy called "Operational Intelligence" (OI) to meet this challenge. The objective is to enable operational managers to understand what happened in the past as well as what is currently happening in their business. In this context, the notions of time and traceability turns out to play a crucial role to understand what happened in the company and what is currently happening in the company. In this thesis, we present "Axway Decision Insight" (ADI), an "Operational Intelligence" solution developed by Axway. ADI's key component is a proprietary bi-temporal and column-oriented DBMS that has specially been designed to meet OI requirements. Its bi-temporal capabilities enable to catch both data evolution in the modeled reality (valid time) and in the database (transaction time).We first introduce ADI by focusing on two topics: 1) the GUI that makes the platform "code-free". 2) The adopted bi-temporal modeling approaches. Then we propose a performance benchmark that meets ADI's requirements. Next, we present two bi-temporal query optimizations for ADI. The first one consists in redefining a complex bi-temporal query into: 1) a set of continuous queries in charge of computing aggregation operations as data is collected. 2) A bi-temporal query that accesses the continuous queries' results and feeds the GUI. The second one is a cost-based optimization that uses statistics on bi-temporal data to determine an "optimal" query plan. For these two optimizations, we conducted some experiments, using our benchmark, which show their interests
24
Arvidsson, Andreas, and Jörgen Bygdemark. "JÄMFÖRELSE MELLAN ORACLE RDBMS, ORACLE NOSQL OCH MONGODB." Thesis, Umeå universitet, Institutionen för datavetenskap, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-163179.
Full textAbstract:
Databases are present everywhere in our modern society and the amount of data that have to be stored is constantly increasing, which means that it’s now more important than ever to be able to handle massive data sets effectively. NoSQL databases2 were developed to solve this problem by efficiently storing large amounts of data and enable fast access to that data. Since NoSQL databases only became popular within the last ten years, they haven’t been as well researched as relational databases. An in-depth evaluation is carried out on six distinct features, where one part is comparative performance tests. The other features are: scalability, consistency, availability, durability and reliability. MongoDB and Oracle NoSQL are the NoSQL databases used and together with Oracle RDBMS as relational database make up the basis for a comparative study of the above mentioned features.The results showed that there are big differences between how data is handled in NoSQL compared to relational databases that will affect the choice of database, e.g. that NoSQL tends to prioritize that clients can reach the database over non-contradictory data and lowering the demands on transaction management to increase performance and storage capacity. Furthermore, the performance tests showed that both NoSQL databases performed beer than the relational database regardless of the data set size. MongoDB was clearly the fastest on reading operations, while Oracle NoSQL performed write operations the fastest most of the time. Both NoSQL databases are impacted less by a growing data set than the relational database for both read and write operations.
25
Hedman, Jennifer, and Mikael Holmberg. "Jämförelse av NoSQL-databas och SQL-baserad relationsdatabas : En förklarande studie för när NoSQL kan vara att föredra framför en relationsdatabas." Thesis, Högskolan Dalarna, Informatik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:du-29817.
Full textAbstract:
With the explosive development of the mobile world, web applications and Big Data, new requirements for storage capacity and speed of database systems have arisen. The traditional relational database that has long dominated the marked has received competition because of its lack in speed and scalability. NoSQL is a collective name for databases that are not based on the traditional relational model. NoSQL databases are designed to easily expand their storage capacity while delivering high performance. NoSQL databases have been around for decades but the need for them is relatively new. Our partner expressed a desire to know what differences exist between NoSQL and the traditional relational database. To clarify these differences, we have answered the following questions in this work: When can a NoSQL database be preferred to a relational database? What are the differences in database performance? In order to answer these questions, a literature study has been conducted together with experiments where we test which performance differences exist between the selected databases. Performance tests have been performed with the benchmarking tool Yahoo Cloud Serving Benchmark, to verify or falsify the enhanced performance of the NoSQL databases. The hypotheses were falsified in both NoSQL databases. The results showed that the relational database performed better than the cloud based NoSQL databases, but also that the relational database performance deteriorates when the load increased. The results of the experiments are combined with the literature study and together answer our questions. The conclusion is that no database performs better than another one, it is the requirements of the data to be stored. From these requirements, analyses can be made to draw conclusions about what kind of database is preferable.
26
Landbris, Johan. "A Non-functional evaluation of NoSQL Database Management Systems." Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-46804.
Full textAbstract:
NoSQL is basically a family name for all Database Management Systems (DBMS) that is not Relational DBMS. The fast growth of all social networks has led to a huge amount of unstructured data that NoSQL DBMS is supposed to handle better than Relational DBMS. Most comparisons performed are between Relational DBMS and NoSQL DBMS. In this paper, the comparison is about non-functional properties for different types of NoSQL DBMS instead. Three of the most common NoSQL types are Document Stores, Key-Value Stores and Column Stores. The most used DBMS of those types are MongoDB, Redis and Apache Cassandra. After working with the databases and performing YCSB Benchmarking the conclusion is that if the database should handle an enormous amount of data, Cassandra is most probably best choice. If speed is the most important property and if all data fits within the memory; Redis is probably the most well suited database. If the database needs to be flexible and versatile, MongoDB is probably the best choice.
27
Pulgatti, Leandro Duarte. "Data migration between different data models of NOSQL databases." reponame:Repositório Institucional da UFPR, 2017. http://hdl.handle.net/1884/49087.
Full textAbstract:
Orientador : Marcos Didonet Del FabroDissertação (mestrado) - Universidade Federal do Paraná, Setor de Ciências Exatas, Programa de Pós-Graduação em Informática. Defesa: Curitiba, 17/02/2017
Inclui referências : f. 76-79
Resumo: Desde sua origem, as bases de dados Nosql têm alcançado um uso generalizado. Devido à falta de padrões de desenvolvimento nesta nova tecnologia emergem grandes desafios. Existem modelos de dados , linguagens de acesso e frameworks heterogêneos, o que torna a migração de dados ainda mais complexa. A maior parte das soluções disponíveis hoje se concentra em fornecer uma representação abstrata e genérica para todos os modelos de dados. Essas soluções se concentram em adaptadores para acessar homogeneamente os dados, mas não para implementar especificamente transformações entre eles. Essas abordagens muitas vezes precisam de um framework para acessar os dados, o que pode impedir de usá-los em alguns cenários. Entre estes desafios, a migração de dados entre as várias soluções revelou-se particularmente difícil. Esta dissertação propõe a criação de um metamodelo e uma série de regras capazes de auxiliar na tarefa de migração de dados. Os dados podem ser convertidos para vários formatos desejados através de um estado intermediário. Para validar a solução foram realizados vários testes com diversos sistemas e utilizando dados reais disponíveis. Palavras Chave: NoSql Databases. Metamodelo. Migração de Dados.
Abstract: Since its origin the NoSql Database have achieved widespread use. Due to the lack of standards for development in this new technology great challenges emerges. Among these challenges, the data migration between the various solutions has proved particularly difficult. There are heterogeneous datamodels, access languages and frameworks available, which makes data migration even more complex. Most part of the solutions available today focus on providing an abstract and generic representation for all data models. These solutions focus in design adapters to homogeneously access the data, but not to specifically implement transformations between them. These approaches often need a framework to access the data, which may prevent from using them in some scenarios. This dissertation proposes the creation of a metamodel and a series of rules capable of assisting in the data migration task. The data can be converted to various desired formats through an intermediate state. To validate the solution several tests were performed with different systems and using real data available. Key-words: NoSql Databases. Metamodel. Data Migration.
28
Skarman, Mattias, and Jacob Östelid. "Relationsdatabas eller NoSQL? : En jämförelse mellan MSSQL och MongoDB." Thesis, Karlstads universitet, Institutionen för matematik och datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-43255.
Full textAbstract:
Midroc automation uses databases for many different projects, both internally and in customer projects. At present, they are mainly using relational databases. There is an interest in researching different types of databases not based on the relational model. Midroc automation wants to know if there are any advantages of using a non-relational database. This project will compare two different databases. To make this comparison Microsoft SQL and MongoDB has been selected. MongoDB is a document type database which belongs to the category of non-relational databases commonly referred to as NoSQL. An application with a GUI and CRUD operations for each database has been implemented. This implementation was done using C# .NET in Visual Studio. The result of the comparison shows that MongoDB is more flexible while developing a database. It is also easier to make changes to an existing database while working with MongoDB. It is however harder to find information and support online when working with MongoDB.Midroc Automation använder databaser till många olika projekt, både internt och mot sina kunder. Idag använder de främst databaser baserade på relationsmodellen. De är intresserade av att utreda om det finns några andra typer av databaser som inte är baserade på relationsmodellen och också om dessa skulle innebära några fördelar. I detta projekt kommer man att jämföra två olika databaser. För att göra denna jämförelse har man valt att undersöka Microsoft SQL och MongoDB. MongoDB är en databas av dokumenttyp som tillhör de moderna icke-relationella databaserna kallade NoSQL. För att göra jämförelsen har en applikation med tillhörande GUI och CRUD-operationer implementerats för varje databas. Implementationen har gjorts med hjälp av C# .NET i utvecklingsverktyget Visual Studio. Resultatet av jämförelsen visar att MongoDB är mer flexibelt vid utveckling av databasen. Det är också enklare att göra ändringar till en befintlig databas med MongoDB. Det är dock svårare att hitta information och hjälp online då man utvecklar en Mongo databas.
29
Sortelius, Erik, and Gabriellle Önnestam. "Påverkan av query-komplexitet på söktiden hos NoSQL-databaser." Thesis, Högskolan i Skövde, Institutionen för informationsteknologi, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-15970.
Full textAbstract:
Arbetet jämför fyra olika NoSQL-databaser med fokus på tidseffektivitet. De fyra databaserna är MongoDB, RavenDB, ArangoDB och Couchbase. Studien består av en benchmark för att mäta tidseffektiviteten av de fyra databaserna och en litteraturstudie av hur tidseffektiviteten påverkas av optimeringslösningar. Tillsammans bidrar dessa metoder till en slutsats från båda perspektiven då de kompletterar varandra och ger en grund för resultatets betydelse. Arbetets grund ligger i ett tidigare examensarbete som går ut på att jämföra en SQL-databas mot en NoSQL-databas med en benchmark. Resultatet av studien visar att för de flesta databaser så ökar söktiden för en query i korrelation med ökningen av query-komplexiteten, och att tidseffektiviteten mellan de olika databaserna varierar vid sökningar med hög komplexitet. Framtida arbeten som kan baseras på denna studie är att göra en liknande benchmark på ett dataset som är större eller att en annan typ av databas används.
30
Блинков, Ю. А., and И. А. Панкратов. "Применение технологии NoSQL для хранения и обработки библиографической информации." Thesis, Сумский государственный университет, 2017. http://essuir.sumdu.edu.ua/handle/123456789/64366.
Full textAbstract:
В настоящей работе построена концепция информационной системы для документо-ориентированного хранения и обработки информации публикациях различного типа с помощью технологии NoSQL [1].
При использовании NoSQL не требуется создавать несколько связанных друг с другом таблиц. Применение технологии NoSQL позволяет
отказаться от жёсткой структуры базы данных. Легко можно будет
при необходимости добавить новый, пока ещё отсутствующий тип
публикации, не затрагивая ранее внесённые записи.
31
Блинков, Ю. А., and И. А. Панкратов. "Применение технологии NoSQL для хранения и обработки библиографической информации." Thesis, Сумский государственный университет, 2017. http://essuir.sumdu.edu.ua/handle/123456789/65690.
Full text
32
Vizina, Petr. "NoSQL databáze pro data senzorů s podporou časových řad." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2017. http://www.nusl.cz/ntk/nusl-363797.
Full textAbstract:
This thesis deals with NoSQL databases, which can be used for effective storage of sensors data with character of time series. The aim is to design and implement own solution for database designed to store time series data, with usage of NoSQL.
33
Schildgen, Johannes [Verfasser], and Stefan [Akademischer Betreuer] Deßloch. "Datentransformationen in NoSQL-Datenbanken / Johannes Schildgen ; Betreuer: Stefan Deßloch." Kaiserslautern : Technische Universität Kaiserslautern, 2017. http://d-nb.info/1141678063/34.
Full text
34
Salvatori, Riccardo. "Analisi delle strategie di modellazione dei dati su database NoSQL." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2021. http://amslaurea.unibo.it/23172/.
Full textAbstract:
Negli ultimi anni, i sistemi NoSQL si sono rivelati una soluzione efficace alle stringenti esigenze del web e dei sistemi di big data, grazie alle caratteristiche di scalabilità e flessibilità che superano le limitazioni imposte dai classici RDBMS.
La crescente popolarità è accompagnata però dalla mancanza di metodologie generali ed efficaci per la modellazione di dati, che permettano di sfruttare al meglio le possibilità offerte dal mondo non relazionale. Infatti, a differenza dei database relazionali, per cui esiste una vasta letteratura sul tema, molte tecniche di progettazione in ambito NoSQL sono proposte sotto forma di linee guida e best practice, per lo più dettate dall'esperienza, che spesso vanno adattate al carico di lavoro e alla specifica implementazione.
In questa tesi sono state analizzate le diverse strategie di modellazione in ambito NoSQL, evidenziando il ruolo fondamentale che hanno nel determinare le prestazioni finali del database.
L'analisi è stata effettuata utilizzando il benchmark TPC-C, su due popolari database NoSQL: MongoDB e Cassandra.
Inoltre, è stato progettato un indicatore che permette di avere un'approssimazione a priori delle prestazioni di una de-normalizzazione. L'indicatore si è dimostrato efficace per i database MongoDB e Cassandra nell'individuare le modellazioni dei dati ottimali per il carico di lavoro previsto.
35
Öhrn, Henrik. "NoSQL-databaser och utnyttjandet av en grafdatabas i ett transportnätverk." Thesis, University of Gävle, Department of Industrial Development, IT and Land Management, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hig:diva-7016.
Full textAbstract:
Den allmänna kunskapen om NoSQL-databaser är begränsad. Den här uppsatsen koncentrerar sig på att sammanställa egenskaper och information om för- och nackdelar som rör dessa databastyper samt relationsdatabaser i en undersökning. Uppsatsen belyser även användningsområden för de olika databastyperna och i en fallstudie testas en grafdatabas förmåga att representera och utföra sökningar av data från ett järnvägsspårnät. Problemområdena undersöktes genom att samla information om olika typer av databaser från artiklar och böcker. Tillämpningsfallet i fallstudien implementerades och testades i en grafdatabas. Resultatet av undersökningen visade att NoSQL-databaser är ett intressant alternativ i vissa fall men att mycket hänsyn måste tas innan man väljer vilken typ av databas som är mest lämpad i den specifika tillämpningen. Resultatet av fallstudien visar att en grafdatabas är särdeles lämpad för att representera och utföra operationer på ett transportnätverk. Detta till stora delar beroende på dess förmåga att representera kopplingarna i ett transportnätverk och i form av de operationerna som finns i grafteorin och som grafmodellen erbjuder.Nyckelord: nosql, relationsdatabas, nyckel/värde-databas, kolumndatabas, objektdatabas, dokumentdatabas, grafdatabas, järnvägsnätverk, transportnätverk
36
Rothsberg, Johan. "Evaluation of using NoSQL databases in an event sourcing system." Thesis, Linköpings universitet, Databas och informationsteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-123193.
Full textAbstract:
An event store is a database for storing events in an event sourcing system. Instead of storing the current state, a very common way to persist data, an event sourcing system captures all changes to an application state as a sequence of events. Usually the event store is a relational database. Relational databases have several drawbacks and therefore NoSQL databases have been developed. The purpose of this thesis is to explore the possibility of using a NoSQL database in an event sourcing system. We will see how data is stored in an event store and then evaluate di↵erent solutions to find a suitable database. The graph database Neo4j was selected to be further investigated and a Neo4j event store has been implemented. At last the implemented solution is evaluated against the existing event store that uses a relational database. The conclusion of this thesis is that event store data could easily be modeled in Neo4j but some queries became complex to implement. The performance tests showed us that the implemented event store had poorer performance than the existing one using a relational database.
37
Dehdouh, Khaled. "Entrepôts de données NoSQL orientés colonnes dans un environnement cloud." Thesis, Lyon 2, 2015. http://www.theses.fr/2015LYO22018.
Full textAbstract:
Le travail présenté dans cette thèse vise à proposer des approches pour construire et développer des entrepôts de données selon le modèle NoSQL orienté colonnes. L'intérêt porté aux modèles NoSQL est motivé d'une part, par l'avènement des données massives et d'autre part, par l'incapacité du modèle relationnel, habituellement utilisés pour implémenter les entrepôts de données, à permettre le passage à très grande échelle. En effet, les différentes modèles NoSQL sont devenus des standards dans le stockage et la gestion des données massives. Ils ont été conçus à l'origine pour construire des bases de données dont le modèle de stockage est le modèle « clé/valeur ». D'autres modèles sont alors apparus pour tenir compte de la variabilité des données : modèles orienté colonne, orienté document et orienté graphe. Pour développer des entrepôts de données massives, notre choix s'est porté sur le modèle NoSQL orienté colonnes car il apparaît comme étant le plus approprié aux traitements des requêtes décisionnelles qui sont définies en fonction d'un ensemble de colonnes (mesures et dimensions) issues de l'entrepôt. Cependant, le modèle NoSQL en colonnes ne propose pas d'opérateurs de type analyse en ligne (OLAP) afin d'exploiter les entrepôts de données.Nous présentons dans cette thèse des solutions innovantes sur la modélisation logique et physique des entrepôts de données NoSQL en colonnes. Nous avons proposé une approche de construction des cubes de données qui prend compte des spécificités de l'environnement du stockage orienté colonnes. Par ailleurs, afin d'exploiter les entrepôts de données en colonnes, nous avons défini des opérateurs d'agrégation permettant de créer des cubes OLAP. Nous avons proposé l'opérateur C-CUBE (Columnar-Cube) permettant de construire des cubes OLAP stockés en colonnes dans un environnement relationnel en utilisant la jointure invisible. MC-CUBE (MapReduce Columnar-Cube) pour construire des cubes OLAP stockés en colonnes dans un environnement distribué exploitant la jointure invisible et le paradigme MapReduce pour paralléliser les traitements. Et enfin, nous avons développé l'opérateur CN-CUBE (Columnar-NoSQL Cube) qui tient compte des faits et des dimensions qui sont groupés dans une même table lors de la génération de cubes à partir d'un entrepôt dénormalisé selon un certain modèle logique. Nous avons réalisé une étude de performance des modèles de données dimensionnels NoSQL et de nos opérateurs OLAP. Nous avons donc proposé un index de jointure en étoile adapté aux entrepôts de données NoSQL orientés colonnes, baptisé C-SJI (Columnar-Star Join Index). Pour évaluer nos propositions, nous avons défini un modèle de coût pour mesurer l'impact de l'apport de cet index. D'autre part, nous avons proposé un modèle logique baptisé FLM (Flat Logical Model) pour implémenter des entrepôts de données NoSQL orientés colonnes et de permettre une meilleure prise en charge par les SGBD NoSQL de cette famille.Pour valider nos différentes contributions, nous avons développé une plate-forme logicielle CG-CDW (Cube Generation for Columnar Data Warehouses) qui permet de générer des cubes OLAP à partir d'entrepôts de données en colonnes. Pour terminer et afin d'évaluer nos contributions, nous avons tout d'abord développé un banc d'essai décisionnel NoSQL en colonnes (CNSSB : Columnar NoSQL Star Schema Benchmark) basé sur le banc d'essai SSB (Star Schema Benchmark), puis, nous avons procédé à plusieurs tests qui ont permis de montrer l'efficacité des différents opérateurs d'agrégation que nous avons proposéThe work presented in this thesis aims at proposing approaches to build data warehouses by using the columnar NoSQL model. The use of NoSQL models is motivated by the advent of big data and the inability of the relational model, usually used to implement data warehousing, to allow data scalability. Indeed, the NoSQL models are suitable for storing and managing massive data. They are designed to build databases whose storage model is the "key/value". Other models, then, appeared to account for the variability of the data: column oriented, document oriented and graph oriented. We have used the column NoSQL oriented model for building massive data warehouses because it is more suitable for decisional queries that are defined by a set of columns (measures and dimensions) from warehouse. However, the NoSQL model columns do not offer online analysis operators (OLAP) for exploiting the data warehouse.We present in this thesis new solutions for logical and physical modeling of columnar NoSQL data warehouses. We have proposed a new approach that allows building data cubes by taking the characteristics of the columnar environment into account. Thus, we have defined new cube operators which allow building columnar cubes. C-CUBE (Columnar-CUBE) for columnar relational data warehouses. MC-CUBE (MapReduce Columnar-CUBE) for columnar NoSQL data warehouses when measures and dimensions are stored in different tables. Finally, CN-CUBE (Columnar NoSQL-CUBE) when measures and dimensions are gathered in the same table according a new logical model that we proposed. We have studied the NoSQL dimensional data model performance and our OLAP operators, and we have proposed a new star join index C-SJI (Columnar-Star join index) suitable for columnar NoSQL data warehouses which store measures and dimensions separately. To evaluate our contribution, we have defined a cost model to measure the impact of the use of this index. Furthermore, we have proposed a logic model called FLM (Flat Logical Model) to represent a data cube NoSQL oriented columns and enable a better management by columnar NoSQL DBMS.To validate our contributions, we have developed a software framework CG-CDW (Cube Generation for Data Warehouses Columnar) to generate OLAP cubes from columnar data warehouses. Also, we have developed a columnar NoSQL decisional benchmark CNSSB (Columnar NoSQL Star Schema Benchmark) based on the SSB and finally, we conducted several tests that have shown the effectiveness of different aggregation operators that we proposed
38
Simões, David João Apolinário. "Endowing NoSQL DBMS with SQL features through call level interfaces." Master's thesis, Universidade de Aveiro, 2015. http://hdl.handle.net/10773/18592.
Full textAbstract:
Mestrado em Engenharia de Computadores e TelemáticaOs arquitetos de software usam ferramentas, tais como Call Level Interfaces (CLI), para guardar, atualizar e retirar dados de Sistemas de Gestão de Bases de Dados (SGBD). Estas ferramentas estão desenhadas para efetuarem a junção entre os paradigmas de Base de Dados Relacional e da Programação Orientada a Objetos e fornecem funcionalidades padrão para interagir com SGBD. No entanto, a emergência do paradigma NoSQL, e particularmente de novos fornecedores de SGBD NoSQL, leva a situações onde algumas das funcionalidades padrão fornecidas por CLI não são suportadas. Isto deve-se normalmente à distância entre o modelo SQL e NoSQL, ou devido a restrições de design. Assim, quando um arquiteto de sistema precisa de evoluir, nomeadamente de um SGBD relacional para um SGBD NoSQL, tem de ultrapassar as dificuldades que emergem por existirem funcionalidades não suportadas pelo SGBD NoSQL. Não só isso, mas as CLI costumam ignorar políticas de controlo de acesso estabelecidas e, portanto, programadores de aplicações têm de dominar as ditas políticas de maneira a desenvolverem software em concordância com elas. Escolher o SGBD NoSQL errado pode levar a problemas de grandes dimensões quando as aplicações pedem funcionalidades não suportadas ou a que não têm acesso. Esta tese foca-se em implementar funcionalidades que não são comummente suportadas por SGBD NoSQL, tais como Stored Procedures, Transações, Save Points e interações com estruturas de memória local, através de uma framework baseada numa CLI padrão. O modelo de implementação de funcionalidades é definido por módulos da nossa framework, e permite a criação de sistemas distribuídos e tolerantes a falhas, que simulam as funcionalidades anteriormente referidas e abstraem as funcionalidades da base de dados subjacente de clientes. Também temos como objetivo integrar a nossa framework com trabalho anterior, a S-DRACA, uma arquitetura dinâmica e segura de controlo de acesso para aplicações relacionais, onde as permissões são definidas como sequências de expressões create, read, update e delete. Com esta integração, conseguimos fornecer Role-Based Access Control e outras funcionalidades de segurança a qualquer tipo de SGBD. Desenvolvemos várias formas de utilizar cada componente (localmente ou distribuído) e a framework está construída de forma modular, o que permite aos vários componentes serem utilizados individualmente ou em grupo, assim como permite o acrescento de funcionalidades ou SGBD adicionais por administradores de sistema que queiram adaptar a framework às suas necessidades particulares.
To store, update and retrieve data from database management systems (DBMS), software architects use tools, like call level interfaces (CLI), which provide standard functionality to interact with DBMS. These tools are designed to bring together the relational database and object-oriented programming paradigms, but the emergence of the NoSQL paradigm, and particularly new NoSQL DBMS providers, leads to situations where some of the standard functionality provided by CLI are not supported, very often due to their distance from the relational model or due to design constraints. As such, when a system architect needs to evolve, namely from a relational DBMS to a NoSQL DBMS, he must overcome the difficulties conveyed by the features not provided by the NoSQL DBMS. Not only that, but CLI usually forsake applied access control policies. As such, application developers must master the established policies as a means to develop software that is conformant with them. Choosing the wrong NoSQL DBMS risks major issues with applications requesting non-supported features and with unauthorized accesses. This thesis focuses on deploying features that are not so commonly supported by NoSQL DBMS, such as Stored Procedures, Transactions, Save Points and interactions with local memory structures, through a framework based in a standard CLI. The feature implementation model is defined by modules of our framework, and allows for distributed and fault-tolerant systems to be deployed, which simulate the previously mentioned features and abstract the underlying database features from clients. It is also our goal to integrate our framework with previous work, S-DRACA, a dynamic secure access control architecture for relational applications, where permissions are defined as a sequence of create, read, update and delete expressions. With the integration, we can provide dynamic Role-Based Access Control and other security features to any kind of DBMS. We developed several ways of using each component (locally or distributed) and the framework is built in a modular fashion, which allows several components to be used individually or together, as well as extra features or DBMS to be added by system administrators that wish to adapt the framework to their particular needs.
39
Vrbík, Tomáš. "Srovnání distribuovaných "NoSQL" databází s důrazem na výkon a škálovatelnost." Master's thesis, Vysoká škola ekonomická v Praze, 2011. http://www.nusl.cz/ntk/nusl-124673.
Full textAbstract:
This paper focuses on NoSQL database systems. These systems currently serve rather as supplement than replacement of relational database systems. The aim of this paper is to compare 4 selected NoSQL database systems (MongoDB, Apache Cassandra, Apache HBase and Redis) with a main focus on performance and scalability. Performance comparison is done using simulated workload in a 4 nodes cluster environment. One relational SQL database is also benchmarked to provide comparison between classic and modern way of maintaining structured data. As the result of comparison I found out that none of these database systems can be labeled as "the best" as each of the compared systems is suitable for different production deployment.
40
Villabona, Antonio, and Fredrik Dietrichson. "Effektivisera generering av parameterfiler för betalterminaler." Thesis, KTH, Data- och elektroteknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-153794.
Full textAbstract:
Denna rapport återger arbetsprocessen kring att utvärdera datalagringsstruktur och förbättra prestanda för generering av parameterfiler för kortterminaler. Arbetet utfördes på plats hos Esplanad AB, ett företag som bland annat arbetar med säkerhetslösningar och distribution av inställningar för betalstationer. Uppgiften bestod av att utvärdera möjligheter till att förbättra databasen som sparar alla inställningarna för betalsystemen, samt att förbättra kodstruktur och prestanda för programmet som genererar filerna. Rapporten beskriver testning av prestanda, både på Esplanads gamla program för att generera parameterfiler och det nya som konstruerades. En lösning presenteras som inkluderar förbättring av filgenereringens prestanda och en ny struktur på databasen för ökad skalbarhet. Tester visar att det nya systemet klarar av att skapa parameterfiler på TLV-format ungefär 16 gånger snabbare. Den föreslagna lösningen implementerar parallella processer och replikering av databasen.This thesis describes the process of analyzing and evaluating the structure of data storage and improving the performance for generating parameter files destined for card terminals. The work was done in house at Esplanad AB, a company dealing with security solutions and distribution of settings for payment stations. The first task was to evaluate the possibilities for improving the database storing the settings for each card reader. The second task was to improve the structure of the code and also improve the file generating systems performance. The thesis describes testing performance, both for Esplanad’s old system for generating parameter files, and the new one constructed. The solution presented includes improved performance of the file generating process and a new structure for the database that increases scalability. Tests show that the new system is capable of generating parameter files with TLV-format, about 16 times faster. The proposed solution implements parallel processes and database replication.
41
Muhammad, Yousaf. "Evaluation and Implementation of Distributed NoSQL Database for MMO Gaming Environment." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-159864.
Full text
42
Miiro, Fabian, and Mikael Nääs. "SQL and NoSQL databases : A CASE STUDY IN THE AZURE CLOUD." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-186398.
Full textAbstract:
I denna rapport jämförs Azure SQL Database med NoSQL lösningen DocumentDB, under förutsättningarna givna av ett turbaserat flerspelarspel. NoSQL är en relativt ny typ av databas, som till skillnad från dess relationsbaserade kusin har nya lovord angående fantastisk prestanda och oändlig skalbarhet. Det sägs att det är skapt för dagens problem utan gårdagens begränsningar. Warmkitten vill ta reda på om löftena kring NoSQL håller i deras scenario. Eller om den nuvarande SQL lösningen är en bättre match för deras spel med tanke på skalning, snabbhet och anvädningen utav .NET. Jämförelsen gjordes genom att först skapa ett testramverk för spelets flerspelar funktioner. Sedan optimerades både den relations- och den icke-relationsbaserade lösningen, baserat på rekommendationer och experters utlåtande. Testerna kördes sedan under förhållanden som skulle återspegla verkligheten. Rapporten visar att denna nya typ utav databaser helt klart är mogna nog att i vissa scenarion användas istället för de relationsbaserade databaserna, givet att tillräckligt mycket tid ges åt att förstå skillnaderna mellan databastyperna och vad det innebär. Extra betänketid bör läggas på hur NoSQL skalar samt vilka skillnader som det innebär när relations-begränsningarna försvinner. Prestandamässigt så är DocumentDB snabbare under normal användning när det finns lugnare stunder, SQL är bättre för applikationer som behöver köra under långa stunder med hög användning utav databasen. Rapportens slutsats blir en rekommendation till Warmkitten att fortsätta med den redan utvecklade SQL lösningen. Detta då prestandaförbättringarna från NoSQL inte väger upp för den ökade transaktionskomplexiteten, då spelet använder transaktioner i hög utsträckning.This paper was created to compare Azure SQL Database to the Azure NoSQL solution DocumentDB. This case study is done in the scope of a turn-based multiplayer game created by Warmkitten. NoSQL is a new type of databases, instead of the relational kind we are used to, this new type gives promises of increased performance and unlimited scalability. It is marketed that it is created for the problems of today and not bound by yesterday’s limitations. Warmkitten would like to gain insight if the promises from NoSQL holds for the game they are developing or if the current SQL solution fit their needs. They are most interested in the areas of scaling, performance and .NET interoperability. The comparison was carried out by creating a test suite testing the game functionalities. Then both the SQL and NoSQL solution was optimized based on best practices and expert guidelines. The tests were then run under circumstances mimicking real-world scenarios. The paper shows that NoSQL is a valid replacement to SQL, if enough time and thought is put into the implementation. Given that NoSQL is a good fit for the problem at hand. Our paper shows that performance wise NoSQL is faster under normal load when there are times with less load, SQL is better for applications that will have continuously heavy load. The final verdict of this paper is a recommendation for Warmkitten to continue using SQL for their game. This is because the recorded performance improvements does not outweighs the transactional problems seen in this case study created by the transactional nature of the game.
43
Aslan, David. "Lagring av Motion Capture Data i NoSQL-databser : Undersökning av CouchDB." Thesis, Högskolan i Skövde, Institutionen för informationsteknologi, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-11095.
Full textAbstract:
Motion capture data behöver lagra på ett eller annat sätt lagra detta med databas skulle innebära väldigt många fördelar. Den används på många olika sätt och i olika branscher därmed skulle innebära en stor förändring. Det finns två olika kategorier av databaser SQL databaser och NoSQL databaser, dem databaser som kommer testas är relationsbaserade MySQL och dokumentbaserade CouchDB med en prototyp som utvecklas för att utföra dessa tester. Testerna påvisar att CouchDB är bättre databaslösningen vid lagringen av motion capture data. Men ytterligare arbete skulle kunna utföra flera tester som påvisar att läsning av motion capture data från databaserna kan ske i realtid. Mätningar från experimentet bevisar att CouchDB är den snabbare på att lagra Motion Capture data. I framtida arbete skulle arbetet kunna införas i filmbranschen och bli effektivt genom att använda mindre hårddiskutrymme och minska kostnaderna.
44
Klingsbo, Lukas. "NoSQL: Moving from MapReduce Batch Jobs to Event-Driven Data Collection." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-260394.
Full textAbstract:
Collecting and analysing data of analytical value is important for many service providers today. Many make use of NoSQL databases for their larger software systems, what is less known is how to effectively analyse and gather business intelligence from the data in these systems. This paper suggests a method of separating the most valuable analytical data from the rest in real time and at the same time providing an effective traditional database for the analyser. In this paper we analyse our given data sets to decide whether big data tools are required and then traditional databases are compared to see how well they fit the context. A technique that makes use of an asynchronous log- ging system is used to insert the data from the main system to the dedicated analytical database. The tests show that our technique can efficiently be used with a tra- ditional database even on large data sets (>1000000 insertions/hour per database node) and still provide both historical data and aggregate func- tions for the analyser.
45
Klapač, Milan. "Výhody a nevýhody relačních a nerelačních (noSQL) databází pro analytické úlohy." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-193931.
Full textAbstract:
This work focuses on NoSQL databases, their use for analytical tasks and on comparison of NoSQL databases with relational and OLAP databases. The aim is to analyse the benefits of NoSQL databases and their use for analytical purposes. The first part presents the basic principles of Business Intelligence, Data Warehousing, and Big Data. The second part deals with the key features of relational and NoSQL databases. The last part of the thesis describes the properties of four basic types of NoSQL databases, analyses their advantages, disadvantages and areas of application. The end of this part in-cludes specific examples of the use of NoSQL databases, together with the reasons for the selection of those solutions.
46
Bernabe, Gianni. "Progettazione di un sistema di prenotazione on line con DBMS NoSQL." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2015. http://amslaurea.unibo.it/8265/.
Full text
47
Kharboutli, Zacky. "NoSQL Database Selection Focused on Performance Criteria for Web-driven Applications." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-88608.
Full textAbstract:
This paper delivers a comparative analysis of the performance of three of the NoSQL technologies in Web applications. These technologies are graph stores, key-value stores, and document stores. The study aims to assist developers and organizationsin picking the suitable NoSQL solution for their application. For this purpose, three identical e-book applications were developed. Each of these is connected to adatabase from the selected technologies to examine how they perform compared toeach other against various performance measures.
48
Pernini, Marina <1983>. "NoSql Databases: Analisi prestazionale e confronto col modello relazionale. Un’applicazione: MongoDB." Master's Degree Thesis, Università Ca' Foscari Venezia, 2015. http://hdl.handle.net/10579/6953.
Full textAbstract:
Con lo sviluppo di internet e la nascita dei sistemi cloud, si è venuta a creare l’esigenza di pubblicare online grandi quantità di dati e di contenuti. Di conseguenza è sorto il problema di permettere la gestione di grandi quantità di dati e allo stesso tempo garantire la funzionalità, l’affidabilità e la disponibilità dei servizi. A questo proposito i DBMS tradizionali hanno iniziato a portare a galla diversi limiti che andremo ad evidenziare in seguito. Molti limiti e problemi che si venivano a creare con i classici database relazionali furono risolti dalla nascita e dall’utilizzo di una nuova generazione di database: i database NO-SQL. NO-SQL sta per ”Not Only Sql” che indica un data-model diverso dal modello di dati con le tabelle al quale siamo sempre stati abituati. Tra le caratteristiche principali dei db NoSql c'è il fatto di non avere uno schema predefinito e di non utilizzare come linguaggio per le query l’SQL. Questa famiglia di database in realtà non è una vera e propria novità, in quanto questo termine fu coniato per la prima volta da Carlo Strozzi nel 1998 ed ha col tempo dimostrato di avere molti vantaggi rispetto ai DBMS anche se in alcuni campi specifici si preferisce ancora continuare ad utilizzare i db tradizionali per motivi che vedremo nel corso della tesi. Questa tesi ha come scopo quello di andare ad approfondire le caratteristiche dei database NOSql andando ad analizzarne la tassonomia e presentando 3 diversi tipi di db NoSQL con i 3 modelli di dati principali e di confrontare questi db con i classici database tradizionali, andando anche a creare lo stesso database prima con Mysql e poi con MongoDB, un database NoSql, andando a confrontare anche la prestazioni eseguendo delle query simili in entrambi i db.
49
Espling, Sebastian. "Faktorer att beakta vid val av databasmodell för en molntjänst : Ur ett mikroföretags perspektiv." Thesis, Högskolan i Skövde, Institutionen för kommunikation och information, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-6025.
Full textAbstract:
En databasmodell är en viktig del av en applikation och för företag som utvecklar molntjänster är det viktigt att databasmodellen kan hantera föränderlig och växande data. För mikroföretag som utvecklar molntjänster är val av databasmodell en stor investering. Ett medvetet val måste göras för att säkerställa att rätt databasmodell väljs utefter de förutsättningar, resurser och syfte man har med sin applikation. Då mikroföretag inte har samma resurser i form av kapital, kunskap och kompetens som större företag är detta val än mer viktigt. I denna uppsats har en kvalitativ undersökning genomförts i syfte att svara på två delfrågor och en huvudfråga. Delfrågorna skall ligga som grund till att svara på huvudfrågan i uppsatsen. Huvudfrågan ämnar identifiera vilka faktorer mikroföretag som utvecklar molntjänster bör beakta vid val avdatabasmodell för deras förutsättningar och syfte. Delfråga 1 ämnar identifiera vilka fördelar samt nackdelar som finns med databasmodellerna relationsdatabaser och NoSQL databaser. Delfråga 2 ämnar klargöra om det finns några faktorer som påverkar valet av databasmodell speciellt för en molntjänst. Resultatet av uppsatsen och den slutsats som arbetet resulterade i var att mikroföretag med hjälp av de för- och nackdelar som identifierats kan utvärdera vilken databasmodell som passar deras förutsättningar och syfte. Då syfte och förutsättningar skiljer sig mellan företag är detta en analys som de själva måste genomföra. Studien visade att finns vissa speciella aspekter att beakta för valet av databasmodell för en molntjänst men att det inte skiljer sig avsevärt från vilka aspekter som beaktas för val av databasmodeller i allmänhet.
50
Ankit, Bajpai. "SQL versus MongoDB from an application development point of view." Kansas State University, 2014. http://hdl.handle.net/2097/18816.
Full textAbstract:
Master of ScienceDepartment of Computing and Information Sciences
Doina Caragea
There are many formats in which digital information is stored in order to share and re-use it by different applications. The web can hardly be called old and already there is huge research going on to come up with better formats and strategies to share information. Ten years ago formats such as XML, CSV were the primary data interchange formats. And these formats were huge improvements over SGML (Standard Generalized Markup Language). It’s no secret that in last few years there has been a huge transformation in the world of data interchange. More lightweight, bandwidth-non-intensive JSON has taken over traditional formats such as XML and CSV. BigData is the next big thing in computer sciences and JSON has emerged as a key player in BigData database technologies. JSON is the preferred format for web-centric, “NoSQL” databases. These databases are intended to accommodate massive scalability and designed to store data which does not follow any columnar or relational model. Almost all modern programming languages support object oriented concepts, and most of the entity modeling is done in the form of objects. JSON stands for Java Script object notation and as the name suggests this object oriented nature helps modeling entities very naturally. And hence the exchange of data between the application logic and database is seamless. The aim of this report is to develop two similar applications, one with traditional SQL as the backend, and the other with a JSON supporting MongoDB. I am going to build real life functionalities and test the performance of various queries. I will also discuss other aspects of databases such as building a Full Text Index (FTI) and search optimization. Finally I will plot graphs to study the trend in execution time of insertion, deletion, joins and co- relational queries with and without indexes for SQL database, and compare them with the execution trend of MongoDB queries.