Claranet from on-premise to serverlessAWS Summit 2018

• Why are we here today? • Why should you listen to my talk in the first place? • What will I be talking about?

Motivation

About Claranet Group• Founded in 1996 • Private business – owner managed• Pro forma revenues of £310 million (€360 million)• Operations in 8 countries. 1,800 staff in 24 offices• £215m annualised revenues • Over 6,500 customers• 43 data centres• Comprehensive service portfolio:

Hosting, Communications, Networks & Security• Leader in Gartner MQ for Cloud enabled

Managed Hosting (2013, 2014, 2015, 2016, 2017)• Listed in Gartner Worldwide Public Cloud

managed Service Providers (2017)

Accreditations

Leader 2013, 2014, 2015, 2016 und 2017 Managed Hybrid Cloud Hosting, Europa 2017

Accreditations

Public Cloud Partner

ISO27001:201327018:2014

ISO22301:2012

Gartner Magic Quadrant

Customer case

• Company in the stock media market with 2PB of data• All data are compressed media files deduplication can’t be used• Application is a monolith architecture based on VMs on on-premise DC• Overprovisioning must be minimized• Core application is not fully high available• Minimize administrative effort• Image editing and thumbnail generating needs many resources

Customer Challenge

From on-premise to EC2

• Storage gateway for data transfer to S3 (NFS) over VPN• Spot request with several generations and types

- Requested: C-3,4,5 / R-3,4 / M-3,4,5• Combination of reserved and spot instances to increase availability• Combination of reserved and spot instances minimizes the costs• Minimal development effort for the customer

(EC2-based Architecture)

Implementation / Architecture based on EC2 / Spot Instances

• Pros- Minimize cost- Availability over 3 AZs- Easy implementation- Good performance

• Cons- Difficult cost estimation (only upper limits) - effort to adapt monitoring- additional admin effort- Storage Gateway is a single point of failure

Architecture Pros & Cons

Going to serverless

• Transfer of images to S3 via http (customer effort)• Using S3 Events for Lambda calls• Using the image processing code direct in Lambda• AWS SQS for error handling of not processable images• Monitoring via CloudWatch

Implementation / Architecture based on serverless / AWS Lambda

• Pros- Easy to implement- No OS administration- Highly scalable- Easy to monitor- Never pay for idle time

• Cons- Needs longer testing period for optimisation of

implementation- Performance improvement or cost reductions

can only be done by the development team

Lambda Pros & Cons

• Languages will have an effect to the cold start time- C# and Java = Slow- Node.js and Python = Fast

• Increase the memory will increase the cold start time- Increases nearly linear

Start your engine (Lambda Cold Start)

128 MB 265 MB 512 MB 1024 MB

Cold Start

Python / Node.js C# / Java

• generating more than one thumbnail per Lambda call saves time- Loading one image per call takes time- Loading several images in one call minimize the time to generate a thumbnail- To many Images per call will also slow down the call- Find the sweetspot to minimize the costs

Improve Lambda code

0123456789

10

1image

5images

10images

15images

20images

25images

30images

35images

40images

Thumbnail generation

Thank you!

Mickael ZewdeSenior Business Development Manager

E-Mail: mickael.zewde@de.clara.net