by Ganesh Hegde (@xgt008) on Friday, 27 January 2017

+11
Vote on this proposal
Status: Submitted
Section
Full talk of 40 mins duration

Technical level
Intermediate

Media

Abstract

Modern startups need to focus on infrastructure optimization without compromising on performance, availability and redundancy to make sure they are efficiently capitalizing on their limited budgets. This talk aims to provide a brief rundown on this based on AWS infrastructure.

Outline

Premise

With infrastructure budgets being a critical component of modern web companies and most of the firms going cloud completely or partially, cost optimization with minimal production impact gains more importance than ever before.
The talk will explore:

  • Some less explored paths for cost savings on AWS without spending additionally
  • Case studies on problems faced when engineering for lower costs

Cost On Optimization on AWS : A practical guide

  • Cost is an afterthought. Shouldn’t be
  • Cloud cost overruns - 5 symptoms
  • Know your enemies
    • Know where exactly are you burning money
    • Using AWS Billing Dashboard to breakdown resource usage
    • Limitations of AWS instance types
  • Docker! Docker! Docker!
    • Impact of Dockerization on your budget
    • Using Docker to optimize resource usage of your hosts
  • Shift to Cheaper regions!
    • Deciding between Latency vs Cost for cheaper regions
    • Headaches to avoid when handling multiple regions
    • Benefits of using a denser region
  • Can you use Spot Fleet?
    • Deciding payloads that can be on Spot Fleet
    • Spot Fleet’s and their limitations
  • Leveraging your CDN to reduce your infra
    • Caching API responses to reduce your infrastructure load
    • Serving assets from S3 wherever possible
    • Caveats
  • Do you really need third party providers?
    • Deciding the right answer for third party cost optimization services
  • Test setup shouldn’t be burning a hole in your pocket
    • Do you really need HA in your test bed 24/7
    • “Production Parity in Test” Greatest fallacies of our generation
  • Reserved Instances Strategies
    • If all fails….

Case Studies

  • Leverage AWS Lambda
    • Use AWS Lambda to intelligently handle compute resources for random, asymmetric workloads using cloudwatch, SQS and boto3
  • Handling resources on non business hours
    • Save on your resources without tampering your developer’s peace of mind using Python, boto3 and Google Sheets API

Requirements

Intermediate to Advanced knowledge of AWS or equivalent concepts in GCP/Azure
Basic to Intermediate knowledge of Linux
Intermediate knowledge of SRE/DevOps concepts

Speaker bio

Senior Software Engineer at Urban Ladder

Comments

  • 1
    [-] Zainab Bawa (@zainabbawa) Reviewer 8 months ago

    This is a relevant proposal. Can we have more details such as draft slides for this proposal?

    • 1
      [-] Ganesh Hegde (@xgt008) Proposer 8 months ago

      Sure Zainab! Will do

    • 1
      [-] Ganesh Hegde (@xgt008) Proposer 8 months ago

      Zainab, have updated a bit more detailed draft slides for this proposal. Please take a look.

      • 1
        [-] Zainab Bawa (@zainabbawa) Reviewer 8 months ago

        Is this a recent update?

  • 1
    [-] saurabh hirani (@saurabh-hirani) 8 months ago

    This would be a good talk considering AWS cost optimizations is an ongoing pain point at every organization. It would be more useful if you could leave the audience with a good checklist that they can reuse.

  • 1
    [-] saurabh hirani (@saurabh-hirani) 7 months ago

    What can an audience member expect to learn what can’t be learnt from the usual AWS best practices docs and AWS Trusted advisor? For e.g. advice like shutting down instances when not using them is a no-brainer and sharing that isn’t going to add much value I guess.

    • 1
      [-] Ganesh Hegde (@xgt008) Proposer 7 months ago

      Saurabh,
      On the topic of shutting down instances, will be talking more about the details of how we handled shutting down instances and handling scaling down gracefully rather than going over the same known principles. Some of the details are already shared in brief in the draft slides. As you said, there is no point in repeating the same known best practice :)

      Even on the other potentially overlapping principle ( Spot Instances/Fleet), intend to talk more about what actually is the painpoint when using them rather than going over the mere principles.

      Rest of the talking points are either rarely touched upon IMO.

Login with Twitter or Google to leave a comment