A case in point is Pro Bono Net, a national nonprofit organization dedicated to increasing access to justice through innovative uses of technology and increased volunteer lawyer participation. The organization meets this mission, among other ways, through its Pro Bono Manager™ service, which boosts a law firm’s pro bono program management capacity. Operating as a secure, seamless extension of a law firm’s intranet, Pro Bono Manager integrates content from the public-interest legal community with reporting, knowledge management, and lawyer-and-case matching tools that draw on a firm’s own human resources and time keeping systems.
Pro Bono Manager is a web-based, or software-as-a-service, solution—and the low-cost and minimal management required by the law firms that adopt it has been one of its selling points. But the cloud that hosted the service was a very physical set of servers owned and managed by Pro Bono Net. When those servers reached end-of-life, Pro Bono Net faced the same choice that their customers had answered by choosing Pro Bono Manager: Should Pro Bono Net refresh its hardware installation, or migrate Pro Bono Manager to a cloud platform?
The organization had to consider the economics of its choices, as any enterprise would. But, as a service provider to others, it had additional considerations: Would a move to the cloud affect the prices, availability, reliability, and speed that Pro Bono Net offered its customers and, if so, how?
One reason: Windows Azure was built from the ground up to support the same Microsoft technologies—Microsoft SharePoint Server, Microsoft SQL Server Reporting Services (in the cloud: Windows Azure SQL Reporting), and the Microsoft .NET Framework—that Pro Bono Net already used. Another reason: Microsoft offered Windows Azure Virtual Machines, which provided the flexibility and availability that comes from the use of virtualization technology.
Pro Bono Net used Windows Azure Virtual Machines for persistent virtualization in support of SharePoint Server, which serves as the foundation for Pro Bono Manager. If the organization had been moving between more consistent platforms—say, two virtual platforms, one managed on-premises and one in the cloud—it would have been easier to estimate cost. Going from a physical/on-premises platform to a virtual/cloud platform required some experimentation in preproduction environments, which the organization and Microsoft completed successfully.
Pro Bono Net eventually decided on a high-availability infrastructure that replicated domain controllers, front ends, application servers, and Windows Azure SQL Database instances on virtual machines. It also adopted Windows Azure availability sets to further mitigate risk and promote reliability. And as its use of Windows Azure grows, the organization expects to adopt geo-colocation features that will further increase fault tolerance and business continuity.
For its specific configuration on Windows Azure, Pro Bono Net spends $11,000 annually—and saves 79 percent over comparable cost for an on-premises infrastructure and support, after a 1.4-year payback period.
Pro Bono Net now pays less to support Pro Bono Manager while gaining more, particularly more reliability. Since the move to Windows
Azure, uptime for the application has increased from 99 percent to 99.9 percent. “That’s a significant increase for us,” says Alec Rosin, Consulting Engineer for Pro Bono Net. “On-premises, if we had a disaster, we could be out for a week. We don’t anticipate that happening on Windows Azure.”
Pages and reports now load about 20 percent faster on Windows Azure, creating a more natural user experience.
Chat with an expert about your business’s technology needs.