Cloud Components

3 components
  • Clients
  • Datacenter
  • Distributed servers

Comments

Post a Comment

Popular posts from this blog

Characteristics of Cloud Computing

Described as: On-demand computing, pay as you go, software as a service, utility computing Usually costs, but cost-effective Emphasizes availability Virtualization Scalable (expand on current hardware) Elastic (dynamically add hardware as needed by application/user) Distributed and highly parallel approach Replication, replication, replication. On-demand self service: Cloud computing resources can be provisioned on-demand by the users, without requiring interactions with the cloud service provider.   The process of provisioning resources is automated. Broad network access: Cloud computing resources can be accessed over the network using standard access mechanisms that provide platform-independent access through the use of heterogeneous client platforms such as workstations, laptops, tablets and smartphones. Resource pooling: The computing and storage resources provided by cloud service providers are pooled to serve multiple users using multi-tenancy. Multi-tenant aspects o
Read more

Logical Model

Image
At a high level, both cloud and traditional computing adhere to a logical model that helps identify different layers based on functionality. This is useful to illustrate the differences between the different computing models themselves: Infrastructure:  The core components of a computing system: compute, network, and storage. The foundation that every else is built on. The moving parts. Metastructure:  The protocols and mechanisms that provide the interface between the infrastructure layer and the other layers. The glue that ties the technologies and enables management and configuration. Infostructure:  The data and information. Content in a database, file storage, etc. Applistructure:  The applications deployed in the cloud and the underlying application services used to build them. For example, Platform as a Service features like message queues, artificial intelligence analysis, or notification services. Different security focuses map to the different logical layers. Ap
Read more

Platform as a Service

Image
Of all the service models,  PaaS  is the hardest to definitively characterize due to both the wide range of PaaS offerings and the many ways of building PaaS services. PaaS adds an additional layer of integration with application development frameworks, middleware capabilities, and functions such as databases, messaging, and queuing. These services allow developers to build applications on the platform with programming languages and tools that are supported by the stack. One option, frequently seen in the real world and illustrated in our model, is to build a platform on top of IaaS. A layer of integration and middleware is built on IaaS, then pooled together, orchestrated, and exposed to customers using APIs as PaaS. For example, a Database as a Service could be built by deploying modified database management system software on instances running in IaaS. The customer manages the database via API (and a web console) and accesses it either through the normal database network protoc
Read more