User:Doublec34/sandbox

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 (e.g. fat client, thin client, mobile device), a back end platforms (servers, storage), a cloud based delivery, and a network (e.g. Internet, Intranet, Intercloud). All of which combined makes up cloud computing architecture.

Cloud client platforms[edit]

Cloud computing architectures consist of front end platforms called clients or cloud clients. These clients are compromised of 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), a web browser, or through a virtual session.

The zero client[edit]

The zero or ultra-thin clients initializes the network to gather required configuration files that then tell it where their OS binaries are stored. [1] The entire zero client machine runs via the network; therefore, creating a single point of failure: the network. If the network goes down the machine is rendered useless.[2]

Cloud storage[edit]

A 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. [3]

In order to be effective, the cloud storage needs to be agile, flexible, scalable, multitenancy, and secure. [4]

Cloud based delivery[edit]

Software as a Service (SaaS)[edit]

Software as a Service (SaaS) is a service model where software is installed and maintain - by the cloud provider - in the cloud and a user runs the software from their cloud client over the Internet (or Intranet). Therefore, no software is installed on the client machine. It is all running from the server (in the cloud). SaaS is scalable and therefore the applications is loaded 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 SaaS the customer can access the application without installing the software locally on typically requires a monthly or annual fee. [5]

Software as a Service is the equivalent to installed applications in the traditional (non-cloud computing) delivery of applications.[6]

Software as a Service has four common approaches: single instance, multi instance, muti-tenant, and flex tenancy.[6] [7]

Development as a Service (DaaS)[edit]

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

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.[3] This is the equivalent to middleware in the traditional (non-cloud computing) delivery of application platforms and databases.[6]

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

Cloud networking[edit]

Generally, the cloud network layer should offer:

Allowing the users to have uninterrupted access 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-tency it becomes much more important because you're dealing with segregating multiple customers.[8]

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-10: 0-9563556-1-7.
  • Shroff, Dr. Gautam. Enterprise Cloud Computing: Technology, Architecture, Applications.

References[edit]

  1. ^ 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)
  2. ^ Segal, I. ""When Is Zero Client Not Zero Client?", SysGen, Inc" (PDF).
  3. ^ a b Mell, P. and Grance, T. (2011-09). "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. {{cite web}}: Check date values in: |date= (help)CS1 maint: multiple names: authors list (link)
  4. ^ Sherbak, T., Sweere, N., and Belapurkar, V. "Virtualized Enterprise Storage for Flexible, Scalable Private Clouds. Reprinted from Dell Power Solutions, 2012 Issue 1" (PDF). Retrieved 2012-05-27.{{cite web}}: CS1 maint: multiple names: authors list (link)
  5. ^ Chou, Timothy. Introduction to Cloud Computing: Business & Technology.
  6. ^ a b c d e Wang, R. "Tuesday's Tip: Understanding The Many Flavors of Cloud Computing and SaaS". Retrieved 2012-05-27.
  7. ^ "Understanding the Flex Tenancy Architecture by CITRIX". Retrieved 2012-05-27.
  8. ^ 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.{{cite web}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)