- Clients (examples) are computer hardware and/or computer software which rely on The Cloud for application delivery, or which is specifically designed for delivery of cloud services, and which are in either case essentially useless without it.
- Services (examples) (aka Web Service) are "software system[s] designed to support interoperable machine-to-machine interaction over a network"[36] which may be accessed by other cloud computing components, software (eg Software plus services) or end users directly.
- Application (examples) leverages The Cloud in software architecture, often eliminating the need to install and run the application on the customer's own computer, thus alleviating the burden of software maintenance, ongoing operation, and support.
- Platform (examples) (aka Platform as a service) (the delivery of a computing platform and/or solution stack as a service) facilitates deployment of applications without the cost and complexity of buying and managing the underlying hardware and software layers
- Storage (examples) is the delivery of data storage as a service (including database-like services), often billed on a utility computing basis (eg per gigabyte per month)
- Infrastructure (examples) (aka Infrastructure as a service) is the delivery of computer infrastructure (typically a platform virtualization environment) as a service
Monday, September 29, 2008
The 6 layers of the Cloud Computing Stack
From Sam Johnston's Taxonomy post
Subscribe to:
Post Comments (Atom)
4 comments:
You don't mention where security fits in this stack. I know security is important at every level and it is there at every level now, but really there should be a single source of secure control of access to resources.
That's something big we need to work out. How can I have one account, the account I use to log into my cloud application and I can use that application with any other layer of stack or in combination with them without having to know that amazon requires these credentials and nirvanix requires another set.
The end user shouldn't care about these things, it should be handled at the platform level, but from my perspective there is no robust security model for the cloud, not yet.
Any ideas what we might see fill this gap?
Actually security is something that I do think about as a CISSP, but having looked at the various solutions it was clear that they permiated every layer of the stack. The resources themselves are secured by various mechanisms (AWS request signing for example) and from the user point of view you have OpenID and OAuth at the services layer. Even on the clients we don't want cloud apps interfering with each other and you can see that browsers like chrome go to great lengths to prevent this.
So yes it's a valid point, but not one that wasn't well considered.
Cheers,
Sam
This is an informative blog to everyone in which it would really helps to gain knowledge about this technology.
AWS Online Training
AWS Training in Hyderabad
Amazon Web Services Online Training
The blog post https://attractgroup.com/blog/overcoming-common-devops-challenges-in-implementing-devops-solutions-for-success/ on Attract Group provides valuable insights into the common challenges faced when implementing DevOps solutions. It effectively highlights key obstacles such as cultural resistance, integration issues, and the need for proper tooling. I particularly appreciated the emphasis on collaboration and continuous improvement as vital components for overcoming these hurdles. This comprehensive guide not only educates but also inspires teams to embrace DevOps for enhanced efficiency and success. A must-read for any organization looking to adopt DevOps practices!
Post a Comment