White Paper: An Essential Guide to Possibilities and Risks of Cloud Computing

Cloud Computing is quite possibly the hottest, most discussed and often misunderstood concept in Information Technology (IT) today.

In short, Cloud Computing proposes to transform the way IT it’s deployed and managed, promising reduced implementation, maintenance costs and complexity, while accelerating innovation, providing faster timeto-market, and the ability to scale high-performance applications and infrastructures on demand.

But business managers know that in spite of the benefits of every new technology/business model there are also risks and issues (like for example: trust, loss of privacy, regulatory violation, data replication, coherency and erosion of integrity, application sprawl and dependencies, etc.) and that rushing things when it comes to Cloud Computing can be a very bad decision, but blowing off Cloud Computing all together because you think you can secure your own stuff better than a service provider or because many claims, made about Cloud Computing, have lead you to the point of “irrational exuberance” and unrealistic expectations, isn’t smart, either .

The goal of this White Paper is to provide a realistic perspective of the possibilities, benefits and risks of Cloud Computing; what to look for, what to avoid, and also some tips and best practices on implementation, architecture and vendor management strategies. It is important to consider all those aspects before you decide either to move (but without putting the carriage before the horse) or not to move your systems, applications, and/or data to to the “Cloud”, in a “hype free” approach.

Click here to download the White Paper (or click on the image at left side)

Thanks and please let me know how I can help you.

P.S. And of course your comments, feedback’s and thoughts are always welcome.

Is this Cloud thing something new?

For my first post here I going to answer this question (sort of):

To be honest I was skeptical about Cloud Computing:
Having seen in that in the past some acronyms and hypes showing up I think its natural.
One of them was Ajax. Ajax is just creating one word to sum a bunch of technologies: (X)HTML + DOM + CSS + Javascript. Don’t get me wrong, I think that we need the acronyms, they are useful for communication but they don’t necessary add anything new.

One other acronym that I found interesting was ASP (Application Service Provider). ASP at first seemed to me just a way to say that we would sell our same desktop applications as a service. It was not a new technology, a new application or a new standard but just a new revenue model. Was this a small change? At first I thought so, but then I realized that this was a shift from the normal way of doing things and that opened the door for new companies that started building applications from scratch for the internet.
At that time someone (don’t remember who) called this new companies ASP2. This acronym had a short life (thankfully!) and the term Software as a Service (and the acronym SaaS) appeared.

Affer SaaS, other related acronyms started to pop up: SaaS, HaaS, PaaS, etc. and for me personally I need to figure out if they are bringing something new. In the future I will write something about them.

Right now I’m interest in writing about Could Computing. So what is it? Is just a new name?
For me Could Computing is more than just a new name, its again an interesting shift from the normal way we currently developed and sell software. This new term is not just the sum of several technologies but a change of paradigm that brings a lot of questions with it: What new applications will it bring? What new revenue models will appear? How will developers use it and how will they adapt? Will customers see any benefits? Who will be the big players in this field?

Bellow you can see some links that show some useful information about the Cloud:
- Demystifying Cloud Computing (sent by Paulo)
-
- viagra gel