Killer scenarios for SharePoint 2010 and Azure - jeremy thake
Upcoming SlideShare
Loading in...5
×
 

Killer scenarios for SharePoint 2010 and Azure - jeremy thake

on

  • 2,868 views

Killer scenarios for SharePoint 2010 and Azure...

Killer scenarios for SharePoint 2010 and Azure
400 – Level
So you’ve been drinking the kool-aid on “the cloud” and have seen the buzz from Microsoft on both Office 365 and Azure in the last year. You may have even seen Steve Fox or Paul Stubbs, from Microsoft, content that has been published on the Internet of late focusing on leveraging Azure.
In this session, Jeremy Thake, will discuss where SharePoint and Azure makes sense. He will show you how to get started in your development environment and the bear traps to look out for. Some key scenarios will be demonstrated and the code walked through. Both SharePoint 2010 on-premise and SharePoint 2010 online scenarios will be demonstrated leveraging BCS, SQL Azure, Azure Service Bus and lots more.
 
From this session you should have
- a good understanding of how Azure could help your organization with your existing SharePoint 2010 environment and how to get started both on-premise and online.
- An understanding of the key concepts of how Azure could help your organization with your existing SharePoint 2010 environment
- An understanding of how to get started in your development environment with Azure and SharePoint 2010
- How BCS, SQL Azure and Azure Service Bus specifically can be leveraged in your organization by showing examples of the power of this technology in use

Statistics

Views

Total Views
2,868
Views on SlideShare
2,867
Embed Views
1

Actions

Likes
1
Downloads
20
Comments
1

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Killer scenarios for SharePoint 2010 and Azure400 – LevelSo you’ve been drinking the kool-aid on “the cloud” and have seen the buzz from Microsoft on both Office 365 and Azure in the last year. You may have even seen Steve Fox or Paul Stubbs, from Microsoft, content that has been published on the Internet of late focusing on leveraging Azure.In this session, Jeremy Thake, will discuss where SharePoint and Azure makes sense. He will show you how to get started in your development environment and the bear traps to look out for. Some key scenarios will be demonstrated and the code walked through. Both SharePoint 2010 on-premise and SharePoint 2010 online scenarios will be demonstrated leveraging BCS, SQL Azure, Azure Service Bus and lots more. From this session you should have - a good understanding of how Azure could help your organization with your existing SharePoint 2010 environment and how to get started both on-premise and online.- An understanding of the key concepts of how Azure could help your organization with your existing SharePoint 2010 environment- An understanding of how to get started in your development environment with Azure and SharePoint 2010- How BCS, SQL Azure and Azure Service Bus specifically can be leveraged in your organization by showing examples of the power of this technology in use
  • Windows Azure Application Model BenefitsWhen you deploy your application as a hosted service, Windows Azure creates one or more virtual machines (VMs) that contain your application’s code, and boots the VMs on physical machines residing in one of the Windows Azure data centers. As client requests to your hosted application enter the data center, a load balancer distributes these requests equally to the VMs. While your application is hosted in Windows Azure, it gets three key benefits:High availability. High availability means Windows Azure ensures that your application is running as much as possible and is able to respond to client requests. If your application terminates (due to an unhandled exception, for example), then Windows Azure will detect this, and it will automatically re-start your application. If the machine your application is running on experiences some kind of hardware failure, then Windows Azure will also detect this and automatically create a new VM on another working physical machine and run your code from there. NOTE: In order for your application to get Microsoft’s Service Level Agreement of 99.95% available, you must have at least two VMs running your application code. This allows one VM to process client requests while Windows Azure moves your code from a failed VM to a new, good VM.Scalability. Windows Azure lets you easily and dynamically change the number of VMs running your application code to handle the actual load being placed on your application. This allows you to adjust your application to the workload that your customers are placing on it while paying only for the VMs you need when you need them. When you want to change the number of VMs, Windows Azure responds within minutes making it possible to dynamically change the number of VMs running as often as desired.Manageability. Because Windows Azure is a Platform as a Service (PaaS) offering, it manages the infrastructure (the hardware itself, electricity, and networking) required to keep these machines running. Windows Azure also manages the platform, ensuring an up-to-date operating system with all the correct patches and security updates, as well as component updates such as the .NET Framework and Internet Information Server. Because all the VMs are running Windows Server 2008, Windows Azure provides additional features such as diagnostic monitoring, remote desktop support, firewalls, and certificate store configuration. All these features are provided at no extra cost. In fact, when you run your application in Windows Azure, the Windows Server 2008 operating system (OS) license is included. Since all of the VMs are running Windows Server 2008, any code that runs on Windows Server 2008 works just fine when running in Windows Azure.
  • Steve fox slide from AC presentation
  • COMPUTE: 750 hours of a Small Compute Instance* (can run one small instance full-time or other sizes at their equivalent ratios)STORAGE: 20GB with 50k Storage transactionsDATA TRANSFERS: 20GB outbound / Unlimited inbound data transferRELATIONAL DATABASE: 1GB Web Edition SQL Azure databaseACCESS CONTROL: 100k transactionsSERVICE BUS: Free through March 31, 2012CACHING: 128MB cache
  • Windows AzureCompute 1Extra small instance: $0.04 per hour 2Small instance (default): $0.12 per hourMedium instance: $0.24 per hourLarge instance: $0.48 per hourExtra large instance: $0.96 per hourStorage$0.14 per GB stored per month$0.01 per 10,000 storage transactionsContent Delivery Network (CDN)$0.12 per GB for data transfers under Zone 1$0.19 per GB for data transfers under Zone 2$0.01 per 10,000 transactionsVirtual Network 3Windows Azure Connect - No charge during CTPAccess Control 4$1.99 per 100,000 transactionsService Bus 5$0.10 per 100 relay hours$0.01 per 10,000 messagesCaching128 MB cache for $45.00256 MB cache for $55.00512 MB cache for $75.001 GB cache for $110.002 GB cache for $180.004 GB cache for $325.00SQL Azure 6Web Edition (up to 5 GB per database)$9.99 per 1 GB of database per monthBusiness Edition (up to 150 GB per database) 7$99.99 per 10 GB of database per month, with a maximum charge of $499.95 per databaseData Transfers 8Zone 1$0.12 per GB outZone 2$0.19 per GB outAll inbound data transfers are at no charge.
  • Quick overview of the development environment and tools (Azure and SharePoint 2010)Integration of ASP.NET application on Azure with SharePoint using IFRAMEUsing the Business Connectivity Services to integrate SQL Azure with a SharePoint external list (using SPD 2010).Leveraging the built-in security features in SharePoint to connect the separate username/password in Azure with that of SharePoint (using the Secure Store Service).Building custom services that you deploy in Azure and then integrate back into SharePoint through the BDC Metadata Model template in Visual Studio 2010 (that is the BCS).Integrating Silverlight with an Azure-connected external list using the SharePoint Client Object Model.http://cid-40a717fc7fcd7e40.office.live.com/browse.aspx/Azure%5E_TechEd
  • https://www.windowsazure.com/en-us/develop/net/tutorials/web-app-with-sql-azure/
  • http://blogs.msdn.com/b/brunoterkaly/archive/2011/11/17/how-to-consume-restful-services-using-jquery-and-or-javascript.aspx
  • ADFS2.0 in the cloud

Killer scenarios for SharePoint 2010 and Azure - jeremy thake Killer scenarios for SharePoint 2010 and Azure - jeremy thake Presentation Transcript

  • Killer scenarios for SharePoint 2010 and Azure Jeremy Thake Enterprise Architect jeremy.thake@avepoint.com jthake
  • Jeremy Thake
  • Agenda Key concepts Getting started Approaches Examples
  • Make It Rain!
  • On-premise IaaS PaaS SaaS Applications Data Runtime Middleware O/S Virtualization Servers Storage NetworkCredit: Professional SharePoint 2010 Cloud-based solutions
  • Benefits of Azure High availability Scalability Manageability
  • WAIT A MINUTE!
  • Why not just run on-premise IIS 7.5 / SQL Server  can host these things too! High availability of applications  Don’t worry about DR/HA costs Scalability of applications  Pay by usage rather than servers sitting cold Manageability of applications  Deployment of apps faster
  • Why do this? Offload heavy processing from SharePoint farm servers Transactional, normalized data processes Sandboxed solutions not as manageable SharePoint not great at “big data” Developers can stay in ASP.NET land & SP Dev can do “light touch” plumbing SharePoint becomes presentation layer to many applications
  • Flexible Pay as you go Scale out by changing in control panel
  • Key concepts
  • Components of Azure
  • “Free” trial COMPUTE: 750 hours of a Small Compute Instance STORAGE: 20GB with 50k Storage transactions DATA TRANSFERS: 20GB outbound / Unlimited inbound data transfer RELATIONAL DATABASE: 1GB Web Edition SQL Azure database ACCESS CONTROL: 100k transactions SERVICE BUS: Free through March 31, 2012 CACHING: 128MB cachehttps://www.windowsazure.com/en-us/offers/ms-azr-0018p
  • PAYG CostsCompute  Extra small instance: $0.04 $0.02 per hour  Small instance (default): $0.12 per hour  Medium instance: $0.24 per hour  Large instance: $0.48 per hour  Extra large instance: $0.96 per hourStorage  $0.14 $0.125 per GB stored per month  $0.01 per 10,000 storage transactions https://www.windowsazure.com/en-us/offers/ms-azr-0018p
  • PAYG CostsSQL Azure Web Edition (up to 5 GB per database)  $9.99 per 1 GB of database per month Business Edition (up to 150 GB per database)  $99.99 per 10 GB of database per month, with a maximum charge of $499.95 per database Data Transfers https://www.windowsazure.com/en-us/offers/ms-azr-0018p
  • Sample calculatorhttps://www.windowsazure.com/en-us/pricing/calculator/
  • Things to watch out for Identity Data security Regulation & policy Costs © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a
  • Getting started
  • Windows Azure SDK for .NET Comes with Visual Studio 2011 Developer Preview Web Platform Installer
  • ASP.NET MVC 3 Visual Studio 2010 SP1 or 2011 Dev Preview http://www.asp.net/mvc/mvc3 SSL Windows Azure application http://msdn.microsoft.com/en-us/gg271302
  • SharePoint Power Tools
  • Windows Azure accounthttps://www.windowsazure.com/
  • Windows Azure Platform
  • Account subscriptions
  • Billing Overview
  • Approaches
  • Approaches Simple Moderate Complex SharePoint hosted  Client side solutions  Imperative BCS (IFRAME) (CEWP) with JavaScript &  Consuming custom Azure- jQuery hosted services  BCS with SharePoint  Securing custom Azure- Designer 2010 hosted services with  Excel Services with Azure certificates  Azure Access Control Services  Pluggable workflow  Azure calling SharePoint via CSOM/REST/Web Services http://www.andrewconnell.com/blog/archive/2012/01/06/sharepoint-2010-windows-azure-integration- options.aspx
  • IFRAME approach
  • Hosted JavaScript to Azure SharePoint Online safe Client side  Debugging  No compilation  Browsers different  Speed of client machines  Shows IP
  • Azure DataMarket & Excel Services Powerful graphical data visuals Excel Services REST API Pivot Tables & Charts
  • BCS to SQL Azure Simple odbc connections Stronger normalized db structure External lists  Not full support of normal list
  • Azure Access Control Services Used for facebook, twitter, google Authentication mechanism
  • Azure calling SharePointCSOM / REST / Web services Hard coding authentication Consuming SharePoint in business apps
  • The Experts Microsoft’s Steve Fox http://blogs.msdn.com/b/steve_fox/ Microsoft’s Paul Stubbs http://blogs.msdn.com/b/pstubbs/ Microsoft’s Donovon Follette http://blogs.msdn.com/b/donovanf/ Critical Path’s Andrew Connell http://www.andrewconnell.com/blog tozit’s Tobias Zimmergren http://www.zimmergren.net Slalom’s Paul Galvin http://www.mstechblogs.com/paul/
  • BookSteve Fox Steve Fox, Paul Tom RizzoDeveloping Microsoft Stubbs, Girish Programming Microsoft’sSharePoint Applications Raja, Donovon Follette Clouds Azure and Office 365using Windows Azure SharePoint 2010 Cloud- Based Solutions
  • References SharePoint 2010 & Azure SharePoint + Azure training kit Windows Azure training kit Azure Developer Center Andrew Connell series Steve Fox’s series Tobias Zimmergren Chris Johnson’s series
  • Q&A Jeremy Thake www.NothingButSharePoint.com jeremy.thake@avepoint.com gplus.to/jthake @jthake www.linkedin.com/in/jeremythake
  • Gold Sponsors Silver SponsorsBronze Sponsors Media Sponsors