AP 2022 Cloud use case

Editor's Notes

• #5: Types of cloud services: IaaS, PaaS, SaaS Most cloud computing services fall into three broad categories: infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (Saas). These are sometimes called the cloud computing stack, because they build on top of one another. Knowing what they are and how they’re different makes it easier to accomplish your business goals. Infrastructure-as-a-service (IaaS) The most basic category of cloud computing services. With IaaS, you rent IT infrastructure—servers and virtual machines (VMs), storage, networks, operating systems—from a cloud provider on a pay-as-you-go basis. Infrastructure as a service (IaaS) is an instant computing infrastructure, provisioned and managed over the Internet. Quickly scale up and down with demand, and pay only for what you use. IaaS helps you avoid the expense and complexity of buying and managing your own physical servers and other datacenter infrastructure. Each resource is offered as a separate service component, and you only need to rent a particular one for as long as you need it. The cloud computing service provider manages the infrastructure, while you purchase, install, configure, and manage your own software—operating systems, middleware, and applications. Platform as a service (PaaS) Platform-as-a-service (PaaS) refers to cloud computing services that supply an on-demand environment for developing, testing, delivering, and managing software applications. PaaS is designed to make it easier for developers to quickly create web or mobile apps, without worrying about setting up or managing the underlying infrastructure of servers, storage, network, and databases needed for development. Platform as a service (PaaS) is a complete development and deployment environment in the cloud, with resources that enable you to deliver everything from simple cloud-based apps to sophisticated, cloud-enabled enterprise applications. You purchase the resources you need from a cloud service provider on a pay-as-you-go basis and access them over a secure Internet connection. Like IaaS, PaaS includes infrastructure—servers, storage, and networking—but also middleware, development tools, business intelligence (BI) services, database management systems, and more. PaaS is designed to support the complete web application lifecycle: building, testing, deploying, managing, and updating. PaaS allows you to avoid the expense and complexity of buying and managing software licenses, the underlying application infrastructure and middleware or the development tools and other resources. You manage the applications and services you develop, and the cloud service provider typically manages everything else. Software as a service (SaaS) Software-as-a-service (SaaS) is a method for delivering software applications over the Internet, on demand and typically on a subscription basis. With SaaS, cloud providers host and manage the software application and underlying infrastructure, and handle any maintenance, like software upgrades and security patching. Users connect to the application over the Internet, usually with a web browser on their phone, tablet, or PC.. Software as a service (SaaS) allows users to connect to and use cloud-based apps over the Internet. Common examples are email, calendaring, and office tools (such as Microsoft Office 365). SaaS provides a complete software solution that you purchase on a pay-as-you-go basis from a cloud service provider. You rent the use of an app for your organization, and your users connect to it over the Internet, usually with a web browser. All of the underlying infrastructure, middleware, app software, and app data are located in the service provider’s data center. The service provider manages the hardware and software, and with the appropriate service agreement, will ensure the availability and the security of the app and your data as well. SaaS allows your organization to get quickly up and running with an app at minimal upfront cost.
• #6: “On-premise” datacenters Servers in basement Proper server rooms Proper server buildings 2006 AWS EC2 launch Compute as a service Large scale public cloud Today Hybrid cloud (on-premise with scale out capabilities in public cloud) Multi cloud (landscape across different public cloud providers) On-premise DC only in specific use cases (Low latency, air gapped systems, legacy…) Screenshot from https://www.youtube.com/watch?v=XZmGGAbHqa0
• #7: From https://blog.google/around-the-globe/google-europe/new-data-data-centers-how-google-helps-regions-grow/
• #8: https://dev.to/alex_barashkov/microservices-vs-monolith-architecture-4l1m
• #9: https://dev.to/alex_barashkov/microservices-vs-monolith-architecture-4l1m
• #10: https://gotocon.com/dl/goto-amsterdam-2016/slides/RuslanMeshenberg_MicroservicesAtNetflixScaleFirstPrinciplesTradeoffsLessonsLearned.pdf
• #11: Architectural changes Monoliths vs microservices Real time data processing (vs overnight batches) Increased complexity Load requirements Applications running for 10s to 100s of users at companies Applications running for literally millions of users Data processing requirements Speed of applications Slow is broken Pets vs cattle Due to sizing, not possible to manage all workloads anymore
• #12: Cost Total cost of ownership Google DC in Saint Ghislain -> 1,6 billion investment (not running cost) since 2007 VM 4 core, 16GB, 100GB SSD -> 1,000 euro per year Time to market Spinning up 1 VM in the cloud, 3 minutes of work Spinning up 1 server in a rack, 15 minutes -> months, with todays chip shortage -> year+ E.g. going from 0 to fully deploy landscape 90 minutes Levels of operational abstraction Managed storage Managed static web hosting Managed database Function as a service / Serverless
• #13: Flexibility Every morning developers start -> 60 VMs (32GB, 8 cores each) get started Every night -> 60 VMs are destroyed Saving 60% on cost (and less unused resources) Automation capabilities Infrastructure as code Automated scaling based on load Automated policy enforcement Security Large cloud providers have larger budgets to devote to this Best practises embedded in platform Auditiblity based on standards (ISO, HIPAA, NIST, IRS, …)
• #14: Source
• #15: Source
• #16: Source