Cloud computing architecture
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.
- 1 Cloud client platforms
- 2 Cloud storage
- 3 Cloud based delivery
- 4 Cloud networking
- 5 See also
- 6 Further reading
- 7 References
Cloud client platforms
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. These client platforms interact with the cloud data storage via an application (middleware), via a web browser, or through a virtual session.
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. 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.
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.
Cloud based delivery
Software as a service (SaaS)
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 their cloud clients over the Internet (or Intranet). The users' client machines require no installation of any application-specific software - cloud applications run on the server (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.
Software as a service provides the equivalent of installed applications in the traditional (non-cloud computing) delivery of applications.
- single instance
- multi instance
- flex tenancy
Development as a service (DaaS)
Development as a service is web based, community shared development tools. This is the equivalent to locally installed development tools in the traditional (non-cloud computing) delivery of development tools.
Data as a service (DaaS)
Data as a service is web based design construct where by cloud data is accessed through some defined API layer. DaaS services are often considered as a specialized subset of a Software as a service offering.
Platform as a service (PaaS)
Platform as a service is cloud computing service which provides the users with application platforms and databases as a service. This is equivalent to middleware in the traditional (non-cloud computing) delivery of application platforms and databases.
Infrastructure as a service (IaaS)
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.
Generally, the cloud network layer should offer:
- High bandwidth (low latency)
- Allowing users to have uninterrupted access to their data and applications.
- 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.
- 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. Scientific Bug Hunting in the Cloud: An Unexpected CEO Adventure.
- 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.
- Segal, I. ""When Is Zero Client Not Zero Client?", SysGen, Inc" (PDF).
- 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.
- 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.
- Chou, Timothy. Introduction to Cloud Computing: Business & Technology.
- Wang, R. "Tuesday's Tip: Understanding The Many Flavors of Cloud Computing and SaaS". Retrieved 2012-05-27.
- "Understanding the Flex Tenancy Architecture by CITRIX". Retrieved 2012-05-27.
- Greaves, J. (of Carpathia Hosting) and Potti, S. (of Citrix). Uploaded by CarpathiaHosting on Feb 22, 2010. "Flex-Tenancy: Secure Multi-Tenancy Network Environments". Retrieved 2012-05-27.