[ #yOS platform ] Workloads candidates for the Cloud

Since 2011 (see here my first post on this topic in French), I regularly publish an updated matrix of the different workloads that the yOS platform (yOS standing here for Yammer, Office 365 and SharePoint) can handle. For each workload, I then try to put a *relative* measure of the maturity of the workload, depending where it is executed. I analyze the following execution spaces :

  • SharePoint on-premises
  • SharePoint Online (in Office 365)
  • SharePoint on Microsoft Azure
  • SharePoint Hosted (outside Europe)
  • SharePoint Hosted (in Europe – as EU has special rules to handle especially personal data)

I also analyze the type of environments and where they can be best run :

  • Production
  • Performance tests
  • User acceptance tests
  • Development
  • Disaster Recovery

It is amazing to see how regularly the Cloud offerings are maturing and are gaining in credibility and interests.

So here is my updated matrix of SharePoint workloads candidates for the Cloud, as of November 2014 :

image

Please note that this a *relative* rating between each workload, and that it is not a definitive scoring. In specifics situations, some workloads can be more interesting than expected in the general case. How should it be understood ?

1. For Social, Intranet usages, SharePoint on-premises is no longer the good option to follow (at least without a third party add-on or event with one of them) because Microsoft is pushing hard customers to embrace Yammer. Microsoft has clearly publicly stated the no new features can be expected on-premises in this area. Even for customers willing to keep their SharePoint on-premises,  Microsoft has been pushing hybrid scenarios especially since SharePoint 2013 SP1.

2. For Collab and Documents management systems, SharePoint on-premises can still be a good choice however Office 365 provide a greater ease of deployment and management.

3. For storing sensitive data, it can still be an issue for some companies to have their docs stored in another country (even if it’s an European one – for memory European DC for Office 365  are in Dublin – Ireland and Amsterdam – the Netherlands). In this case, on-premises deployments can still be the best options. Hosted ones can also by an option.

4. In an Intranet context, My Sites deployments are a specific issue. Indeed, My Sites can be deployed on-prem or in the Cloud. Office 365 provides a very effective way to handle such a need. It provides the needed flexibility especially to deploy associated storage (OneDrive below). In this area, the main technical point to handle is to put in place a synchronization between on-premises Active Directory and Cloud Identities.

To put OneDrives in the Cloud has been a great option since SP2013 SP1 and the availability of increased space for each user. We are now in a world of unlimited space in the Cloud for OneDrive ushttp://blogs.office.com/2014/10/27/onedrive-now-unlimited-storage-office-365-subscribers/ers.

What users experience when redirected

5. As far as Publishing sites are concerned, Office 365 is gaining more and more attraction from the customers. However it is still lacking some important features we have on prem. We can expect new functionnalities in this area when what is called “next gen portals” (what Office 365 Video is presented as a first release) will be there .

6. As far as Search is concerned, Office 365 is gaining more and more attraction from the customers. However it is still lacking some important features we have on preis still lacking some functionnalities we have on-prem. For example, we still can’t yet force a crawling of all data in a tenant. But with the introduction of Delve (as a client tool) and Office graph as the underlying infrastructure, we can affirm that search on-prem will no longer be abalt to match online offering in terms of functionnalities.

7. Regarding BI solutions, the availability of Power BI made immediately all previous on-prem solutions out dated. It should be noticed here, that to be precise Power Bi is not a full Cloud solution but rather a hybrid one. Especially the Data Management Gateway in Power BI allows to share data stored internally, on-premises to all the end-users.

image

8. To access LOB applications from the Intranet, an on-premises Implementation of SharePoint is still the best option even if good tools are available here to handle such needs. I am thinking especially to BCS for SharePoint Online

image

9. To deploy a Video Portal, Office 365 is now with the availability of Office 365 video, the best option by far.

10. For any extranet Solutions, Office 365 is the easiest way to go with its universal sharing option.

11. To deploy an Internet site on SharePoint, an IaaS solution, especially on Microsoft Azure will be the most flexible solution. IaaS provides all features available in the on-premises SharePoint plus a great way to handle the elasticity needed by the workload.

 

As far as environments are concerned, I can propose the following table :

image

1. For Production the three options : On premises, Office 365 and Microsoft Azure are now viable options, dependning of your precise needs, with enough maturity.

2. For Performance testing, Office 365 can’t be used because you can’t replicate the exact workload you have on-premises for example.  Microsoft Azure can be a good option to deploy a temporary farm to do several sizing exercises.

3. For User Acceptance Testing environments, Microsoft Azure can be great because you usually don’t use the tests environments all the time. By shutting down your environment when it is not needed, you also cut the associated costs.

4. For development environments, IaaS solutions provides the versatility needed. You can very quickly instantiate a new environment or also shutdown the env. and cut the associated costs. Iaas is alos great for Apps deployment in the Cloud.

5. For Disaster Recovery, IaaS solution provides a very elegant (and cost optimal) way to solve a very common request : providing a backup solution in case of emergency. With the facts that the DR solution is almost never run and that it will therefore cost almost nothing once created (and regularly updated), we have an almost ideal solution.

 

Here are a quick overview of the whole choices we have to architect and deploy a Yammer-Office 365-SharePoint solution.

This blog post is also dedicated to my good friend Gokan (who asked me some clarification on these topics) and his great new blog located here : https://gokan365.wordpress.com/

 

UPDATED on 2014-12-01 to include Delve and Office Graph as a major improvement to Search for Office Online

Advertisements

5 thoughts on “[ #yOS platform ] Workloads candidates for the Cloud

  1. Reblogged this on El Blog del Programador and commented:
    Hola a todos, quiero compartir un interesante artículo que he leído en un blog que recomiendo encarecidamente. A mi me ha resultado interesante ver la propuesta de distintos escenarios que nos podemos plantear y que “Approach” podemos considerar en cada caso.

    Tanto o más interesante me ha resultado la matriz donde podemos ver los distintos entornos que nos pueden surgir y las posibilidades que nos ofrecen las distintas opciones (On premises, OnLine, IaaS) de que disponemos.

    Un saludo a todos

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s