Livefyre Profile

Activity Stream

Yes, there are many variations possible on the aaS theme. But let's not confuses people more than needed... The three consumption models of cloud (IaaS, PaaS, SaaS) describe up until which layer of your cloud service is managed and from which layer the client is responsible. Intergration is and will become an even more important subject in cloud computing, connecting all cloud services in your IT landscape together into one whole. - It's not just a managed hypervisor/operating system, so it's more than IaaS - It's not offering a complete set of user functionality, so it's less than SaaS - It's a part of your application landscape, a resource, that needs further configuration, so it's PaaS To me it's just one of many managed services that PaaS will be able to offer, next to DevOps, workload deployment software, elastic scaling patterns, databases, applications like SAP etc.

2 years, 4 months ago on IPaaS: Integration Platform as a Service. Buzzword Or Has Real Substance?

Reply

Interesting article, it reads nice in your comparison to the human body. Content wise, basically you are describing common understandable processes and techniques in IT that also are needed for cloud environments: Governance of your entire IT environment, System Management across your cloud provider images and cloud brokerage.

 

On the tiers, let´s not make things more difficult than they are: I would propose 4 tiers. Each tier is a quadrant of mission critical yes/no and strategic yes/no:

Tier 1. Key -  Most critical

Tier 2. Mission critical

Tier 3. Strategic but not mission critical

Tier 4. Not strategic or mission critical

 

You first look at the requirements of your application and than decide which cloud solution fits these requirements best, price is not the only thing to look at. Also take security, resiliency and availability requirements into account.

 

On the whole mechanism described, that´s the elastic scaling that cloud providers are providing or should provide. Elastic scaling is scaling up/down horizontally based on the actual load on the servers. This remove the whole ´shuffle of resources´ you mention, which is even not realistic when you actually spread your tiered applications across multiple cloud provides.

 

And lastly, applications should be monitored on end-to-end response times to determine the user experience and not purely the load on the servers hosting the application.

2 years, 4 months ago on The Hypothermic Cloud Infrastructure: Maintaining the Blood Flow to Tier 1 & 2 Apps

Reply