Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Cloud Computing

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.

Cloud Computing

Class for Dauphine - Executive Master Statistics and Big Data

Avatar for Michael Bensoussan

Michael Bensoussan

February 23, 2026
Tweet

More Decks by Michael Bensoussan

Other Decks in Education

Transcript

  1. Agenda • Fundamentals • History of the cloud • Types

    of cloud services • What’s right for you? • Use case: Drivy • Hands-on: Heroku
  2. What is cloud computing? Cloud computing is a paradigm that

    allows on-demand network access to shared computing resources. A model for managing, storing & processing data online via the internet.
  3. Before 2000 Order your new machine Configure Go / send

    it to the datacenter Online Unboxing
  4. Elasticity Capacity of 1 server Traditional capacity required 1 server

    for 8 hours 3 servers for 8 hours 1 server for 8 hours ~45% saving
  5. • SLA not always on-par with on-premise. EC2 offers 99,99%

    after what you’ll have up to 30% of your bill reimbursed. 99,99% is ~1h of downtime per year. There is a few famous AWS outage like the 2012 Christmas eve power outage. No Netflix for Christmas for every american 😱 • Possible vendor lock-in. No standardizations on Cloud providers external interface meaning migration might be a pain. Some open-source solutions are emerging (see Terraform) • Performances not always on-par with on-premise. Hardware is shared amongst a number of other customers, to the point where multiple accounts will compete for resources from the same servers, network and storage. If an application on the shared hardware begins to grow in utilization of a specific resource, this might take resources away from other applications on that infrastructure (oftentimes from other customers). • Privacy and security not always on-par with on-premise. You’re relying on your cloud provider to secure your data and services. More abstractions means more limitations
  6. Hypervisor 🕵 Hypervisor Hardware App Kernel Virtual hardware Somebody else’s

    problem Applications, dependencies and OS Deps App Kernel Virtual hardware Deps App Kernel Virtual hardware Deps App Kernel Virtual hardware Deps App Kernel Virtual hardware Deps App Kernel Virtual hardware Deps
  7. Containers Hardware Somebody else’s problem Applications, dependencies and OS Kernel

    Container Engine App Deps App Deps App Deps App Deps App Deps App Deps App Deps App Deps
  8. • SLA not always on-par with virtualization. Still new-ish technology.

    • Performances not always on-par with virtualization. Containers are more performant than VM because there’s no virtual hardware but access to the real one. You could run hundreds of containers on a single host without a blink but there’s less isolation though. • Privacy and security not on-par with virtualization. Again, less isolation • No vendor lock-in. Containers technology is open-source and standardized 🎉 More abstractions means more limitations
  9. • Functions code needs to be small 50 Mo maximum.

    250MB for dependencies. 500MB for /tmp • Functions resource allocations needs to be small. Up to 1,5GB Memory, CPU is small • Execution time by function is limited. Up to 300s • Parallelization is limited. Up to 1000 parallel execution of the same function • Cold start. It takes some time for the Lambda function to handle a first request, because Lambda has to start a new instance of the function. One workaround is to send a request periodically to avoid the cold start and to make sure that there is always an active instance, ready to serve requests. • Vendor lock-in. No standardization yet. More abstractions means more limitations
  10. • Amazon Web Services Mostly IaaS at the beginning now

    doing everything; PaaS, SaaS, Serverless, CaaS, ... Tons of services with great interoperability. • Microsoft Azure Less services but focus on ease of use. Mostly PaaS and IaaS. • Google Cloud Less services but great performances More focus on Serverless and CaaS. • Heroku Ease of use: PaaS The big players
  11. IaaS: What you get? • Servers • Load balancers •

    Storage • Networking • Virtualization
  12. IaaS: Really ... all sizes This is 4TB of RAM!

    Who need HADOOP clusters when you can compute everything in memory? It also comes at $26/h, so around ~$20.000/m. The smaller server (1CPU / 512M ram) comes at ~$4/m.
  13. IaaS: Elastic Storage In AWS, Elastic Block Storage (EBS) are

    volumes with the following properties: • Can be mounted after instance is created on one or multiple instances • Have a guaranteed SLA of 99,99% • Can easily be backed-up • Storage size is elastic and can be resized dynamically • Can be encrypted • Can be replicated or migrated to other regions Very useful for storing important data and are the backbone of a lot of other services offer by Amazon.
  14. IaaS: Load balancers In AWS, Elastic Load Balancing (ELB) are

    load balancers with the following properties: • TCP or HTTP(s) • Auto Scaling of EC2 instances • Monitoring and auditing • Load balancing across AWS and on-premises
  15. You can create isolated networks with VPC (Virtual Private Cloud)

    and create secure and complex typologies: • Connect directly to the Internet (public subnets) You can launch instances into a publicly accessible subnet where they can send and receive traffic from the Internet. • Connect to the Internet using Network Address Translation (private subnets) Private subnets can be used for instances that you do not want to be directly addressable from the Internet. Instances in a private subnet can access the Internet without exposing their private IP address by routing their traffic through a Network Address Translation (NAT) gateway in a public subnet. • Connect securely to your corporate datacenter Through a VPN connection • Peer VPC together A lot of SaaS/Paas built on AWS offers you VPC peering to connect to their services without hitting the internet (local connection) • Connect to any other AWS services securely IaaS: Networking
  16. PaaS: Heroku; what you get? • Just push code, Heroku

    handles the OS, the HTTP routing • Scaling as simple as a slider • Auto Scaling based on response times • Easy deploy, easy rollback • Basic monitoring and alerting • Logging • Github Integration • Multiple native DB support: Redis, PostgreSQL, Kafka • Add-ons marketplace to easily integrate multiple SaaS (Data stores, monitoring, logging, messaging, caching, errors/exceptions, content management, user management, image/video processing, search, …) • Continuous delivery • Continuous integration
  17. PaaS: Heroku; deployment • Heroku CLI: deploy from a simple

    command line application • Github: Continuous delivery on github webhooks • Dropbox: Continuous delivery via dropbox • Container registry: Push your containers via the command line applications (CaaS)
  18. • Less control - more limitations Again, more abstractions means

    more limitations • Not cheap • More agility Focus on your product not on infrastructure • No DevOps PaaS: Summing up
  19. How much will cost supporting a website? • 1 small

    server (512MB/1CPU) can handle 200 rpm (request per minute) • 1 devops can handle 100 servers • 1 server cost $4 on AWS and $25 on Heroku • 1 devops cost $4000/m PS: This is completely hypothetical and does not completely reflect reality
  20. Twilio provides an easy API for handling Voice and SMS

    communications. • Sending an SMS is as easy as: • You can send SMS anywhere in the world • You can receive SMS • You can record calls • You can automatically convert text to speech • .... Twilio: Communication as a Service
  21. Amazon S3 is a storage service available over HTTP (or

    torrent). • Unmatched durability, availability and scability SLA of 99.999999999% of durability. So if you store 10,000 objects with Amazon S3, you can on average expect to incur a loss of a single object once every 10,000,000 years. • Number of files is unlimited. • Files need to be 5Tb each maximum. • There is a lot of features… you can run SQL queries on your data (See Amazon Athena or Amazon Spectrum - data lake built-in), lifecycle management, public/private files, can host html websites, supports versioning, support CORS, … • Is used by most companies. S3: Simple Storage Service
  22. Summing up On-Premise IaaS PaaS SaaS Applications Data Runtime O/S

    Virtualisation Servers Storage Network You manage Managed by vendor
  23. CaaS Open source is strong: • Kubernetes invented at Google

    • DC/OS / Mesos The concept of containers is Open-source: Docker The big cloud players created their own CaaS offer too.
  24. - Just ship code - A lot of focus on

    databases too both from Google (BigQuery) and AWS (Athena, Aurora, Lambda) - A lot of limitations today FaaS