Click here to close now.

Welcome!

MICROSERVICES Authors: Liz McMillan, Elizabeth White, Brian Vandegrift, XebiaLabs Blog, Andy Jonak

Related Topics: Cloud Expo, MICROSERVICES, .NET, Virtualization, Silverlight, Big Data Journal

Cloud Expo: Article

A Hybrid Computing Model for SharePoint

Seven critical success factors

For many companies, the business benefits that cloud computing promises are too compelling too ignore: improved agility, lower costs, better resource allocation, and fewer operational issues. As a result, organizations have been moving commodity infrastructure and services to cloud-based services managed by some of the world's leading technology companies - including Office 365, Microsoft's primary offering for business productivity in the cloud.

Several new developments are making Office 365 even more enticing:

  • New release of SharePoint: Extranets and public-facing websites are expensive in SharePoint 2010. However, with pricing changes and new web content management (WCM) functionality for SharePoint 2013, many organizations are beginning to take a second look at the cloud for some work streams as Office 365 gets updated in early 2013 with the latest SharePoint version.
  • Broad Office 365 adoption: According to Kurt DelBene, President of the Office Division at Microsoft, Office 365 is on target to become the fastest-selling server product in Microsoft's history, outpacing all analyst expectations.
  • Additional cost savings: With Office 365, organizations pay a monthly fee per user and gain access to ongoing maintenance and expertise to manage servers. That saves them from a huge, upfront operating expense. (We should point out, however, that because SharePoint Online is more of a product and service than a platform, it has more limited capabilities than the on-premises version, so long-term cost implications are not yet known.)

Given these gains, no company should ignore a move to the cloud. However, a full jump to the public cloud without careful consideration is ill advised. Some companies can't move everything to the cloud because they have compliance, regulatory, or government restrictions that limit where data can be stored and who can have access to it. But many companies shouldn't move everything to the cloud, because there is simply not parity between online and on-premise versions of SharePoint. What makes SharePoint compelling for many enterprises is the ability to extend, customize, and integrate with other enterprise systems, much of which is impossible with the Office 365 platform. Until there is parity, certain workstreams should stay in their current environments.

What's needed now is a thoughtful, strategic approach to cloud computing that is based on the needs of your business. Understanding which aspects of your organization's business systems can be moved, and should be moved, to the cloud is an important discussion that leaders must undertake. Although some work streams can be moved easily, many others require customization and management that only an on-premise deployment can support. That's why a hybrid model - comprising on-premise, private, and/or public cloud components - offers organizations the best way to ease into the cloud computing paradigm and leverage the promise of SharePoint Online.

Where to start? As part of readiness planning for cloud services adoption, companies must address seven critical success factors:

1. What are the business requirements?
As a first step, organizations must get their arms around the underlying business requirements of the environment, the key use cases, and the key work streams. For example, it may be possible to build out a lightweight customer relationship management solution, acting as a portal for sales, marketing, and support to connect with customers. But it may not make sense to move development team activities to the cloud due to integration issues with case management or configuration management systems. Outline your key workstreams, and then begin to map each workstream to your on-premise and online models to see which activities can be improved upon.

2. What are the business implications?
Companies must understand the implications of moving each use case and each work stream into the cloud. You must know the answers to these key questions: Can current functionality, security, audits, and reporting be replicated in the cloud? If key functions cannot be offered and supported, what are the risks? Say you have a ticketing system, with SharePoint acting as the front end. Without a full understanding of the architecture of the solution and how data is shared between the ticketing platform and SharePoint it may be difficult to understand the true cost implications of moving to the cloud. You also need an understanding of the performance and cost impacts to the large number of web service calls the platform may make within a pure cloud environment. Depending on the volume of data moved, how it is moved, and the timeframe for moving this important business system to the cloud, it may make financial sense to maintain an on-premise version of SharePoint for your product and support organizations.

3. What are the management ramifications?
Companies must understand the management implications of each work stream. It's not just a matter of "can we move it?" but "should we move it?" In some instances, a move to the cloud may result in added administrative effort and costs. Case in point: In one of the most common hybrid scenarios, a business that uses Office 365 as its extranet while maintaining an on-premise or dedicated cloud SharePoint environment may find that managing permissions, storage, and usage/activity is an extremely manual and time-consuming process. That's because there are no native tools for managing these functions across disparate SharePoint environments. Therefore, it's critical to look at your current metrics and KPIs for managing SharePoint, and understand the implications of duplicating these metrics within a new cloud environment - as well as combining and normalizing this data across all systems.

4. What about the end user experience?
We can't state this strongly enough: Companies must understand what the end-user experience will look like. If a hybrid environment adds effort or decreases productivity for end users, what is the cost? Consider these factors: Access to your enterprise platforms probably begins with a single sign-on experience - you log in once to get to all the tools and systems you need to do your business tasks. Your organization may have made significant investments to brand your internal platforms and put processes in place to maintain consistency across team sites and business unit portals. But, if you add another external system to the mix, what happens to the end-user experience? If permissions are separate, how does that affect end-user productivity? Your imperative is to understand how your primary users will conduct their business, thinking about the end-to-end experience, not just whether key functionality is being met through the new system. Remember: the more difficult a system is to use, the less likely people will be to use it.

5. How will we move?
If part of your organization, and key work streams, are moved to the cloud, what is the plan for the move? Will you move all at once? In waves? What about training? Migration and onboarding strategies vary widely. Your strategy should be based on critical path business use cases, helping those who rely on the new system before the masses. One strategy is to follow the 80/20 rule: concentrate your planning around the 20% of the users who use SharePoint most heavily, giving them 80% of your time, while spending 20% of your time with the remaining (mostly casual) users. However you decide to time moving end users and work streams, you must involve end users as you formulate and communicate your plan. The more you involve people in the process, the more likely they are to support that process.

6. How will we measure success?
Companies must have the right metrics in place to track performance across the entire environment. Companies also need to think about whether or not content needs to be synchronized between environments, or if these use cases can be maintained separately. Most companies fail at this today - because they don't have sufficient visibility into their SharePoint environment to generate and track adequate metrics. Moving to a hybrid model is a great opportunity to correct this trend. One strategy is to begin by identifying three key metrics across both systems, and build from there. An example might be Top 10 Most Active Sites, Top 10 Most Active Users, and Most Active Content Databases. Based on this data, you will gain a much better understanding of who is actually using SharePoint and where, allowing you to better allocate your time and resources to support the sites and users who are most active on the platform.

7. How will we enforce governance?
Ask yourself: Do we have a defined change management process? Do we have our roles and accountabilities defined? Are we actively reviewing and taking action on new requests? Are we giving end users and admins visibility into the changes being made and the priorities of those requirements? Having a governance body in place is crucial. Without automation, manual governance practices (policies, documentation, metrics) need to be extended or duplicated, with appropriate roles defined and assigned. Best practices include running through the document lifecycle across environments and identifying where current policies break. Focus your attention on the governance policies that manage risk - compliance, regulations, retention, or any other legal requirements of a hybrid system. Then define what it will take to maintain minimum security levels, and create a plan for automating and simplifying.

Despite the risks, some companies may be drawn into the cloud by the perceived cost savings, despite their customization or integration needs. This is a recipe for failure. Companies that successfully make the move to a hybrid model are those that understand the business activities that can be offloaded to the cloud, benefiting from its scale and cost benefits.

The beauty of a strategic, hybrid model is that it's not "all or nothing." By addressing the seven critical success factors outlined above, companies will be taking a holistic approach versus making a blind technology decision. By focusing on specific workstreams, and only building out those workstreams that can be supported, your company will end up with a strategic, hybrid model that supports the needs of your business.

For more information:

More Stories By Christian Buckley

Christian Buckley serves as Director of Product Evangelism at Axceler. He is a Microsoft SharePoint MVP and an internationally recognized expert on collaboration platforms, social informatics, business analysis, and project management topics. As Axceler's evangelist, he drives product awareness, partner advocacy, and community development. He previously worked at Microsoft as part of the enterprise hosted SharePoint platform team (now part of Office365).

Prior to Microsoft, Christian was managing director of a regional consulting firm in the San Francisco East Bay, co-founded and sold two technology startups, and worked with some of the world’s largest hi-tech and manufacturing companies to build and deploy collaboration and supply chain solutions.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
OmniTI has expanded its services to help customers automate their processes to deliver high quality applications to market faster. Consistent with its focus on IT agility and quality, OmniTI operates under DevOps principles, exploring the flow of value through the IT delivery process, identifying opportunities to eliminate waste, realign misaligned incentives, and open bottlenecks. OmniTI takes a unique, value-centric approach by plotting each opportunity in an effort-payoff quadrant, then work...
SYS-CON Events announced today that MangoApps will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY., and the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. MangoApps provides private all-in-one social intranets allowing workers to securely collaborate from anywhere in the world and from any device. Social, mobile, and eas...
SYS-CON Events announced today that Solgenia will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY, and the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Solgenia is the global market leader in Cloud Collaboration and Cloud Infrastructure software solutions. Designed to “Bridge the Gap” between Personal and Professional S...
When it comes to microservices there are myths and uncertainty about the journey ahead. Deploying a “Hello World” app on Docker is a long way from making microservices work in real enterprises with large applications, complex environments and existing organizational structures. February 19, 2015 10:00am PT / 1:00pm ET → 45 Minutes Join our four experts: Special host Gene Kim, Gary Gruver, Randy Shoup and XebiaLabs’ Andrew Phillips as they explore the realities of microservices in today’s IT worl...
This month I want to revisit supporting infrastructure and datacenter environments. I have touched (some would say rant) upon this topic since my post in April 2014 called "Take a Holistic View of Support". My thoughts and views on this topic have not changed at all: it's critical for any organization to have a holistic, comprehensive strategy and view of how they support their IT infrastructure and datacenter environments. In fact, I believe it's even more critical today then it was a year ago ...
The world's leading Cloud event, Cloud Expo has launched Microservices Journal on the SYS-CON.com portal, featuring over 19,000 original articles, news stories, features, and blog entries. DevOps Journal is focused on this critical enterprise IT topic in the world of cloud computing. Microservices Journal offers top articles, news stories, and blog posts from the world's well-known experts and guarantees better exposure for its authors than any other publication. Follow new article posts on T...
Hosted PaaS providers have given independent developers and startups huge advantages in efficiency and reduced time-to-market over their more process-bound counterparts in enterprises. Software frameworks are now available that allow enterprise IT departments to provide these same advantages for developers in their own organization. In his workshop session at DevOps Summit, Troy Topnik, ActiveState’s Technical Product Manager, will show how on-prem or cloud-hosted Private PaaS can enable organ...
Cloud computing is changing the way we look at IT costs, according to industry experts on a recent Cloud Luminary Fireside Chat panel discussion. Enterprise IT, traditionally viewed as a cost center, now plays a central role in the delivery of software-driven goods and services. Therefore, companies need to understand their cloud utilization and resulting costs in order to ensure profitability on their business offerings. Led by Bernard Golden, this fireside chat offers valuable insights on ho...
Microservice architectures are the new hotness, even though they aren't really all that different (in principle) from the paradigm described by SOA (which is dead, or not dead, depending on whom you ask). One of the things this decompositional approach to application architecture does is encourage developers and operations (some might even say DevOps) to re-evaluate scaling strategies. In particular, the notion is forwarded that an application should be built to scale and then infrastructure sho...
SYS-CON Events announced today the IoT Bootcamp – Jumpstart Your IoT Strategy, being held June 9–10, 2015, in conjunction with 16th Cloud Expo and Internet of @ThingsExpo at the Javits Center in New York City. This is your chance to jumpstart your IoT strategy. Combined with real-world scenarios and use cases, the IoT Bootcamp is not just based on presentations but includes hands-on demos and walkthroughs. We will introduce you to a variety of Do-It-Yourself IoT platforms including Arduino, Ras...
It's 2:15pm on a Friday, and I'm sitting in the keynote hall at PyCon 2013 fidgeting through a succession of lightning talks that have very little relevance to my life. Topics like "Python code coverage techniques" (ho-hum) and "Controlling Christmas lights with Python” (yawn - I wonder if there's anything new on Hacker News)...when Solomon Hykes takes the stage, unveils Docker, and the world shifts. If you haven't seen it yet, you should watch the video of Solomon's Pycon The Future of Linux C...
Even though it’s now Microservices Journal, long-time fans of SOA World Magazine can take comfort in the fact that the URL – soa.sys-con.com – remains unchanged. And that’s no mistake, as microservices are really nothing more than a new and improved take on the Service-Oriented Architecture (SOA) best practices we struggled to hammer out over the last decade. Skeptics, however, might say that this change is nothing more than an exercise in buzzword-hopping. SOA is passé, and now that people are ...
Microservices are the result of decomposing applications. That may sound a lot like SOA, but SOA was based on an object-oriented (noun) premise; that is, services were built around an object - like a customer - with all the necessary operations (functions) that go along with it. SOA was also founded on a variety of standards (most of them coming out of OASIS) like SOAP, WSDL, XML and UDDI. Microservices have no standards (at least none deriving from a standards body or organization) and can be b...
Right off the bat, Newman advises that we should "think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile Software development". These analogies are very interesting because my expectation was that microservices is a pattern. So I might infer that microservices is a set of process techniques as opposed to an architectural approach. Yet in the book, Newman clearly includes some elements of concept model and architecture as well as p...
You hear the terms “subscription economy” and “subscription commerce” all the time. And with good reason. Subscription-based monetization is transforming business as we know it. But what about usage? Where’s the “consumption economy”? Turns out, it’s all around us. When most people think of usage-based billing, the example that probably comes to mind first is metered public utilities — water, gas and electric. Phone services, especially mobile, might come next. Then maybe taxis. And that’s ab...
SYS-CON Events announced today the DevOps Foundation Certification Course, being held June ?, 2015, in conjunction with DevOps Summit and 16th Cloud Expo at the Javits Center in New York City, NY. This sixteen (16) hour course provides an introduction to DevOps – the cultural and professional movement that stresses communication, collaboration, integration and automation in order to improve the flow of work between software developers and IT operations professionals. Improved workflows will res...
As a group of concepts, DevOps has converged on several prominent themes including continuous software delivery, automation, and configuration management (CM). These integral pieces often form the pillars of an organization’s DevOps efforts, even as other bigger pieces like overarching best practices and guidelines are still being tried and tested. Being that DevOps is a relatively new paradigm - movement - methodology - [insert your own label here], standards around it have yet to be codified a...
Microservices, for the uninitiated, are essentially the decomposition of applications into multiple services. This decomposition is often based on functional lines, with related functions being grouped together into a service. While this may sound a like SOA, it really isn't, especially given that SOA was an object-centered methodology that focused on creating services around "nouns" like customer and product. Microservices, while certainly capable of being noun-based, are just as likely to be v...
Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities. Accordingly, attendees at the upcoming 16th Cloud Expo at the Javits Center in New York June 9-11 will find fresh new content in a new track called PaaS | Containers & Microservices Containers are not being considered for the first time by the cloud community, but a current era of re-consideration has pushed them to the top of the cloud agenda. With the launch ...
An explosive combination of technology trends will be where ‘microservices’ and the IoT Internet of Things intersect, a concept we can describe by comparing it with a previous theme, the ‘X Internet.' The idea of using small self-contained application components has been popular since XML Web services began and a distributed computing future of smart fridges and kettles was imagined long back in the early Internet years.