DISQUS

Matt Topper · 5 months ago

Now that we can all standardize on the definition of "a cloud" we can start drilling down into the more important "X"aaS topics. This is my typical definition of Infrastructure as a Service. Now the models have to be expanded to support Platform and Software architectures. Whats important is provided an S3 type service to stage the information for deployment. People must understand that most applications won't just run in the cloud, they need to be architected in such a way that they can handle the dynamic growth and condensing of resources without user interruption.

They documents list "security" and "identity" at a high level as important issues. I'm disappointed that they don't list these as part of the foundation for the architecture. However doesn't go into depth as to how to provide IDaaS allowing identity attributes to be cascaded into role and then into policies for provisioning purposes. This concept is key to cloud success and in my opinion being one of the hardest problems to solve is not getting the attention it deserves. Everything from how to add new resources, to installing / managing the operating system to the platform on top of them to the end users/services attaching to the software needs to be addressed and each in their own unique way.

Azure which was mentioned in the powerpoint deck is only a partial solution to the problem (and one of many). These organizations have enough problems doing this internally, let alone when they introduce a federated identity model when sharing information, platforms and services between organizations.

ctovision · 5 months ago

Thanks Matt. I see your points about security and identity needing to be much higher in level as issues-- as foundational to the architecture. I appreciate all your comments.

Cheers,
Bob