Figure 7 - uploaded by Marko Horvat
Content may be subject to copyright.
An example of a general query function [7].

An example of a general query function [7].

Source publication
Conference Paper
Full-text available
Modern large-scale information systems often use multiple database management systems, not all of which are necessarily relational. In recent years, NoSQL databases have gained acceptance in certain domains while relational databases remain de facto standard in many others. Many "legacy" information systems also use relational databases. Unlike rel...

Context in source publication

Context 1
... this approach database adapters are used. They get the query parameters from a function like the one in Figure 7. This function's name specifies the database operation it performs. ...

Similar publications

Article
Full-text available
The NoSQL databases that emerged this century were created to solve the limitations of relational database systems due to the different types of data that have appeared for information processing. In this paper, we present the results of a secondary study carried out to find and synthesize the research made up to now on modeling processes, characte...
Article
Full-text available
This work presents the design and implementation of two web-based search systems, Busc@NIMA and Quem@PUC. Both systems allow the identification of research and development projects, besides existing competencies in laboratories and departments involving professors and researchers at PUC-Rio University. Our applications are based on a list of search...
Article
Full-text available
Today, computing has become an obligation in the lives of individuals and institutions alike. This magical sector uses and develops very rich, important, and sensitive tools and solutions, which make everyone's life easier. Computers with their tools have become indispensable and they have transformed the world into a small town. These tools revolv...

Citations

... From a single DB's perspective, data distilling can be distinguished from the backend DB system and merged into upper-layer business logic implementations. When it comes to concurrently distributed DBs, the DB integration technologies also emphasise data usage (distilling) at an abstract level, via standard user interfaces and uniform data access [27], [28]. However, data distilling is not separable from the fractal object of FDBS, even though it can be optionally implemented or ignored by different component systems. ...
... From a single DB's perspective, data distilling can be distinguished from the backend DB system and merged into upper-layer business logic implementations. When it comes to concurrently distributed DBs, the DB integration technologies also emphasise data usage (distilling) at an abstract level, via standard user interfaces and uniform data access [27], [28]. However, data distilling is not separable from the fractal object of FDBS, even though it can be optionally implemented or ignored by different component systems. ...
Preprint
Full-text available
Cloud computing has made federated database systems (FDBS) significantly more practical to implement than in the past. As part of a recent Web-based Geographic Information System (WebGIS) project, we are employing cloud-native technologies (from the container ecosystem) to develop a federated database (DB) infrastructure, to help manage and utilise the distributed and various geospatial data. Unfortunately, there seem to be inherent challenges and complexity of applying the container and Kubernetes technologies to building and running DB systems. Considering that most of the geospatial and theme data are pre-obtained and fixed in our WebGIS project, we decided to focus on the read-only user queries and still resort to Kubernetes to implement an FDBS instance to use. Unlike the de facto practices (e.g., using the StatefulSets mechanism, extending Kuberentes APIs, or employing KubeFed), our solution for Kubernetes-aided FDBS simplifies the tech stack by investigating the fractal object of federated data management, inclusively containerising DB instances, and using the lightweight Deployment mechanism to handle stateless DB containers. Overall, this research not only reveals an easy-to-implement approach to constructing read-only components in a fully-fledged FDBS, but also proposes and demonstrates a novel methodology for FDBS investigations.