Content deleted Content added
Gilded Snail (talk | contribs) copy-edits |
Largoplazo (talk | contribs) →History: Found independent citation for Wang's role |
||
(31 intermediate revisions by 18 users not shown) | |||
Line 1:
{{Short description|Information technology paradigm}}
{{technical|date=January 2019}}
'''Dew computing'''<ref name="urlAn Introduction to Dew Computing: Definition, Concept and Implications - IEEE Journals & Magazine">{{cite journal |title=An Introduction to Dew Computing: Definition, Concept and Implications - IEEE Journals & Magazine |journal= IEEE Access|year=2018 |volume=6 |pages=723–737 |doi=10.1109/ACCESS.2017.2775042 |last1=Ray |first1=Partha Pratim |s2cid=3324933 |doi-access=free }}</ref> is an [[information technology]] ([[Information technology|IT]]) paradigm that combines the core concept of [[cloud computing]] with the capabilities of end devices ([[personal computer]]s, [[mobile phone]]s, etc.).<ref>{{Cite journal|last=Wang|first=Yingwei|date=2015-09-16|title=Cloud-dew architecture
== History ==
The term "dew computing", as used in information technology, first appeared in 2015 in IT literature and since then has become a field of its own. The cloud-dew architecture was proposed by Yingwei Wang<ref>{{Cite web |date=2015-09-17 |title=Dew Architecture helps Ground Cloud Services |url=https://www.rdworldonline.com/dew-architecture-helps-ground-cloud-services/ |access-date=2025-03-03 |website=Research & Development World |language=en-US}}</ref> as a possible solution to the offline data accessibility problem.<ref name=":7">{{Cite web|url=http://wwwen.zte.com.cn/endata/magazine/ztecommunications/2017/5/articles/201711/t20171124_466311.html|title=Dew Computing and Transition of Internet Computing Paradigms - ZTE Corporation|website=wwwen.zte.com.cn|access-date=2018-06-30|archive-date=2018-09-15|archive-url=https://web.archive.org/web/20180915122113/http://wwwen.zte.com.cn/endata/magazine/ztecommunications/2017/5/articles/201711/t20171124_466311.html|url-status=dead}}</ref> At first, its scope included only [[web application]]s; broader applications were later proposed.<ref>Skala, Karolj; Davidović, Davor; Afgan, Enis; Sović, Ivan; Šojat, Zorislav: [https://www.ronpub.com/publications/OJCC_2015v2i1n03_Skala.pdf Scalable Distributed Computing Hierarchy: Cloud, Fog and Dew Computing] // Open Journal of Cloud Computing (OJCC), 2 (2015), 1; 16-24 doi:10.19210/1002.2.1.16</ref><ref name=":1" />
Dew computing is a model which was derived from the original concept of [[cloud computing]]. Other models have also emerged from cloud computing, including [[fog computing]], [[edge computing]]
Cloud computing provides universal access and [[scalability]]. However, having all the resources far from a user's control occasionally causes problems. In the classic cloud computing paradigm, when the internet connection to the [[Server (computing)|servers]] is lost, the user is unable to access their data; dew computing aims to solve this problem.<ref name=":0" /><ref name=":6">{{Cite web |
== Definition ==
Line 32 ⟶ 33:
** The local device must possess a duplicated fraction of the [[World Wide Web]] (WWW) or a modified copy of that fraction to satisfy the independence feature. Because this fraction synchronizes with the web, it satisfies the collaboration feature of dew computing.<ref name=":0" />
* Storage in Dew (SiD)
** The [[Storage (memory)|storage]] of the local device is partially or fully copied into the cloud. An example
* Database in Dew (DBiD)
** 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,
* Software in Dew (SiD)
** The configuration and ownership of software are saved in the [[Cloud computing|cloud]].
* 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
* Infrastructure as Dew (IaD)
** The local device is dynamically supported by cloud services. IaD can come in different forms, but the following two forms can be used: (1) the local device can have an exact duplicate DVM instance in the cloud, which is always kept in the same state as the local instance, or (2) the local device can have all its settings/data saved in the cloud, including system settings/data and data for each application.<ref name=":0" />
* Data in Dew (DiD)
** The term DiD is applied when all its applications satisfy the independence and collaboration requirements but cannot be placed in any of the above categories. An example
== Possible challenges ==
Dew computing faces a number of technical challenges, including issues related to power management, processor utility, and data storage. Other factors impacting the use of dew computing are the viability of the operation system, network model,
== See also ==
Line 57 ⟶ 58:
== References ==
{{Reflist}}
<references group="Skala, Karolj; Davidović, Davor; Afgan, Enis; Sović, Ivan; Šojat, Zorislav Scalable Distributed Computing Hierarchy: Cloud, Fog and Dew Computing // Open Journal of Cloud Computing (OJCC), 2 (2015), 1; 16-24 doi:10.19210/1002.2.1.16 " />
{{Cloud computing}}
[[Category:Post-cloud computing architecture]]
|