aws re:invent 2016: busting the myth of vendor lock-in: how d2l embraced the lock and opened the...

Post on 11-Jan-2017

78 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

November 30, 2016

Busting the Myth of Vendor Lock-In

How D2L Embraced the Lock and Opened the Cage

ARC318

Ben Snively (AWS)

Stephen S. Skrzydlo and Stan Przychodzki

Stephen.Skrzydlo@D2L.com Stan.Przychodzki@D2L.com

What to Expect from the Session

AWS cloud

The Basics Amazon

EC2

Who’s afraid of

Amazon EC2?

Usage Curve

Usage Curve – Self-Hosting Provisioning

Usage Curve – Reserved InstancesAmazon

EC2

Why is no one afraid of EC2?

Virtualization already

paved that road

We’re not afraid of

what we’re used to

Amazon

EC2

D2L shops at the Content Store

Don’t forget the tax

Round 1: DFSR

• At least 2 windows

• Each with 12 TB of

• Cost curve looks familiar

• High minimum

• Step function

Amazon EBS

instances

$-

$5,000

$10,000

$15,000

$20,000

$25,000

$30,000

$35,000

$40,000

$45,000

$50,000

0

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

160

170

180

190

200

Month

ly C

ost

TB Storage

Round 2: NetApp ONTAP

• At least 2 ONTAP

• Each with 50 TB of

• Cost curve is better but…

• Still a step function!

Amazon EBS

instances

$-

$5,000

$10,000

$15,000

$20,000

$25,000

$30,000

$35,000

$40,000

$45,000

$50,000

0

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

160

170

180

190

200

Month

ly C

ost

TB Storage

Round 3: S3

• Standard storage

• Bye-bye step function

• But… that’s not a CIFS

share, we’d need to change

our product!

Amazon

S3

bucket

$-

$5,000

$10,000

$15,000

$20,000

$25,000

$30,000

$35,000

$40,000

$45,000

$50,000

0

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

160

170

180

190

Month

ly C

ost

TB Storage

The dreaded Vendor Lock-in

And here we see it, changing the code to handle S3

instead of CIFS shares. Think of the poor developers!

Yes, let’s think of them… Math time!

ROI = <Estimated Cost of Dev Effort>---------------------------------------------------------------------

(<OpExold> - <OpExnew>)

(Watch your units)

$-

$5,000

$10,000

$15,000

$20,000

$25,000

$30,000

$35,000

$40,000

$45,000

$50,000

0

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

160

170

180

190

Month

ly C

ost

TB Storage

Why not EFS?

Doesn’t meet our needs

Costs more

Amazon EFS

Don’t compete outside

your core competency

Amazon

Route 53

DNS and CachingAmazon

ElastiCache

DNS

“Transforming the way the

world learns”

Not: “implementing DNS”

Amazon

Route 53

$

Number of domains

DNS

“Transforming the way the

world learns”

Not: “implementing DNS”

Amazon

Route 53

$

Number of domains

Caching

“Transforming the way the

world learns”

Not: “re-implementing

Memcached”

Amazon

ElastiCache

$-

$1,000

$2,000

$3,000

$4,000

$5,000

$6,000

$7,000

$8,000

$9,000

Number of instances

Scaling and Opportunity Cost

If D2L were to have 1 DNS

specialist that would be like

Amazon having

Classic Build vs. Buy pattern

Better integration into the rest

of the ecosystem

Just superior feature sets

The Cloud is NOT a

Hosting Facility in the Sky

Logging ErrorsAmazon Kinesis

FirehoseAmazon

KinesisAmazon

Elasticsearch Service

SQL as a Logging Database – Legacy Design

• Unpleasant to search

• Only 30 days retained

• Hardcoded sharding

• Costly

50

100

150

200

250

300

350

400

450

500

550

600

650

700

750

800

850

900

950

100

0

$

TB

Kinesis Firehose -> Elasticsearch

(with S3)

• Designed for search

• 12 months retained

• Could retain more

• Sharding by choice

• Cheaper (~1/4th the cost) 50

100

150

200

250

300

350

400

450

500

550

600

650

700

750

800

850

900

950

100

0

$

TB

Amazon Kinesis

Firehose

Amazon

Elasticsearch Service

Amazon

S3

PaaS GOOD

IaaS BAD

Big Data LessonsAmazon

Redshift

Amazon

EMR

Original “Hosted” Design

• Pure self-roll

• Self-hosted

• Very high floor costs

• Concerns over multiregion

requirements

• IaaS$

Time

AWS “Lifted” Design – In Theory

• Pure self-roll

• AWS hosted

• Much better floor costs

• Concern over crossover

point

• IaaS$

Time

AWS “Lifted” Design – In Practice

• Self-roll

• AWS hosted

• Much better floor costs

• Concern over crossover

point

• IaaS$

Time

AWS Native Design

• AWS native

• AWS hosted

• Jump in with both feet

• Crossover point becomes

hilarious

• PaaS$

Time

Amazon

EMR

Amazon

Redshift

People

OPPORTUNITY

COST

“Understand motivations”

3rd Party Pushback

People

Recap

• Who’s afraid of EC2?

• Don’t forget to account for all costs

• Don’t compete outside your core competency

• The cloud is not a Hosting Facility in the Sky

• PaaS > IaaS

• This AWS thing might stick around for a bit

Integrating AWS with existing On-Prem Solutions

Integrated

networking

Integrated

access control

Integrated

storage and

backups

Integrated

Management

# 10.0.100.0

# 10.0.200.0

Microsoft Active

Directory,

OTKA,

Shib,

Etc..

App 1

AWS Storage Gateway

Integrating AWS with existing On-Prem Infrastructure

Amazon EFS

File

Amazon EBSAmazon EC2

Instance Store

Block

Amazon S3 Amazon Glacier

Object

Data Transfer

AWS Direct

Connect

AWS

Snowball

ISV Connectors Amazon

Kinesis

Firehose

S3 Transfer

Acceleration

AWS Storage

Gateway

Storage is a platform: AWS Storage Maturity

AWS Database

Migration Service

Start your first migration in 10 minutes or less

Keep your apps running during the migration

Replicate within, to, or from Amazon EC2 or Amazon RDS

Move data to the same or different database engineAWS Schema

Conversion Tool

AWS Application Discovery Service

Identify application

Inventory

Map application

dependencies

Baseline system and

process performance

Automate data center application discovery

AWS Server Migration Service

• Support VMWare VMs migration

• Agentless VM Migration

• Capture incremental changes

• Migrate a group of VMs

• Management Console/API Access

• Launch EC2 instances from AMIs

Thank you!

Ben Snively (AWS)snivelyb@amazon.com

Stephen S. Skrzydlo and Stan Przychodzki

Stephen.Skrzydlo@D2L.com Stan.Przychodzki@D2L.com

Remember to complete

your evaluations!

top related