2013 IEEE Ninth World Congress on Services 2013
DOI: 10.1109/services.2013.59
|View full text |Cite
|
Sign up to set email alerts
|

Towards DaaS 2.0: Enriching Data Models

Abstract: Abstract-Current Data as a Service solutions present a lack of flexibility in terms of allowing users to customize the underlying data models by including new concepts or functionalities. Data providers either publish global APIs to make data available, or "sell" and transfer data to clients so they can do whatever they want with it. Thereby, collaboration and B2B becomes limited and sometimes is not even feasible. Our technology implements the necessary mechanisms for data providers to enable their clients to… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
2
0

Year Published

2017
2017
2020
2020

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 2 publications
0
2
0
Order By: Relevance
“…By default, COMPSs works standalone with local storage, but it also provides support for interaction with existing storage technologies, such as dataClay (Marti et al, 2013) and Hecuba (Tejedor et al, 2015), through a simple API. In addition to the exploitation of Grids, Clusters, and Cloud environments, COMPSs contains specific connectors to enable its deployment in Dockers, and is currently working on the integration with Mesos.…”
Section: Compssmentioning
confidence: 99%
“…By default, COMPSs works standalone with local storage, but it also provides support for interaction with existing storage technologies, such as dataClay (Marti et al, 2013) and Hecuba (Tejedor et al, 2015), through a simple API. In addition to the exploitation of Grids, Clusters, and Cloud environments, COMPSs contains specific connectors to enable its deployment in Dockers, and is currently working on the integration with Mesos.…”
Section: Compssmentioning
confidence: 99%
“…A new type of consumerproducer applications can be designed, where the data can be stored in these persistent storage and be accessed during the execution of the producer application or after. While this data can be stored in files or databases, both are designed to use block devices, while this type of storage supports other alternatives, as direct object storage [36].In the environment described before, persistent storage can be used to store the results of simulations. The data can be consumed by the analytic services as soon as it has been produced and the results of the analytic steps can also be stored in persistent storage, in order to be used in visualization steps or in future queries.…”
mentioning
confidence: 99%