Polypheny
 | The topic of this article may not meet Wikitia's general notability guideline. |
| Developer(s) | Polypheny GmbH & The Polypheny Project |
|---|---|
| Initial release | 18 January 2019 |
| Stable release | v0.9.1
/ 3 August 2023 |
| Written in | {{#statements:P277|from=Q122920886}} |
| Operating system | Cross-platform |
| Type | Database System |
| License | {{#statements:P275|from=Q122920886}} |
| Website | https://polypheny.com |
Polypheny is a multi-model database management system (DBMS) designed to process and manage a diverse array of data and mixed workloads.[2] Based on the concept of a PolyDBMS (Polymorphic Database Management System), Polypheny presents a technical framework for managing diverse data through a unified platform.[2] The system can process complex queries across extensive and heterogeneous datasets by utilizing various third-party database systems, each optimized for specific workloads, as execution engines.[3][4] It accommodates structured, semi-structured, and unstructured data, allowing for the processing of various workloads.[5]
The system is capable of managing various types of data while preserving their semantics. Polypheny natively supports the relational, document and labeled-property graph data models.[6] Furthermore, Polypheny includes a browser-based user interface, which provides a platform for the management and monitoring of the system, as well as facilitating data and schema management and data querying. This interface also supports computational notebooks, providing a single interface for data integration and analysis tasks.
Polypheny supports a variety of query languages, such as SQL, openCypher, the Contextual Query Language, and the MongoDB Query Language, which contributes to its versatility in data retrieval and management. A distinctive feature of Polypheny lies in its capability to execute cross-model queries, allowing for the combination of data, irrespective of its organizational structure and model, within a singular query through a unified query language and interface.[6] This functionality simplifies data interaction and supports a unified approach to managing and querying diverse data sets within the system.
History
Polypheny started as a research project at the University of Basel in 2017.[7][8] The initial funding for the project has been provided by the Swiss National Science Foundation (SNF).[8] The project was rooted in the exploration and development of advanced database management systems, with the objective of developing a solution that could handle a wide range of data types, query languages, and workloads.[8] The foundational research and development were focused on innovating data management and developing a system intended to address the varied and changing needs of data-driven applications.[9]
A significant milestone for Polypheny has been the selection as a mentoring organization for the Google Summer of Code (GSoC) in 2021[10], followed by subsequent selection in 2022.[11] This involvement provided a platform for the project to gain visibility, engage with the global developer community, and facilitate collaborative development and knowledge exchange. The GSoC participation contributed to the advancement of the project, bringing in fresh perspectives and contributing to the enhancement and refinement of Polypheny.
The project reached a milestone with its first public release in February 2022[12], transitioning from a research project to a publicly available database management system. This release was characterized by the introduction of several key features and functionalities, including support for multiple data models and query languages, and the ability to perform cross-model queries. The public release made the solutions developed during the research phase available to a wider audience and various applications.
The establishment of Polypheny GmbH followed in December 2022[13], adopting an open-core model to drive the project forward.[14] This model is intended to ensure the continued development and support of the open-source (community) edition of Polypheny and offers additional functionalities through enterprise editions. The formation of Polypheny GmbH indicated a move towards commercializing the Polypheny DBMS, while also aiming to ensure its ongoing development and adaptation to the changing needs and challenges of data management and analytics across various applications and sectors.
Platform
Polypheny is developed using Java, enabling it to run on systems for which an appropriate Java Runtime Environment (JRE) is available. The available releases include a Java Virtual Machine (JVM) and other dependencies to facilitate installation and execution across various operating systems. Releases are available for Windows, macOS, and Linux.[7] For Linux, support is limited to distributions using either RPM or DEB packages.
Schema model
Polypheny's schema model accommodates multiple data models, including the relational, document, and Labeled Property Graph (LPG) models, with each model holding equal standing within the system.[6] Unlike some multi-model database systems that convert data into a single (extended) data model, Polypheny maintains the intrinsic semantics of each data model by supporting them in their original forms.[6] This approach is intended to maintain the unique advantages and characteristics of each data model, aiming to provide users with the respective benefits and capabilities of each model.[2] No model is prioritized or considered primary; they coexist, providing an environment for managing diverse data types and structures.
In Polypheny, namespaces are pivotal in organizing and structuring data, acting as a crucial element for defining logical schemas. Each namespace in Polypheny acts as a logical container, segregating different data models within the logical schema and identified by a unique name corresponding to a specific data model. The definition of a schema occurs within a namespace, and this namespace determines the rules and semantics for that schema, adhering to the principles of the corresponding data model.[6] For instance, a namespace associated with a relational model adheres to its schema rules, while a namespace related to a document model follows its schema-less structure.
Polypheny supports cross-model queries and automated mapping between different data models.[6] This capability allows data, organized and structured according to different data models, to be combined in a single query using one query language and interface, without the need for manual data transformation or migration.[15]
Storage model
Polypheny's storage model is designed to manage and store a variety of data, with a focus on performance and scalability. The model distinguishes between data stores and data sources, each having a specific role in data management, storage, and access within the system.[6]
Data Stores
Data stores in Polypheny are integral components responsible for persistently storing data and executing queries. They serve not only as storage units but also have the capability to execute queries, participating in the data retrieval process.[2][4] Polypheny supports several well-known and highly optimized and domain-specific database systems to be utilized as data stores. This inherently distributed architecture also introduces horizontal scaling, which can be advantageous when processing huge amounts of data. The data stores can handle different data models and are optimized to ensure efficient data storage and retrieval. Polypheny also allows data to be replicated and partitioned across multiple data stores.[3][16]
Data sources
Data sources act as connectors to external systems and do not store data persistently within Polypheny.[6] They serve as bridges to other sources of information (e.g., other database systems, blockchains, files), allowing Polypheny to access and integrate external data without physically storing it.[6] Data sources allow Polypheny to execute queries on external systems, retrieve data, and integrate it with the data in its own data stores. This means that Polypheny can access and utilize data from external databases and static files, providing a unified interface for accessing and managing data across multiple platforms and systems.
Internal engine
Polypheny incorporates an internal execution engine, involved in query optimization and enabling the execution of query plans across multiple underlying data stores and data sources. Additionally, this internal engine can compensate for missing query functions on a data store or data source. Although this integrated engine might not achieve the same level of efficiency and optimizations as certain highly optimized database systems, it is not confined to a specific data model and natively supports all three data models available in Polypheny.[6]
The internal execution engine plays a key role in executing cross-model queries and managing automated mapping between different data models. When a query is executed, the engine determines a method to retrieve and combine data from various data stores and sources, considering the different data models and query functions involved. It utilizes various optimization techniques, such as cost-based optimization and rule-based optimization, to determine an execution plan for each query, aiming to perform data retrieval in a resource-efficient manner.
Furthermore, the internal execution engine also facilitates the seamless execution of cross-model queries, enabling users to query data across different data models using a single query language.[6] It handles the task of mapping between different data models, aiming to execute queries accurately and efficiently, even when they involve multiple data models and storage systems.
When a query involves data from different stores or sources, the internal execution engine coordinates the retrieval and integration of this data, intending to present a unified set of results to the user.[15] This functionality can be advantageous in environments with diverse data models and systems, as it provides a unified interface for query execution and data retrieval.
References
- ↑ "Polypheny". Retrieved 2023-10-03.
Polypheny: The first PolyDBMS and your Ultimate Data Management Platform.
- ↑ 2.0 2.1 2.2 2.3 Vogt, Marco; Lengweiler, David; Geissmann, Isabel; Hansen, Nils; Hennemann, Marc; Mendelin, Cédric; Philipp, Sebastian; Schuldt, Heiko (2021), Rezig, El Kindi; Gadepally, Vijay; Mattson, Timothy; Stonebraker, Michael (eds.), "Polystore Systems and DBMSS: Love Marriage or Marriage of Convenience?", Heterogeneous Data Management, Polystores, and Analytics for Healthcare, Lecture Notes in Computer Science, Cham: Springer International Publishing, vol. 12921, pp. 65–69, doi:10.1007/978-3-030-93663-1_6, ISBN 978-3-030-93662-4, retrieved 2023-10-03
- ↑ 3.0 3.1 Vogt, Marco; Hansen, Nils; Schönholz, Jan; Lengweiler, David; Geissmann, Isabel; Philipp, Sebastian; Stiemer, Alexander; Schuldt, Heiko (2021), Gadepally, Vijay; Mattson, Timothy; Stonebraker, Michael; Kraska, Tim (eds.), "Polypheny-DB: Towards Bridging the Gap Between Polystores and HTAP Systems", Heterogeneous Data Management, Polystores, and Analytics for Healthcare, Lecture Notes in Computer Science, Cham: Springer International Publishing, vol. 12633, pp. 25–36, doi:10.1007/978-3-030-71055-2_2, ISBN 978-3-030-71054-5, retrieved 2023-10-03
- ↑ 4.0 4.1 Azzini, Antonia; Barbon, Sylvio; Bellandi, Valerio; Catarci, Tiziana; Ceravolo, Paolo; Cudré-Mauroux, Philippe; Maghool, Samira; Pokorny, Jaroslav; Scannapieco, Monica (2021), Goedicke, Michael; Neuhold, Erich; Rannenberg, Kai (eds.), "Advances in Data Management in the Big Data Era", Advancing Research in Information and Communication Technology, Cham: Springer International Publishing, vol. 600, pp. 99–126, doi:10.1007/978-3-030-81701-5_4, ISBN 978-3-030-81700-8, retrieved 2023-10-07
- ↑ Kiehn, Felix; Schmidt, Mareike; Glake, Daniel; Panse, Fabian; Wingerath, Wolfram; Wollmer, Benjamin; Poppinga, Martin; Ritter, Norbert (2022). "Polyglot data management: state of the art & open challenges". Proceedings of the VLDB Endowment. 15 (12): 3750–3753. doi:10.14778/3554821.3554891. ISSN 2150-8097.
- ↑ 6.00 6.01 6.02 6.03 6.04 6.05 6.06 6.07 6.08 6.09 6.10 Vogt, Marco Dieter (2022). Adaptive Management of Multimodel Data and Heterogeneous Workloads (PhD thesis). University of Basel. doi:10.5451/unibas-ep90279.
- ↑ 7.0 7.1 "Database of Databases — Polypheny". Database of Databases. 2023-02-16. Retrieved 2023-10-07.
- ↑ 8.0 8.1 8.2 "SNSF Data Portal". data.snf.ch. Retrieved 2023-10-07.
- ↑ Vogt, Marco; Stiemer, Alexander; Schuldt, Heiko (2018). "Polypheny-DB: Towards a Distributed and Self-Adaptive Polystore". 2018 IEEE International Conference on Big Data (Big Data). IEEE. pp. 3364–3373. doi:10.1109/BigData.2018.8622353. ISBN 978-1-5386-5035-6.
- ↑ "Google Summer of Code". summerofcode.withgoogle.com. Retrieved 2023-10-06.
- ↑ "Google Summer of Code". summerofcode.withgoogle.com. Retrieved 2023-10-06.
- ↑ "Release v0.7.0 · polypheny/Polypheny-DB". GitHub. Retrieved 2023-10-06.
- ↑ "Company | Polypheny". polypheny.com. Retrieved 2023-10-07.
- ↑ "Pricing | Polypheny". polypheny.com. Retrieved 2023-10-07.
- ↑ 15.0 15.1 Conrad, André; Utzmann, Philipp; Klettke, Meike; Störl, Uta (2022-10-23). "Metamodels to support database migration between heterogeneous data stores". ACM: 546–551. doi:10.1145/3550356.3561574. ISBN 978-1-4503-9467-3.
{{cite journal}}: Cite journal requires|journal=(help) - ↑ Sá, Rafael Avilar; Moreira, Leonardo O.; Machado, Javam C. (2023-09-25). "Improving Interoperability between Relational and Blockchain-based Database Systems: A Middleware approach". Sociedade Brasileira de Computação - SBC: 115–127. doi:10.5753/sbbd.2023.232503.
{{cite journal}}: Cite journal requires|journal=(help)
External links
This article "Polypheny" is from Wikipedia. The list of its authors can be seen in its historical. Articles taken from Draft Namespace on Wikipedia could be accessed on Wikipedia's Draft Namespace.