Content deleted Content added
Rescuing 1 sources and tagging 0 as dead. #IABot (v2.0beta15) |
m clean up |
||
Line 9:
===The zero client===
The zero or ultra-thin client initializes the network to gather required configuration files that then tell it where its OS binaries are stored.<ref>{{cite web|url=http://www.brianmadden.com/blogs/brianmadden/archive/2010/05/19/wyse-unveils-a-new-extensible-zero-client-platform-how-quot-zero-quot-is-this-and-how-will-it-help-citrix-here-s-our-full-analysis.aspx|last=Madden, B. (May 19, 2012) |title = Wyse hopes to shake up the thin client industry with a new zero client platform. Will it work?|date=2010-05-19 |accessdate=2012-05-27}}</ref> The entire zero client device runs via the network. This creates a single point of failure, in that, if the network goes down, the device is rendered useless.<ref>{{cite web |url=http://www.assurx.com/pdf/ZeroClient.pdf |last=Segal, I. |title="When Is Zero Client Not Zero Client?", SysGen, Inc |access-date=2012-05-27 |archive-url=https://web.archive.org/web/20030403135932/http://assurx.com/pdf/ZeroClient.pdf |archive-date=2003-04-03 |
==Cloud storage==
{{Main
An online network storage where data is stored and accessible to multiple clients. Cloud storage is generally deployed in the following configurations: [[Cloud computing#Public cloud|public cloud]], [[Cloud computing#Private cloud|private cloud]], [[Cloud computing#Community cloud|community cloud]], or some combination of the three also known as [[Cloud computing#Hybrid cloud|hybrid cloud]].<ref name="bare_url">{{cite web|title = The NIST Definition of Cloud Computing. NIST Special Publication 800-145 (September 2011). National Institute of Standards and Technology, U.S. Department of Commerce |author1=Mell, P. |author2=Grance, T. |url=http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf |date=September 2011 |accessdate=2012-05-20}}</ref>
Line 21:
===Software as a service (SaaS)===
{{Main
The [[software-as-a-service]] (SaaS) service-model involves the cloud provider installing and maintaining software in the cloud and users running the software from cloud over the Internet (or Intranet). The users' client machines require no installation of any application-specific software since cloud applications run in the cloud. SaaS is scalable, and system administrators may load the applications on several servers. In the past, each customer would purchase and load their own copy of the application to each of their own servers, but with the SaaS the customer can access the application without installing the software locally. SaaS typically involves a monthly or annual fee.<ref name="Chou">
Line 39:
# flex tenancy
Of these, flex tenancy is considered the most user adaptive SaaS paradigm in designated multi-input four way manifold models.<ref name="Andrikopoulos">{{cite journal|last1=Andrikopoulos|first1=Vasilios|title=Towards Modeling and Execution of Collective Adaptive Systems|journal=ICSOC 2013: Service-Oriented Computing – ICSOC 2013 Workshops|date=2013|pages=
===Development as a service (DaaS)===
Line 48:
===Platform as a service (PaaS)===
{{Main
[[Platform as a service]] is cloud computing service which provides the users with application platforms and databases as a service.<ref name="bare_url" /> This is equivalent to middleware in the traditional (non-cloud computing) delivery of application platforms and databases.<ref name="enterpriseirregulars" />
|