Skip to main content

A Guide to Cloud Computing

Interesting article.

Everyone agreed that cloud services such as Amazon Web Services, Google Apps, and Salesforce.com CRM have become bona fide enterprise options, but there were also questions about privacy, data security, industry standards, vendor lock-in, and high-performing apps that have yet to be vaporized as cloud services. (For a recap of that give and take, see "Customers Fire A Few Shots At Cloud Computing")

If we learned anything from our Enterprise 2.0 cloud forum, it's that IT departments need to know more. Our approach here is to look at cloud computing from the points of view of eight leading vendors. In doing so, we're leaving out dozens of companies that have a role to play, but what we lack in breadth, we hope to compensate for in depth.

And this analysis is just the beginning of expanded editorial coverage by InformationWeek on cloud computing. Visit our just-launched Cloud Computing blog on InformationWeek.com, and sign up for our new weekly newsletter, Cloud Computing Report. We're also developing video content, an in-depth InformationWeek Analytics report, and a live events series in the fall.

Full article here!

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op