Friday, 11 January 2013

Cloud (summ)arise 2012!

2012 was a remarkable year for me in social media. I’ve gained more than 1 000 followers…without any follow back strategy. More than 10’ visitors on the blog and good traffic and sharing on GP’s around the web. Not bad for a rookie I think. Big THANK YOU to all readers, supporters and followers. I truly appreciate it. And by the way… what a remarkable year it was for Cloud Computing.

And by the way...what a remarkeable year it was for Cloud Computing. Who’s not impressed by true cloud…when it makes sense, fulfill needs and works like it’s supposed to?

This is my cloud, and a bit of IT Ooutsourcing and management, summary for 2012.
A collection of my authored favorites published on sites I write for. I hope I’ve taught some people and organizations about Cloud Computing, helped some to achieve cloud readiness, and inspired some to adopt one or more cloud services. I hope I’ve placed pressure on and triggered some Cloud Service Providers (CSP) to think one more time about how to facilitate customer cloud services adoption.

What we know:

  • Cloud = ?
    • Cloud = SaaS? True When implemented according to specific methods and rules.
    • Cloud = ASP? False ASP (Application Service Provider) is a model to deliver Software as a Service. Perhaps a predecessor, if you like, but it’s not Cloud Computing. If you put a “cloud” on your ASP service you’re cloudwashing.
    • ASP = SaaS? True ASP is Software as a Service. If by any rules connected to the Terminal Service methodology.
  • Cloud computing is a model to deliver IT services (or SaaS), regardless of whether it’s an IaaS, PaaS, SaaS or BPaaS. 
  • NIST defines Cloud Computing well
  • Outages do exist. They happen everywhere. Their minimization is one very important KPI (for the CSP). My POV: CSPs do this pretty well; otherwise they will soon be out of business.
  • All in doesn’t work. Some things should probably remain on-premises and/or at your Service Provider.

What we’ve learned: 

  • If you want to adopt a cloud service, you don’t want to be stuck in a washed one. One that locks you in, is not true to demand, is not easy measureable, etc. 
  • And to avoid confusion and accelerate adoption of you cloud service; try to speak the language consumers understand. Your future customer might not be familiar at all with all the nitty gritty terms the cloud market uses.
  • Lock-ins are devastating for customers, an “in-locking“ CSP and the Cloud market in general.
  • To not lock in is a successful lock-in.
  • Compliance is a tricky thing. You can choose which services and from whom to adopt. But you can’t choose which laws and regulations you have to follow, meaning you might have to change the branch and even the country you operate in. For more thoughts on this, read about Cloud compliance basics.
  • You want to take some time to update yourself about the security responsibilities (supported by Ron Peled, LivePerson) that you can demand from a CSP. And, of course, “on top” of your specific country and branch laws and regulations, you should familiarize yourself with any other common regulations that you or a CSP are obliged to follow. To support in IaaS adoption from the most frequent IaaS-providers these tables might help you.
  • If there’s any compliance problem adopting a cloud service hosted and delivered from a specific country or region, there’s probably a local or foreign compliant CSP available in the multiculti world of IT.
  • Should the CIO be the trusted advisor? IMHO; I don’t think so!
  • What do I think about 2013? I think the Cloud is dead! Long live the Cloud!
  • The commodity future is not bespoke. Bespoke is for special needs and occasions. Use add-ons instead of customizing.
  • The future will not sit down and wait on you. Wake up! You and your business otherwise might be doomed!
  • And hey…we complain a lot about complexity in cloud, ITO etc…there are some guys who handle extreme outsourcing pretty well. Maturity comes by experience, age and the ability to think twice. ITO and cloud have a lot to learn so let us all be patient and talk to each other in different projects.
  • And finally: Clicking Next>Next>Next should always be followed by actually reading the T&C/agreement, before you click Accept. Plan your cloud service adoption.

More stuff to think about:

  • It’s not easy to move apps to the cloud. It might not be compatible, “common sense” or the best approach at all. Adopt a service to replace the existing (old?) one – or adopt it because it gives you an opportunity to expand your portfolio and/or to achieve productivity and effectiveness.
    • Next version of your software might not be available to install on a client or server (independent if on-prem or as a IaaS/PaaS). It might only be available as a cloud service. Are you prepared to integrate it in your IT solution?
  • Adopt cloud services because it brings value to your business.
  • Cloud Computing will be part of your future hybrid IT solution… whether you like it or not. It’s IT – Future IT.
You can find most of my comments around the web and all posts I’ve published 2012 linked up or as originals here on In Max Mind.

2013 will be a great year for me, I’m sure.

2013 will be a great year for Cloud computing, I’m sure.

No comments:

Post a Comment