Cloud computing: Difference between revisions

Content deleted Content added
removed content from unreliable sources. Some info were just wrong. Overhauled the section and explained some nuances
No edit summary
Line 19:
* '''Measured service:''' "Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
By 2023, the [[International Organization for Standardization]] (ISO) had expanded and refined the list. <ref name=":1" />
 
'''[[Cloud computing architecture|Cloud architecture]]''' is the structured design of cloud environments, encompassing components like networks, servers, storage, databases, and software, arranged to deliver scalable, reliable, secure, and cost-efficient cloud services. It defines how these components interact and integrate to meet specific business and technical requirements. [[Cloud engineering]] is the application of engineering principles and practices to design, develop, deploy, and manage cloud computing systems and infrastructure, ensuring scalability, security, reliability, and cost efficiency through automation, monitoring, and optimization.
 
==History==
Line 227 ⟶ 229:
====HPC====
HPC cloud refers to the use of cloud computing services and infrastructure to execute [[high-performance computing]] (HPC) applications.<ref>{{cite journal|last=Netto|first=M. |author2=Calheiros, R. |author3=Rodrigues, E. |author4=Cunha, R. |author5=Buyya, R. |s2cid=3604131 |title=HPC Cloud for Scientific and Business Applications: Taxonomy, Vision, and Research Challenges|journal=ACM Computing Surveys|volume=51|issue=1|pages=8:1–8:29|doi=10.1145/3150224|year=2018|arxiv=1710.08731 }}</ref> These applications consume a considerable amount of computing power and memory and are traditionally executed on [[Computer cluster|clusters]] of computers. In 2016 a handful of companies, including R-HPC, [[Amazon Web Services]], [[Univa]], [[Silicon Graphics International]], Sabalcore, Gomput, and Penguin Computing offered a high-performance computing cloud. The Penguin On Demand (POD) cloud was one of the first non-virtualized remote HPC services offered on a [[Prepayment for service|pay-as-you-go]] basis.<ref>{{cite web|last1=Eadline|first1=Douglas|title=Moving HPC to the Cloud|url=http://www.admin-magazine.com/HPC/Articles/Moving-HPC-to-the-Cloud|website=Admin Magazine|access-date=30 March 2019|archive-date=30 March 2019|archive-url=https://web.archive.org/web/20190330200839/http://www.admin-magazine.com/HPC/Articles/Moving-HPC-to-the-Cloud|url-status=live}}</ref><ref>{{cite web|url=https://pod.penguincomputing.com/|title=Penguin Computing On Demand (POD)|access-date=23 January 2018|archive-date=9 March 2018|archive-url=https://web.archive.org/web/20180309045136/https://pod.penguincomputing.com/|url-status=live}}</ref> Penguin Computing launched its HPC cloud in 2016 as an alternative to Amazon's EC2 Elastic Compute Cloud, which uses virtualized computing nodes.<ref>{{cite web|last1=Niccolai|first1=James|title=Penguin Puts High-performance Computing in the Cloud|url=http://www.pcworld.com/article/170045/article.html|website=PCWorld|publisher=IDG Consumer & SMB|access-date=6 June 2016|date=11 August 2009|archive-date=19 August 2016|archive-url=https://web.archive.org/web/20160819051701/http://www.pcworld.com/article/170045/article.html|url-status=live}}</ref><ref>{{cite web|url=https://aws.amazon.com/hpc/|title=HPC in AWS|access-date=23 January 2018|archive-date=1 December 2017|archive-url=https://web.archive.org/web/20171201181150/https://aws.amazon.com/hpc/|url-status=live}}</ref>
 
==Architecture<!--'Cloud architecture' redirects here-->==
[[File:CloudComputingSampleArchitecture.svg|thumb|325px|right|Cloud computing sample architecture]]
 
'''[[Cloud computing architecture|Cloud architecture]]''',<ref>{{cite web |url=http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1632&categoryID=100 |title=Building GrepTheWeb in the Cloud, Part 1: Cloud Architectures |publisher=Developer.amazonwebservices.com |access-date=22 August 2010 |archive-url=https://web.archive.org/web/20090505200217/http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1632&categoryID=100 |archive-date=5 May 2009 |url-status=dead |df=dmy-all }}</ref> the [[systems architecture]] of the [[software systems]] involved in the delivery of cloud computing, typically involves multiple ''cloud components'' communicating with each other over a loose coupling mechanism such as a messaging queue. Elastic provision implies intelligence in the use of tight or loose coupling as applied to mechanisms such as these and others.
 
===Cloud engineering===
'''[[Cloud engineering]]''' is the application of [[engineering]] disciplines of cloud computing. It brings a systematic approach to the high-level concerns of commercialization, standardization and governance in conceiving, developing, operating and maintaining cloud computing systems. It is a multidisciplinary method encompassing contributions from diverse areas such as [[systems engineering|systems]], [[software engineering|software]], [[web engineering|web]], [[performance engineering|performance]], [[information technology engineering]], [[security engineering|security]], [[platform engineering|platform]], [[Risk analysis (engineering)|risk]], and [[Quality control|quality]] engineering.
 
==Market==