Dew computing: Difference between revisions

Revision as of 15:15, 17 January 2019

Revision as of 12:05, 22 January 2019

Line 15:

As an information technology paradigm, dew computing, using the core concept of cloud computing, seeks to use the capabilities of [[personal computer]]s along with [[cloud services]] in a more reliable manner.<ref name=":2" /><ref name=":6" /><ref name=":5" />

The key features of dew computing are independence and collaboration. Independence means that the local device must be able to provide service without a continuous connection to the [[Internet]]. Collaboration means that the application must be able to connect to the cloud service and synchronize data when appropriate.<ref name=":4" />

Use of the word "[[dew]]" reflects natural phenomena: [[cloud]]s are far from the ground, [[fog]] is closer to the ground, and [[dew]] is on the ground. Analogically, cloud computing is a remote service, fog computing is beside the user, and dew computing is at the user end.

Line 38:

** The local device and the cloud both store copies of the same [[database]]. One of these two databases is considered the main version and can be defined as such by the [[database administrator]]. This service increases the reliability of a database since one of the databases can act as the [[backup]] for the other.<ref name=":0" />

* Software in Dew (SiD)

** The configuration and ownership of a software are saved in the [[Cloud computing|cloud]]. Good examples of this are the [[Apple App Store]] and [[Google Play]] where the applications the user installs are saved to their account and can be installed on any device linked to their account.<ref name=":0" />

* Platform in Dew (PiD)

** A software development suite must be installed on the local device with the settings and application data synchronized to the cloud service. A [[Software development kit|Software Development Kit]] on its own does not satisfy these requirements; it must be able to synchronize development data, system deployment data, and online backups. An example of this category is GitHub.<ref name=":0" />

Line 47:

== Possible challenges ==

Dew computing faces a number of technical challenges, including issues related to power management, processor utility, data storage, the viability of operation system, network model, communication model, programming principles, dew recommenderrecommended engine, local dew network, personal high productivity, database security, and behaviors of the browser.<ref name=":3">{{Cite web|url=https://ieeexplore.ieee.org/document/8114187/|title=An Introduction to Dew Computing: Definition, Concept and Implications - IEEE Journals & Magazine|website=ieeexplore.ieee.org|access-date=2018-06-30}}</ref>

== See also ==