Created by W.Langdon from gp-bibliography.bib Revision:1.8081
Amazon web services: you have to pay for that, internal cloud networking costs. SAP. duckbillgroup.com, stackoverflow monolithic application, blog post.
IaaS Infrastructure as a Service: compute, storage and networking. PaaS Platform as a Service. SaaS Software as a Service (just applications that are hosted in the cloud).
AWS lambda: pay only when used. Use lock-in, that is how they make money.
Google Cloud: configure by web user interface. Terraform: file based configuration (ideal for GI to optimise?) GitOps: ArgoCD push IaC file, automatically updates your cloud configuration Mitigation (guard rails, prevent doing something really stupid) Infracost. AWS power tuning (optimisation). OpenCost (eg Microsoft).
Infrastructure-from-Code IfC api.cost. puppet. Serverless, eg JSON. Evolution of workload. SAP database. (so far) little work in software engineering research. Some in cloud research computing, eg Google cloud v. Apache Finc (IC2E 2022)
Future: mining GitHub. Takeaways 41:00 shifted left, always about tradeoffs 43:00 Q&A.
Myra B Cohen.
Need to simplify to start research. Light weight search.
Bradley Alexander, spot instances. Handle interruptions Amazon EC2. Easier to model spot prices? Hyper-scalars Very complex. You pay for everything.
Erik Frederics, offline testing, test out before actually run on the cloud.
Serverless. Estimate cost before actually running. How frequently do prices. Scrape prices from the internet www web.
Monolithic. SAP. Importance of stable compute platform. micro-services not a solution in themselves. Latency, no easy solutions.",
Genetic Programming entries for Sebastian Baltes