Transcript
Page 1: Moving your share point development to azure

Moving your SharePoint Development to Azure

Malin De SilvaSharePoint SpecialistExilesoft

[email protected]

Page 2: Moving your share point development to azure

About Me

• Experienced with SharePoint 2007/ 2010/ 2013

• Presenter at many meetups and conferences

• A BIG Azure fan.

Page 3: Moving your share point development to azure

Let’s Get to Know

SharePoint Developers?

Experienced with Azure?

Worked with Azure Virtual Machines?

SharePoint Development Experience on Azure?

Page 4: Moving your share point development to azure

Agenda

Introduction Planning infrastructure Azure VMs for SharePoint Capex vs Opex Cost saving tips Q and A

[email protected]

Page 5: Moving your share point development to azure

Running SharePoint on Azure

How much bandwidth required? Develop from ANYWHERE Can scale up easily/ quickly Resources are not idle when VMs are stopped No concerns on local storages Updates automatically if allowed Backup and restore mechanisms

Page 6: Moving your share point development to azure

Our Team 5 Members

Full Trust Solutions

1 SharePoint 2010 Development Environment

5 SharePoint 2013 Development Environments

1 QA Environment

Page 7: Moving your share point development to azure

Planning Infrastructure – Developer Machines

DeveloperDeveloper Developer Developer Developer

Page 8: Moving your share point development to azure

Planning Infrastructure – Developer Machines

developer1farmdeveloper1setupdeveloper2farmdeveloper2setup

….developermember1developerowner1developertestuser1

Developer

Developer

Developer

Developer

Developer

Page 9: Moving your share point development to azure

DemonstrationCreating a Network and a Virtual Machine

Page 10: Moving your share point development to azure

Planning Infrastructure – Test Environment

Same Domain Controller

Database Server for QA

SharePoint WFE

SharePoint App Server

Page 11: Moving your share point development to azure

Azure VMs for SharePoint A series – General Purpose

Basic: 300 IOPS Standard: 500 IOPS

D/ DS Series – SSD + 60% faster G Series – Larger RAMs

INSTANCE

CORES

RAM DISK SIZE

PRICE

A0 1 0.75 GB 20 GB $0.02/hrA1 1 1.75 GB 70 GB $0.09/hrA2 2 3.5 GB 135 GB $0.18/hrA3 4 7 GB 285 GB $0.36/hrA4 8 14 GB 605 GB $0.72/hrA5 2 14 GB 135 GB $0.33/hrA6 4 28 GB 285 GB $0.66/hrA7 8 56 GB 605 GB $1.32/hr

Page 12: Moving your share point development to azure

Capex vs OpexVirtual Machine

A1 (DC) A5 (Developer)

A6 (Database) A3 (QA)

No. of machines 1 5 1 3Cost per hour (USD)

0.09 0.33 * 5 = 1.65 0.66 0.36 * 3 = 1.08

Active hours per month

220 220 220 33

Annual Cost (USD)

237.6 4356 1742.4 427.7

Total Cost per Year (USD) 6763.7 ~ 6,040 EURAssumptions:

Each machine will stay started for 10 hours daily for 22 days a month. QA server will remain up every quarter for 10 days with 10 hours per day.We will keep creating full trust code through the year.

Page 13: Moving your share point development to azure

Cost Saving Tips Auto scaling or Automation

License mobility

Start with Windows Server installations

Page 14: Moving your share point development to azure

DemonstrationAuto scaling, Automating

Page 15: Moving your share point development to azure

Summary Potentials on cloud Better planning for VMs Cost estimations License mobility Auto scaling and automating

Page 16: Moving your share point development to azure

Questions?


Recommended