IDG Contributor Network: Digital Ecosystems: Do Not Do It Alone!

As software becomes an increasingly large part of an enterprise’s external expression, traditional physical ecosystems—such as suppliers, resellers, and retailers—need to be supplemented, and in some cases supplanted, by new software ecosystems.

Consider Walgreens, a customer of my employer, Google. To interact with customers, Walgreens doesn’t merely operate physical stores and provide first-party apps and websites. On the contrary, it also expresses core services—such as filling prescriptions or ordering photo prints—as APIs. This enables developers and partners to easily integrate Walgreens services into their own products, which in turn enables Walgreens to extend its brand presence into ecosystems it neither owns nor had to build.

To read this article in full or to leave a comment, please click here

CIO Cloud Computing

Cloud backup: Don’t rely on your provider alone

You’ve moved data to the cloud. Now it’s time to talk about disaster recovery — how to build a resilient system that can recover from catastrophic failure.

Amazon Web Services, for example, says its S3 service “is designed to deliver flexibility, agility, geo-redundancy, and robust data protection.” To IT, that means the system is fault-tolerant, managing the resiliency needs for you. (“Geo-redundancy” means that, if a center goes down, another center in another part of the country or world will pick up the load. You should never miss a beat.)

If AWS and other public cloud providers include a certain amount of resiliency services, does that mean your data is safe? For the most part, it is. Public cloud providers take great pains to see that data is not lost — ever.

To read this article in full or to leave a comment, please click here

InfoWorld Cloud Computing