PaaS and Time Compression in the Cloud


Recently I got to write a couple of articles which were posted on the Northwest Cadence Blog. I am not going to reproduce them here, so please read them on the NWCadence blog from the links below.


The first, PaaS Architecture: Designing Apps for the Cloud covers some of the considerations you’ll need to make if you’re porting your applications to the Cloud. Moving your website to a VM with IIS is technically “moving to the cloud”, but this is IaaS (infrastructure as a service) rather than PaaS (platform as a service). If you’re going to unlock true scale from the cloud, you’re going to have to move towards PaaS.

Unfortunately, you can’t simply push any site into PaaS, since you’ll need to consider where and how your data is stored, how your authentication is going to work, and most importantly, how your application will handle scale up – being spread over numerous servers simultaneously. The article deals with some these and other considerations you’ll need to make.

Time Compression

The second article, Compressing Time: A Competitive Advantage is written off the back of Joe Weinman’s excellent white paper Time for the Cloud. Weinman asserts that “moving to the cloud” is not a guarantee of success in and of itself – companies must strategically utilize the advantages cloud computing offers. While there are many cloud computing advantages, Weinman focuses on what he calls time compression – the cloud’s ability to speed time to market as well as time to scale. Again, I consider some of the implications you’ll need to be aware of when you’re moving applications to the cloud.

Happy cloud computing!