Content deleted Content added
Citation bot (talk | contribs) Alter: title, template type. Add: chapter, date, doi. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Headbomb | Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox2 | #UCB_webform_linked 41/217 |
|||
| (25 intermediate revisions by 23 users not shown) | |||
Line 1:
{{Short description|none}} <!-- "none" is preferred when the title is sufficiently descriptive; see [[WP:SDNONE]] -->
'''Cloud computing architecture''' refers to the components and subcomponents required for [[cloud computing]]. These components typically consist of a front end platform (fat client, thin client, mobile
[[File:CloudComputingSampleArchitecture.svg|alt=|border|right|frameless|440x440px|Cloud Computing Sample Architecture]]
==Client platforms==
{{See also|Category:Cloud clients}}
Cloud computing architectures consist of front-end platforms called clients or cloud clients.
===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 |url-status=dead}}</ref>
Line 15 ⟶ 14:
{{Main|Cloud storage}}
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
In order to be effective, the cloud storage needs to be agile, flexible, scalable, [[multi-tenancy]], and secure.<ref>{{cite web|title = Virtualized Enterprise Storage for Flexible, Scalable Private Clouds. Reprinted from Dell Power Solutions, 2012 Issue 1 |author1=Sherbak, T. |author2=Sweere, N. |author3=Belapurkar, V. |
==Delivery==
Line 25 ⟶ 24:
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">
{{cite book|title = Introduction to Cloud Computing: Business & Technology|first = Timothy|last = Chou|url = https://www.scribd.com/doc/64699897/Introduction-to-Cloud-Computing-Business-and-Technology}}</ref><ref>{{cite web |last1=Daisy |first1=witson |title=what is cloud computing |date=25 September 2023 |url=https://www.janbasktraining.com/blog/what-is-cloud-computing/ |publisher=JanBask}}</ref>
Software as a service provides the equivalent of installed applications in the traditional (non-cloud computing) delivery of applications.<ref name="enterpriseirregulars">
Line 40 ⟶ 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
===Development as a service (DaaS)===
Line 46 ⟶ 45:
===Data as a service (DaaS)===
[[Data as a service]]
===Platform as a service (PaaS)===
Line 56 ⟶ 55:
==Networking==
{{main|Data center network architectures}}
Generally, the cloud network layer should offer:
* High bandwidth and [[network latency|low latency]]
:Allowing users to have uninterrupted access to their data and applications.<ref name=architecture>M. Noormohammadpour, C. S. Raghavendra, [https://www.researchgate.net/publication/321744877_Datacenter_Traffic_Control_Understanding_Techniques_and_Trade-offs "Datacenter Traffic Control: Understanding Techniques and Trade-offs,"] IEEE Communications Surveys & Tutorials, vol. PP, no. 99, pp. 1-1.</ref>
* Agile network
:On-demand access to resources requires the ability to move quickly and efficiently between servers and possibly even clouds.
* Network security
:Security is always important, but when you are dealing with multi-tenancy, it becomes much more important because you're dealing with segregating multiple customers.<ref>{{
==See also==
*[[Cloud collaboration]]
*[[Cloud computing]]
*[[Cloud
*[[Cloud database]]
*[[Cloud storage]]
==Further reading==
* Reese, G. (2009). Cloud Application Architectures: Building Applications and Infrastructure in the Cloud. Sebastopol, CA: O'Reilly Media, Inc. (2009).
* Rhoton, J. and Haukioja, R. (2011). Cloud Computing Architected: Solution Design Handbook. Recursive Limited, 2011. {{ISBN|0-9563556-1-7}}.
* Shroff, Dr. Gautam. Enterprise Cloud Computing: Technology, Architecture, Applications.
==References==
| |||