coud 3

Indian / Russian doll" nested relationship among IaaS, PaaS, SaaS

1. All SaaS and PaaS require an Infrastructure • This infrastructure could be IaaS or traditional. • However, a traditional infrastructure (vs. IaaS) would likely make the economics prohibitive. 2. A SaaS may or may not be built on a PaaS. • It depends on the development and deployment decisions of the SaaS. 3. Each of the 3 delivery models could come from the same or distinct providers. • This has service level, trust, and "chain of custody" implications for the end user

NIST Provides for 4 Deployment Models - All are commonly accepted, though they have different level of implementation adoption in market

1Private cloud. The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises. 2Community cloud. The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises. 3Public cloud. The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider. 4Hybrid cloud. The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds)

Hybrid cloud.

The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds)

Private cloud.

The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises.

Community cloud.

The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises.

Public cloud.

The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider. shared resources.

In deciding on cloud delivery for projects, various other implications and trade-offs must be considered - technical and business

Understand that building a cloud is not just a technology activity. The choices you make (above) must be congruent with business needs.

5 charcristic is not required

common charactis: virtulization security recovery(not required)

multitanent

many company shared resource

saas

ownership could be anybody

translation

technology---servies