Cloud computing

From BizApps Wiki, the free Business Applications encyclopedia
Jump to: navigation, search

Cloud computing is the on-demand availability of computer system resources, especially data storage (cloud storage) and computing power, without direct active management by the user.[1] The term is generally used to describe data centers available to many users over the Internet.[2] Large clouds, predominant today, often have functions distributed over multiple locations from central servers. If the connection to the user is relatively close, it may be designated an edge server.

Clouds may be limited to a single organization (enterprise clouds[3][4]), or be available to multiple organizations (public cloud). Cloud computing relies on sharing of resources to achieve coherence and economies of scale.

Advocates of public and hybrid clouds note that cloud computing allows companies to avoid or minimize up-front IT infrastructure costs. Proponents also claim that cloud computing allows enterprises to get their applications up and running faster, with improved manageability and less maintenance, and that it enables IT teams to more rapidly adjust resources to meet fluctuating and unpredictable demand,[4][5][6] providing the burst computing capability: high computing power at certain periods of peak demand.[7]

Cloud Types[edit]

There are several basic cloud type we can recognize. On the first place in early cloud phases we had IaaS as Infrastructure-as-a-Service. It means enterprises will take and pay only for infrastructure from cloud provider and they will take care about everything else. In this case, cloud providers typically use a "pay-as-you-go" model, which can lead to unexpected operating expenses if administrators are not familiarized with cloud-pricing models.[8] Even if they are familiar with cloud-pricing model it is not easy to predict final cost. Because of that we have model where it is easier for predicting but still not 100% accurate - this is PaaS as Platform-as-a-Service model. In this case client will use not only infrastructure, but also a lot of platforms. It is easier for administering, but still cannot predict cost accurately. Probably the best model if this is possible (if application exists in this model) is SaaS Software-as-a-Service, because in this model client have information exactly what they are using and what they are paying and operational costs can be predicted accurately.

Service models[edit]

Cloud computing service models arranged as layers in a stack

Though service-oriented architecture advocates "Everything as a service" (with the acronyms EaaS or XaaS,[9] or simply aaS), cloud-computing providers offer their "services" according to different models, of which the three standard models per NIST are Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).[10] These models offer increasing abstraction; they are thus often portrayed as layers in a stack: infrastructure-, platform- and software-as-a-service, but these need not be related. For example, one can provide SaaS implemented on physical machines (bare metal), without using underlying PaaS or IaaS layers, and conversely one can run a program on IaaS and access it directly, without wrapping it as SaaS.

Infrastructure as a service (IaaS)[edit]

"Infrastructure as a service" (IaaS) refers to online services that provide high-level APIs used to abstract various low-level details of underlying network infrastructure like physical computing resources, location, data partitioning, scaling, security, backup, etc. A hypervisor runs the virtual machines as guests. Pools of hypervisors within the cloud operational system can support large numbers of virtual machines and the ability to scale services up and down according to customers' varying requirements. Linux containers run in isolated partitions of a single Linux kernel running directly on the physical hardware. Linux cgroups and namespaces are the underlying Linux kernel technologies used to isolate, secure and manage the containers. Containerisation offers higher performance than virtualization because there is no hypervisor overhead. IaaS clouds often offer additional resources such as a virtual-machine disk-image library, raw block storage, file or object storage, firewalls, load balancers, IP addresses, virtual local area networks (VLANs), and software bundles.[11]

The NIST's definition of cloud computing describes IaaS as "where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., host firewalls)."[10]

IaaS-cloud providers supply these resources on-demand from their large pools of equipment installed in data centers. For wide-area connectivity, customers can use either the Internet or carrier clouds (dedicated virtual private networks). To deploy their applications, cloud users install operating-system images and their application software on the cloud infrastructure. In this model, the cloud user patches and maintains the operating systems and the application software. Cloud providers typically bill IaaS services on a utility computing basis: cost reflects the amount of resources allocated and consumed.[12]

Platform as a service (PaaS)[edit]

The NIST's definition of cloud computing defines Platform as a Service as:[10]

The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages, libraries, services, and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment.

PaaS vendors offer a development environment to application developers. The provider typically develops toolkit and standards for development and channels for distribution and payment. In the PaaS models, cloud providers deliver a computing platform, typically including operating system, programming-language execution environment, database, and web server. Application developers develop and run their software on a cloud platform instead of directly buying and managing the underlying hardware and software layers. With some PaaS, the underlying computer and storage resources scale automatically to match application demand so that the cloud user does not have to allocate resources manually.[13][need quotation to verify]

Some integration and data management providers also use specialized applications of PaaS as delivery models for data. Examples include iPaaS (Integration Platform as a Service) and dPaaS (Data Platform as a Service). iPaaS enables customers to develop, execute and govern integration flows.[14] Under the iPaaS integration model, customers drive the development and deployment of integrations without installing or managing any hardware or middleware.[15] dPaaS delivers integration—and data-management—products as a fully managed service.[16] Under the dPaaS model, the PaaS provider, not the customer, manages the development and execution of programs by building data applications for the customer. dPaaS users access data through data-visualization tools.[17]

Software as a service (SaaS)[edit]

The NIST's definition of cloud computing defines Software as a Service as:[10]

The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based email), or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

In the software as a service (SaaS) model, users gain access to application software and databases. Cloud providers manage the infrastructure and platforms that run the applications. SaaS is sometimes referred to as "on-demand software" and is usually priced on a pay-per-use basis or using a subscription fee.[18] In the SaaS model, cloud providers install and operate application software in the cloud and cloud users access the software from cloud clients. Cloud users do not manage the cloud infrastructure and platform where the application runs. This eliminates the need to install and run the application on the cloud user's own computers, which simplifies maintenance and support. Cloud applications differ from other applications in their scalability—which can be achieved by cloning tasks onto multiple virtual machines at run-time to meet changing work demand.[19] Load balancers distribute the work over the set of virtual machines. This process is transparent to the cloud user, who sees only a single access-point. To accommodate a large number of cloud users, cloud applications can be multitenant, meaning that any machine may serve more than one cloud-user organization.

The pricing model for SaaS applications is typically a monthly or yearly flat fee per user,[20] so prices become scalable and adjustable if users are added or removed at any point. It may also be free.[21] Proponents claim that SaaS gives a business the potential to reduce IT operational costs by outsourcing hardware and software maintenance and support to the cloud provider. This enables the business to reallocate IT operations costs away from hardware/software spending and from personnel expenses, towards meeting other goals. In addition, with applications hosted centrally, updates can be released without the need for users to install new software. One drawback of SaaS comes with storing the users' data on the cloud provider's server. As a result,[citation needed] there could be unauthorized access to the data.[22] Examples of applications offered as SaaS are [games and productivity software like Google Docs and Word Online. SaaS applications may be integrated with cloud storage or File hosting services, which is the case with Google Docs being integrated with Google Drive and Word Online being integrated with Onedrive.[citation needed]

Mobile "backend" as a service (MBaaS)[edit]

In the mobile "backend" as a service (m) model, also known as backend as a service (BaaS), web app and mobile app developers are provided with a way to link their applications to cloud storage and cloud computing services with application programming interfaces (APIs) exposed to their applications and custom software development kits (SDKs). Services include user management, push notifications, integration with social networking services[23] and more. This is a relatively recent model in cloud computing,[24] with most BaaS startups dating from 2011 or later[25][26][27] but trends indicate that these services are gaining significant mainstream traction with enterprise consumers.[28]

Serverless computing[edit]

Serverless computing is a cloud computing code execution model in which the cloud provider fully manages starting and stopping virtual machines as necessary to serve requests, and requests are billed by an abstract measure of the resources required to satisfy the request, rather than per virtual machine, per hour.[29] Despite the name, it does not actually involve running code without servers.[29] Serverless computing is so named because the business or person that owns the system does not have to purchase, rent or provision servers or virtual machines for the back-end code to run on.

Function as a service (FaaS)[edit]

Function as a service (FaaS) is a service-hosted remote procedure call that leverages serverless computing to enable the deployment of individual functions in the cloud that run in response to events.[30] FaaS is included under the broader term serverless computing, but the terms may also be used interchangeably.[31]

Deployment models[edit]

Cloud computing types

Private cloud[edit]

Private cloud is cloud infrastructure operated solely for a single organization, whether managed internally or by a third party, and hosted either internally or externally.[10] Undertaking a private cloud project requires significant engagement to virtualize the business environment, and requires the organization to reevaluate decisions about existing resources. It can improve business, but every step in the project raises security issues that must be addressed to prevent serious vulnerabilities. Self-run data centers[32] are generally capital intensive. They have a significant physical footprint, requiring allocations of space, hardware, and environmental controls. These assets have to be refreshed periodically, resulting in additional capital expenditures. They have attracted criticism because users "still have to buy, build, and manage them" and thus do not benefit from less hands-on management,[33] essentially "[lacking] the economic model that makes cloud computing such an intriguing concept".[34][35]

Public cloud[edit]

Cloud services are considered "public" when they are delivered over the public Internet, and they may be offered as a paid subscription, or free of charge.[36] Architecturally, there are few differences between public- and private-cloud services, but security concerns increase substantially when services (applications, storage, and other resources) are shared by multiple customers. Most public-cloud providers offer direct-connection services that allow customers to securely link their legacy data centers to their cloud-resident applications.[37][38]

Several factors like the functionality of the solutions, cost, integrational and organizational aspects as well as safety & security are influencing the decision of enterprises and organizations to choose a public cloud or on-premise solution.[39]

Public Cloud Providers[edit]

The availability of high-capacity networks, low-cost computers and storage devices as well as the widespread adoption of hardware virtualization, service-oriented architecture and autonomic and utility computing has led to growth in cloud computing.[40][41][42]

As there is a lot of local cloud providers available only in one country or in small region, general market is focused on the biggest cloud players and they are currently:

But looking at cloud services connected with business applications, the most dominant as providers are Microsoft and Salesforce.

Hybrid cloud[edit]

Hybrid cloud is a composition of a public cloud and a private environment, such as a private cloud or on-premises resources,[43][44] that remain distinct entities but are bound together, offering the benefits of multiple deployment models. Hybrid cloud can also mean the ability to connect collocation, managed and/or dedicated services with cloud resources.[10] Gartner defines a hybrid cloud service as a cloud computing service that is composed of some combination of private, public and community cloud services, from different service providers.[45] A hybrid cloud service crosses isolation and provider boundaries so that it can't be simply put in one category of private, public, or community cloud service. It allows one to extend either the capacity or the capability of a cloud service, by aggregation, integration or customization with another cloud service.

Varied use cases for hybrid cloud composition exist. For example, an organization may store sensitive client data in house on a private cloud application, but interconnect that application to a business intelligence application provided on a public cloud as a software service.[46] This example of hybrid cloud extends the capabilities of the enterprise to deliver a specific business service through the addition of externally available public cloud services. Hybrid cloud adoption depends on a number of factors such as data security and compliance requirements, level of control needed over data, and the applications an organization uses.[47]

Another example of hybrid cloud is one where IT organizations use public cloud computing resources to meet temporary capacity needs that can not be met by the private cloud.[48] This capability enables hybrid clouds to employ cloud bursting for scaling across clouds.[10] Cloud bursting is an application deployment model in which an application runs in a private cloud or data center and "bursts" to a public cloud when the demand for computing capacity increases. A primary advantage of cloud bursting and a hybrid cloud model is that an organization pays for extra compute resources only when they are needed.[49] Cloud bursting enables data centers to create an in-house IT infrastructure that supports average workloads, and use cloud resources from public or private clouds, during spikes in processing demands.[50] The specialized model of hybrid cloud, which is built atop heterogeneous hardware, is called "Cross-platform Hybrid Cloud". A cross-platform hybrid cloud is usually powered by different CPU architectures, for example, x86-64 and ARM, underneath. Users can transparently deploy and scale applications without knowledge of the cloud's hardware diversity.[51] This kind of cloud emerges from the rise of ARM-based system-on-chip for server-class computing.

Hybrid cloud infrastructure essentially serves to eliminate limitations inherent to the multi-access relay characteristics of private cloud networking. The advantages include enhanced runtime flexibility and adaptive memory processing unique to virtualized interface models.[52]


Community cloud[edit]

Community cloud shares infrastructure between several organizations from a specific community with common concerns (security, compliance, jurisdiction, etc.), whether managed internally or by a third-party, and either hosted internally or externally. The costs are spread over fewer users than a public cloud (but more than a private cloud), so only some of the cost savings potential of cloud computing are realized.[10]

Distributed cloud[edit]

A cloud computing platform can be assembled from a distributed set of machines in different locations, connected to a single network or hub service. It is possible to distinguish between two types of distributed clouds: public-resource computing and volunteer cloud.

  • Public-resource computing—This type of distributed cloud results from an expansive definition of cloud computing, because they are more akin to distributed computing than cloud computing. Nonetheless, it is considered a sub-class of cloud computing.
  • Volunteer cloud—Volunteer cloud computing is characterized as the intersection of public-resource computing and cloud computing, where a cloud computing infrastructure is built using volunteered resources. Many challenges arise from this type of infrastructure, because of the volatility of the resources used to build it and the dynamic environment it operates in. It can also be called peer-to-peer clouds, or ad-hoc clouds. An interesting effort in such direction is Cloud@Home, it aims to implement a cloud computing infrastructure using volunteered resources providing a business-model to incentivize contributions through financial restitution.[53]

Multi cloud[edit]

Multi cloud is the use of multiple cloud computing services in a single heterogeneous architecture to reduce reliance on single vendors, increase flexibility through choice, mitigate against disasters, etc. It differs from hybrid cloud in that it refers to multiple cloud services, rather than multiple deployment modes (public, private, legacy).[54][55][56]

Poly cloud[edit]

Poly cloud refers to the use of multiple public clouds for the purpose of leveraging specific services that each provider offers. It differs from Multi cloud in that it is not designed to increase flexibility or mitigate against failures but is rather used to allow an organization to achieve more that could be done with a single provider.[57]

Big Data cloud[edit]

The issues of transferring large amounts of data to the cloud as well as data security once the data is in the cloud initially hampered adoption of cloud for big data, but now that much data originates in the cloud and with the advent of bare-metal servers, the cloud has become[58] a solution for use cases including business analytics and geospatial analysis.[59]

HPC cloud[edit]

HPC cloud refers to the use of cloud computing services and infrastructure to execute high-performance computing (HPC) applications.[60] These applications consume considerable amount of computing power and memory and are traditionally executed on 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 pay-as-you-go basis.[61][62] Penguin Computing launched its HPC cloud in 2016 as alternative to Amazon's EC2 Elastic Compute Cloud, which uses virtualized computing nodes.[63][64]


Cloud computing sample architecture

Cloud architecture,[65] 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[edit]

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, software, web, performance, information technology engineering, security, platform, risk, and quality engineering.


  1. Montazerolghaem, Ahmadreza; Yaghmaee, Mohammad Hossein; Leon-Garcia, Alberto (September 2020). "Green Cloud Multimedia Networking: NFV/SDN Based Energy-Efficient Resource Allocation". IEEE Transactions on Green Communications and Networking. pp. 873–889.
  2. The NIST Definition of Cloud Computing
  3. Wang (2012), Enterprise cloud service architectures, Information Technology and Management, pages 445–454|year=2012
  4. 4.0 4.1 "What is Cloud Computing?". Amazon Web Services. 2013-03-19. Retrieved 2013-03-20.
  5. Baburajan, Rajani (2011-08-24). "The Rising Cloud Storage Market Opportunity Strengthens Vendors". Retrieved 2011-12-02.
  6. Oestreich, Ken (2010-11-15). "Converged Infrastructure". CTO Forum. Archived from the original on 2012-01-13. Retrieved 2011-12-02.
  7. Ted Simpson, Jason Novak, Hands on Virtual Computing, 2017, ISBN: 1337515744, p. 451
  8. "Where's The Rub: Cloud Computing's Hidden Costs". 2014-02-27. Retrieved 2014-07-14.
  9. Duan, Yucong; Fu, Guohua; Zhou, Nianjun; Sun, Xiaobing; Narendra, Nanjangud; Hu, Bo (2015). "Everything as a Service (XaaS) on the Cloud: Origins, Current and Future Trends". 2015 IEEE 8th International Conference on Cloud Computing. IEEE. pp. 621–628. doi:10.1109/CLOUD.2015.88. ISBN 978-1-4673-7287-9. S2CID 8201466.
  10. 10.0 10.1 10.2 10.3 10.4 10.5 10.6 10.7 The NIST Definition of Cloud Computing NIST
  11. Amies, Alex; Sluiman, Harm; Tong, Qiang Guo; Liu, Guo Ning (July 2012). "Infrastructure as a Service Cloud Concepts". Developing and Hosting Applications on the Cloud. IBM Press. ISBN 978-0-13-306684-5.
  12. Griffin, Ry'mone (2018-11-20). Internet Governance. Scientific e-Resources. p. 111. ISBN 978-1-83947-395-1.
  13. Boniface, M.; et al. (2010). Platform-as-a-Service Architecture for Real-Time Quality of Service Management in Clouds. 5th International Conference on Internet and Web Applications and Services (ICIW). Barcelona, Spain: IEEE. pp. 155–160. doi:10.1109/ICIW.2010.91.
  14. "Integration Platform as a Service (iPaaS)". Gartner IT Glossary. Gartner.
  15. Gartner; Massimo Pezzini; Paolo Malinverno; Eric Thoo. "Gartner Reference Model for Integration PaaS". Retrieved 16 January 2013.
  16. Loraine Lawson. "IT Business Edge". Retrieved 6 July 2015.
  17. Enterprise CIO Forum; Gabriel Lowy. "The Value of Data Platform-as-a-Service (dPaaS)". Archived from the original on 19 April 2015. Retrieved 6 July 2015.
  18. "Definition of: SaaS". PC Magazine Encyclopedia. Ziff Davis. Retrieved 14 May 2014.
  19. Hamdaqa, Mohammad. A Reference Model for Developing Cloud Applications (PDF).
  20. Chou, Timothy. Introduction to Cloud Computing: Business & Technology.
  21. "HVD: the cloud's silver lining" (PDF). Intrinsic Technology. Archived from the original (PDF) on 2 October 2012. Retrieved 30 August 2012.
  22. Sun, Yunchuan; Zhang, Junsheng; Xiong, Yongping; Zhu, Guangyu (2014-07-01). "Data Security and Privacy in Cloud Computing". International Journal of Distributed Sensor Networks. 10 (7): 190903. doi:10.1155/2014/190903. ISSN 1550-1477. S2CID 13213544.
  23. Carney, Michael (2013-06-24). "AnyPresence partners with Heroku to beef up its enterprise mBaaS offering". PandoDaily. Retrieved 24 June 2013.
  24. Alex Williams (11 October 2012). "Kii Cloud Opens Doors For Mobile Developer Platform With 25 Million End Users". TechCrunch. Retrieved 16 October 2012.
  25. Aaron Tan (30 September 2012). "FatFractal ups the ante in backend-as-a-service market". Retrieved 16 October 2012.
  26. Dan Rowinski (9 November 2011). "Mobile Backend As A Service Parse Raises $5.5 Million in Series A Funding". ReadWrite. Retrieved 23 October 2012.
  27. Pankaj Mishra (7 January 2014). "MobStac Raises $2 Million in Series B To Help Brands Leverage Mobile Commerce". TechCrunch. Retrieved 22 May 2014.
  28. " Is Building an Enterprise MBaas Platform for IoT". programmableweb. 2014-03-03. Retrieved 3 March 2014.
  29. 29.0 29.1 Miller, Ron (24 Nov 2015). "AWS Lambda Makes Serverless Applications A Reality". TechCrunch. Retrieved 10 July 2016.
  30. "bliki: Serverless". Retrieved 2018-05-04.
  31. Sbarski, Peter (2017-05-04). Serverless Architectures on AWS: With examples using AWS Lambda (1st ed.). Manning Publications. ISBN 9781617293825.
  32. "Self-Run Private Cloud Computing Solution – GovConnection". 2014. Retrieved April 15, 2014.
  33. "Private Clouds Take Shape – Services – Business services – Informationweek". 2012-09-09. Archived from the original on 2012-09-09.
  34. Haff, Gordon (2009-01-27). "Just don't call them private clouds". CNET News. Retrieved 2010-08-22.
  35. "There's No Such Thing As A Private Cloud – Cloud-computing -". 2013-01-26. Archived from the original on 2013-01-26.
  36. Rouse, Margaret. "What is public cloud?". Definition from Retrieved 12 October 2014.
  37. "Defining 'Cloud Services' and "Cloud Computing"". IDC. 2008-09-23. Archived from the original on 2010-07-22. Retrieved 2010-08-22.
  38. "FastConnect | Oracle Cloud Infrastructure". Retrieved 2017-11-15.
  39. Schmidt, Rainer; Möhring, Michael; Keller, Barbara (2017). "Customer Relationship Management in a Public Cloud environment - Key influencing factors for European enterprises". HICSS. doi:10.24251/HICSS.2017.513.
  40. "Cloud Computing: Clash of the clouds". The Economist. 2009-10-15. Retrieved 2009-11-03.
  41. "Gartner Says Cloud Computing Will Be As Influential As E-business". Gartner. Retrieved 2010-08-22.
  42. Gruman, Galen (2008-04-07). "What cloud computing really means". InfoWorld. Retrieved 2009-06-02.
  43. "What is hybrid cloud? - Definition from". SearchCloudComputing. Retrieved 2019-08-10.
  44. Butler, Brandon (2017-10-17). "What is hybrid cloud computing? The benefits of mixing private and public cloud services". Network World. Retrieved 2019-08-11.
  45. "Mind the Gap: Here Comes Hybrid Cloud – Thomas Bittman". Thomas Bittman. Retrieved 22 April 2015.
  46. "Business Intelligence Takes to Cloud for Small Businesses". 2014-06-04. Retrieved 2014-06-04.
  47. Désiré Athow. "Hybrid cloud: is it right for your business?". TechRadar. Retrieved 22 April 2015.
  48. Metzler, Jim; Taylor, Steve. (2010-08-23) "Cloud computing: Reality vs. fiction", Network World.
  49. Rouse, Margaret. "Definition: Cloudbursting", May 2011.
  50. "How Cloudbursting "Rightsizes" the Data Center". 2012-06-22.
  51. Kaewkasi, Chanwit (3 May 2015). "Cross-Platform Hybrid Cloud with Docker".
  52. Qiang, Li (2009). "Adaptive management of virtualized resources in cloud computing using feedback control". First International Conference on Information Science and Engineering.
  53. Cunsolo, Vincenzo D.; Distefano, Salvatore; Puliafito, Antonio; Scarpa, Marco (2009). "Volunteer Computing and Desktop Cloud: The Cloud@Home Paradigm". 2009 Eighth IEEE International Symposium on Network Computing and Applications. pp. 134–139. doi:10.1109/NCA.2009.41. S2CID 15848602.
  54. Rouse, Margaret. "What is a multi-cloud strategy". SearchCloudApplications. Retrieved 3 July 2014.
  55. King, Rachel. "Pivotal's head of products: We're moving to a multi-cloud world". ZDnet. Retrieved 3 July 2014.
  56. Multcloud manage multiple cloud accounts. Retrieved on 06 August 2014
  57. Gall, Richard (2018-05-16). "Polycloud: a better alternative to cloud agnosticism". Packt Hub. Retrieved 2019-11-11.
  58. Roh, Lucas (31 August 2016). "Is the Cloud Finally Ready for Big Data?". Retrieved 29 January 2018.
  59. Yang, C.; Huang, Q.; Li, Z.; Liu, K.; Hu, F. (2017). "Big Data and cloud computing: innovation opportunities and challenges". International Journal of Digital Earth. 10 (1): 13–53. Bibcode:2017IJDE...10...13Y. doi:10.1080/17538947.2016.1239771. S2CID 8053067.
  60. Netto, M.; Calheiros, R.; Rodrigues, E.; Cunha, R.; Buyya, R. (2018). "HPC Cloud for Scientific and Business Applications: Taxonomy, Vision, and Research Challenges". ACM Computing Surveys. 51 (1): 8:1–8:29. arXiv:1710.08731. doi:10.1145/3150224. S2CID 3604131.
  61. Eadline, Douglas. "Moving HPC to the Cloud". Admin Magazine. Admin Magazine. Retrieved 30 March 2019.
  62. "Penguin Computing On Demand (POD)". Retrieved 23 January 2018.
  63. Niccolai, James (11 August 2009). "Penguin Puts High-performance Computing in the Cloud". PCWorld. IDG Consumer & SMB. Retrieved 6 June 2016.
  64. "HPC in AWS". Retrieved 23 January 2018.
  65. "Building GrepTheWeb in the Cloud, Part 1: Cloud Architectures". Archived from the original on 5 May 2009. Retrieved 22 August 2010.