Cloud computing architecture

From Wikipedia, the free encyclopedia

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

Cloud Computing Sample Architecture

Client platforms[edit]

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, tablets and mobile devices that users directly interact with. These client platforms interact with the cloud data storage via an application (middle ware), via a web browser, or through a virtual session. Virtual sessions in particular require secure encryption algorithm frame working which spans the entire interface.[1]

Zero client[edit]

The zero or ultra-thin client initializes the network to gather required configuration files that then tell it where its OS binaries are stored.[2] 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.[3]


An online network storage where data is stored and accessible to multiple clients. Cloud storage is generally deployed in the following configurations: public cloud, private cloud, community cloud, or some combination of the three also known as hybrid cloud.[4]

In order to be effective, the cloud storage needs to be agile, flexible, scalable, multi-tenancy, and secure.[5]


Software as a service (SaaS)[edit]

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.[6][7]

Software as a service provides the equivalent of installed applications in the traditional (non-cloud computing) delivery of applications.[8]

Software as a service has four common approaches:[8][9]

  1. single instance
  2. multi-instance
  3. multi-tenant
  4. flex tenancy

Of these, flex tenancy is considered the most user adaptive SaaS paradigm in designated multi-input four way manifold models.[10] Such systems are based on simplified encryption methods that target listed data sequences over multiple passes.[11] 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)[edit]

Development as a service is web based, community shared tool set. This is the equivalent to locally installed development tools in the traditional (non-cloud computing) delivery of development tools.[8]

Data as a service (DaaS)[edit]

Data as a service web based design construct where cloud 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.[12]

Platform as a service (PaaS)[edit]

Platform as a service is cloud computing service which provides the users with application platforms and databases as a service.[4] This is equivalent to middleware in the traditional (non-cloud computing) delivery of application platforms and databases.[8]

Infrastructure as a service (IaaS)[edit]

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.[8]


Generally, the cloud network layer should offer:

Allowing users to have uninterrupted access to their data and applications.[13]
  • 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.[14]

See also[edit]

Further reading[edit]

  • 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.


  1. ^ Sudha, M (2012). "Enhanced security framework to ensure data security in cloud computing using cryptography". Advances in Computer Science and Its Applications. 1 (1).
  2. ^ Madden, B. (May 19, 2012) (2010-05-19). "Wyse hopes to shake up the thin client industry with a new zero client platform. Will it work?". Retrieved 2012-05-27.{{cite web}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  3. ^ Segal, I. ""When Is Zero Client Not Zero Client?", SysGen, Inc" (PDF). Archived from the original (PDF) on 2003-04-03. Retrieved 2012-05-27.
  4. ^ a b Mell, P.; Grance, T. (September 2011). "The NIST Definition of Cloud Computing. NIST Special Publication 800-145 (September 2011). National Institute of Standards and Technology, U.S. Department of Commerce" (PDF). Retrieved 2012-05-20.
  5. ^ Sherbak, T.; Sweere, N. & Belapurkar, V. "Virtualized Enterprise Storage for Flexible, Scalable Private Clouds. Reprinted from Dell Power Solutions, 2012 Issue 1" (PDF). Retrieved 2012-05-27.
  6. ^ Chou, Timothy. Introduction to Cloud Computing: Business & Technology.
  7. ^ Daisy, witson. "what is cloud computing". JanBask.
  8. ^ a b c d e Wang, R. "Tuesday's Tip: Understanding The Many Flavors of Cloud Computing and SaaS". Retrieved 2012-05-27.
  9. ^ "Understanding the Flex Tenancy Architecture by CITRIX". Retrieved 2012-05-27.
  10. ^ Andrikopoulos, Vasilios (2013). "Towards Modeling and Execution of Collective Adaptive Systems". ICSOC 2013: Service-Oriented Computing – ICSOC 2013 Workshops. Lecture Notes in Computer Science. 8377: 69–81. doi:10.1007/978-3-319-06859-6_7. ISBN 978-3-319-06858-9. S2CID 15216208.
  11. ^ Li, Lin (2014). "Multi-tenant Data Authentication Model for SaaS" (PDF). The Open Cybernetics and Systematics Journal. 8 (8): 322–329. doi:10.2174/1874110X01408010322.
  12. ^ 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   
  13. ^ M. Noormohammadpour, C. S. Raghavendra, "Datacenter Traffic Control: Understanding Techniques and Trade-offs," IEEE Communications Surveys & Tutorials, vol. PP, no. 99, pp. 1-1.
  14. ^ Paladi, Nicolae; Gehrmann, Christian (2015). "Towards Secure Multi-tenant Virtualized Networks" (PDF). 2015 IEEE Trustcom/BigDataSE/ISPA. Vol. 1. pp. 1180–1185. doi:10.1109/Trustcom.2015.502.