Cloud computing architecture: Difference between revisions

Revision as of 11:31, 4 February 2020

Latest revision as of 02:41, 20 June 2025

(29 intermediate revisions by 26 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 device), back end platforms (servers, storage), a cloud based delivery, and a network (Internet, Intranet, Intercloud). Combined, these components make up cloud computing architecture.

[[File:CloudComputingSampleArchitecture.svg|alt=|border|right|frameless|440x440px|Cloud Computing Sample Architecture]]

==Cloud clientClient platforms==

{{See also|Category:Cloud clients}}

Cloud computing architectures consist of front-end platforms called clients or cloud clients. These clients are servers, fat (or thick) clients, thin clients, zero clients, [[tablet computer|tablets]] and mobile devices that users directly interact with. These client platforms interact with the cloud data storage via an application (middlewaremiddle ware), via a web browser, or through a virtual session. Virtual sessions in particular require secure encryption algorithm frameworkingframe working which spans the entire interface.<ref>{{cite journal |last1=Sudha |first1=M |title=Enhanced security framework to ensure data security in cloud computing using cryptography |journal=Advances in Computer Science and itsIts Applications |date=2012 |volume=1 |issue=1}}</ref>

===The zero client===

===The zeroZero 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>

==Cloud storageStorage==

{{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 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 |doi=10.6028/NIST.SP.800-145 |accessdate=2012-05-20}}</ref>

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. |lastname-authorlist-ampstyle=yesamp |url=http://i.dell.com/sites/content/business/solutions/power/en/Documents/ps1q12-20120209-sherbak.pdf |accessdate=2012-05-27}}</ref>

==Delivery==

==Cloud based delivery==

===Software as a service (SaaS)===

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 36 ⟶ 35:

# single instance

# multi -instance

# multi-tenant

# 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 journalbook|last1=Andrikopoulos|first1=Vasilios|titles2cid=15216208|chapter=Towards Modeling and Execution of Collective Adaptive Systems|journaltitle=ICSOC 2013: Service-Oriented Computing – ICSOC 2013 Workshops|series=Lecture Notes in Computer Science|date=2013|volume=8377|pages=69–81|urldoi=https://pdfs.semanticscholar10.org1007/868d/7ced8e15aad63b0bbb7bf4f0a3269742d79f.pdf978-3-319-06859-6_7|isbn=978-3-319-06858-9}}</ref> Such systems are based on simplified encryption methods that target listed data sequences over multiple passes.<ref name="Li">{{cite journal|last1=Li|first1=Lin|title=Multi-tenant Data Authentication Model for SaaS|journal=The Open Cybernetics and Systematics Journal|date=2014|volume=8|issue=8|pages=322–329|doi=10.2174/1874110X01408010322|url=http://benthamopen.com/contents/pdf/TOCSJ/TOCSJ-8-322.pdf|doi-access=free}}</ref> The simplicity of this concept makes flex tenancy SaaS popular among those without informatics processing experience, such as basic maintenance and custodial staff in franchise businesses.

===Development as a service (DaaS)===

Line 46 ⟶ 45:

===Data as a service (DaaS)===

[[Data as a service]] is web based design construct where couldcloud data is accessed through a defined API layer. DaaS services are often considered as a specialized subset of a Software as a Service (SaaS) offering.<ref>O. Terzo, P. Ruiu, E. Bucci and F. Xhafa, "Data as a Service (DaaS) for Sharing and Processing of Large Data Collections in the Cloud," ''2013 Seventh International Conference on Complex, Intelligent, and Software Intensive Systems'', Taichung, 2013    </ref>

===Platform as a service (PaaS)===

Line 55 ⟶ 54:

[[Infrastructure as a service]] is taking the physical hardware and going completely virtual (e.g. all servers, networks, storage, and system management all existing in the cloud). This is the equivalent to infrastructure and hardware in the traditional (non-cloud computing) method running in the cloud. In other words, businesses pay a fee (monthly or annually) to run virtual servers, networks, storage from the cloud. This will mitigate the need for a data center, heating, cooling, and maintaining hardware at the local level.<ref name="enterpriseirregulars" />

==Networking==

==Cloud computing 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>{{citeCite webconference| url = https://www.youtubediva-portal.comorg/watch?v=Db95UmMZWzcsmash/get/diva2:1041286/FULLTEXT01.pdf|last doi =Greaves, J10.1109/Trustcom.2015.502| (ofvolume Carpathia= Hosting)1| andpages Potti,= S.1180–1185| (oflast1 Citrix).= Paladi| Uploadedfirst1 by= CarpathiaHostingNicolae| onlast2 Feb= 22,Gehrmann| 2010first2 = Christian| title = Flex-Tenancy:Towards Secure Multi-Tenancytenant NetworkVirtualized EnvironmentsNetworks|accessdate=2012 book-05-27title = 2015 IEEE Trustcom/BigDataSE/ISPA| date = 2015}}</ref>

==See also==

*[[Cloud collaboration]]

*[[Cloud computing]]

*[[Cloud -computing comparison]]

*[[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.

* Wolfram, Stephen. [http://blog.stephenwolfram.com/2015/04/scientific-bug-hunting-in-the-cloud-an-unexpected-ceo-adventure/ Scientific Bug Hunting in the Cloud: An Unexpected CEO Adventure.]

==References==