Data as a service

In computing, data as a service, or DaaS, is enabled by software as a service (SaaS).[1] Like all "as a service" (aaS) technology, DaaS builds on the concept that its data product can be provided to the user on demand,[2] regardless of geographic or organizational separation between provider and consumer. Service-oriented architecture (SOA), and the widespread use of API, has rendered the platform on which the data resides as irrelevant.[3]

For Desktop as a service (DaaS), see Desktop virtualization.

DaaS began primarily in Web mashups and, since 2015, has been increasingly employed both commercially, and within organizations such as the United Nations.[4]

Traditionally, most organisations have used data stored in a self-contained repository, for which software was specifically developed to access and present the data in a human-readable form. One result of this paradigm is the bundling of both the data and the software needed to interpret it into a single package, sold as a consumer product. As the number of bundled software with data packages proliferated, and required interaction among one another, another layer of interface was required. These interfaces, collectively known as enterprise application integration (EAI), often tended to encourage vendor lock-in, as it is generally easy to integrate applications that are built upon the same foundation technology.[5]

The result of the combined software/data consumer package and required EAI middleware has been an increased amount of software for organizations to manage and maintain, simply for the use of particular data. In addition to routine maintenance costs, a cascading amount of software updates are required as the format of the data changes. The existence of this situation contributes to the attractiveness of DaaS to data consumers, because it allows for the separation of data cost and of data usage from the cost of a specific software environment or platform. Sensing as a Service[6][7] (S2aaS) is a business model that integrates Internet of Things data to create data trading marketplaces.

Vendors, such as MuleSoft, Oracle Cloud and Microsoft Azure, undertake development of DaaS that more rapidly computes large volumes of data; integrates and analyzes that data; and publish it in real-time, using Web service APIs that adhere to its REST architectural constraints (RESTful API).

Benefits of DaaS

Data as a service operates on the premise that data quality can occur in a centralized place, cleansing and enriching data and offering it to different systems, applications, or users, irrespective of where they were in the organization, or on the network.[3] DaaS undertakes to provide the following advantages:

  • Agility – users can move quickly, due to the simplicity of data access, and not needing extensive knowledge of the underlying data. Data structures and location-specific requirements can be modified to meet user needs.
  • Cost-effectiveness – providers can build the base with the data experts and outsource the presentation layer, which makes for very cost-effective user interfaces and makes change requests at the presentation layer much more feasible.
  • Data quality – data access is controlled through data services, which tends to improve data quality, as there is a single point for updates. Once those services are tested, only regression testing is needed, if they remain unchanged for the next deployment.

Pricing models

There are hundreds of DaaS vendors on the Web, and the pricing models by which they charge their customers fall mainly into two major categories.[8]

  1. Volume-based model that has two approaches:
    1. quantity-based pricing is the simplest model to implement. A vendor charges its customers based on the amount of data they want to use. Subscriptions for unlimited amounts of data is referred to as the "fire-hose approach".
    2. pay-per-call services, wherein vendors charge for each call from the customer to the API.
  2. data type-based models are structured by vendors to charge users based on the type or attribute of data they require. Geographic, financial, and historical data necessary for customer business are examples of types of data upon which pricing may be based. Some vendors, such as Microsoft Azure, store the data in three different types — blobs, queues, and tables.[9]

Criticism

The drawbacks of DaaS are generally similar to those associated with any type of cloud computing, such as the reliance of the user on the service provider's ability to avoid server downtime. A common criticism specific to the DaaS model is that when compared to traditional data delivery, the consumer is merely "renting" the data, and using it to produce analytics or insights, and, generally, the original data is not available for download.[10]

gollark: But, if you *don't* do that, you can actually make your website load faster.
gollark: So, the average webpage downloads vast amounts of random JS to do some tasks, often from Google or other CDNs.
gollark: osmarks.tk, for example, uses *no* AMP and is much lighter due to not pulling giant amounts of JS from Google servers.
gollark: It's not actually really faster than sane use of regular web tech, it just cheats by having preloading in search results.
gollark: And design the spec.

See also

References
  1. Machan, Dyan (August 19, 2009). "DaaS:The New Information Goldmine". Wall Street Journal. Retrieved 2010-06-09. Unfortunately, the business world has given this baby a jargony name: data as a service, or its diminutive, DaaS.
  2. Olson, John A. (January 2010). "Data as a Service: Are We in the Clouds?". Journal of Map & Geography Libraries. 6 (1): 76–78. doi:10.1080/15420350903432739.
  3. Dyche, Jill. "Data-as-a-service, explained and defined". SearchDataManagement.com. Retrieved October 24, 2010.
  4. "Statistical Data as a Service and Internet Mashups". Zoltan Nagy, United Nations. Retrieved 2010-06-09.
  5. Cagle, Kurt. "Why Data as a Service Will Reshape EAI". DevX.com. Retrieved October 24, 2010.
  6. Perera, Charith; Zaslavsky, Arkady; Christen, Peter; Georgakopoulos, Dimitrios (2014-01-01). "Sensing as a service model for smart cities supported by Internet of Things". Transactions on Emerging Telecommunications Technologies. 25 (1): 81–93. arXiv:1307.8198. doi:10.1002/ett.2704. ISSN 2161-3915.
  7. Perera, Charith (2017). Sensing as a Service for Internet of Things: A Roadmap. Leanpub.
  8. "Data as a Service: Pricing Models for the Future of Data". programmableweb.com. 2010-08-26. Retrieved October 29, 2010.
  9. Redkar, Tejaswi. "Chapter 4 – Windows Azure Storage Part I — Blobs". Windows Azure Platform. Apress, 2009.
  10. "Exploring PBBI's Vision for Geospatial Data as a Service (podcast)". Directions Magazine. Archived from the original on October 24, 2010. Retrieved November 14, 2010.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.