Difference between revisions of "User:Shawndouglas/sandbox/sublevel45"

From LIMSWiki
Jump to navigationJump to search
(Created page with "right|650px|thumb|'''Figure 1.''' A basic visualization of [[cloud computing architecture layers and some of the activities that take p...")
 
Line 1: Line 1:
[[File:1000px-Cloud computing.svg.png|right|650px|thumb|'''Figure 1.''' A basic visualization of [[cloud computing]] architecture layers and some of the activities that take place on those layers.]]
Cloud computing has its strongest origins in the "web services" phase of internet development. In November 2000, Mind Electric CEO and [[distributed computing]] visionary Graham Glass, writing for IBM, described web services as "building blocks for creating open distributed systems" that "allow companies and individuals to quickly and cheaply make their digital assets available worldwide," while prognosticating that web services "will catalyze a shift from client-server to peer-to-peer architectures."<ref name="GlassTheWeb00">{{cite web |url=http://www-106.ibm.com/developerworks/library/ws-peer1.html |archiveurl=https://web.archive.org/web/20010424015036/http://www-106.ibm.com/developerworks/library/ws-peer1.html |title=The Web services (r)evolution, Part 1: Applying Web services to applications |author=Glass, G. |work=IBM developerWorks |publisher=IBM |date=November 2000 |archivedate=24 April 2001 |accessdate=21 August 2021}}</ref> At that point, the likes of Microsoft and IBM were already developing toolkits for creating and deploying web services<ref name="GlassTheWeb00" />, with IBM releasing an initial high-level report in May 2001 on IBM's web services architecture approach. In that paper, web services were described by its author Heather Kreger as allowing "companies to reduce the cost of doing e-business, to deploy solutions faster, and to open up new opportunities," while also allowing "applications to be integrated more rapidly, easily, and less expensively than ever before."<ref name="KregerWeb01">{{cite web |url=https://www.researchgate.net/profile/Heather-Kreger/publication/235720479_Web_Services_Conceptual_Architecture_WSCA_10/links/563a67e008ae337ef2984607/Web-Services-Conceptual-Architecture-WSCA-10.pdf |format=PDF |title=Web Services Conceptual Architecture (WSCA 1.0) |author=Kreger, H. |date=May 2001 |publisher=IBM Software Group |accessdate=21 August 2021}}</ref>  
If you were alive in the late 2000s and doing most anything related to computers and the internet, you were bound to encounter the latest internet buzzword: [[cloud computing]].<ref name="PogueInSync08">{{cite web |url=https://www.nytimes.com/2008/07/17/technology/personaltech/17pogue.html |archiveurl=https://web.archive.org/web/20180105205750/https://www.nytimes.com/2008/07/17/technology/personaltech/17pogue.html |title=In Sync to Pierce the Cloud |author=Pogue, D. |work=The New York Times |date=17 July 2008 |archivedate=05 January 2018 |accessdate=21 August 2021}}</ref><ref name="WangCloud10">{{cite journal |title=Cloud Computing: A Perspective Study |journal=New Generation Computing |author=Wang, L.; von Laszewski, G.; Younge, A. et al. |volume=28 |pages=137–46 |year=2010 |doi=10.1007/s00354-008-0081-5 |url=https://scholarworks.rit.edu/cgi/viewcontent.cgi?article=1748&context=other}}</ref> A certain mysticism was seemingly attached to the concept, that your files and applications could reside on the internet, "out there in the 'cloud.'"<ref name="PogueInSync08" /> "But what is this 'cloud'?" many would ask. A plethora of media articles, journal articles, blogs, and company websites were published to give practically everyone's take on what the cloud was and wasn't meant to be.<ref name="ChamberlinCloud08">{{cite web |url=https://www.billchamberlin.com/cloud-computing-what-is-it/ |title=Cloud Computing: What is it? |author=Chamberlin, B. |work=BillChamberlin.com |date=28 October 2008 |accessdate=21 August 2021}}</ref> However, the then growing consensus of cloud computing as networked and scalable architecture meant to rapidly provide application and infrastructure services at reasonable prices to internet users<ref name="WangCloud10" /><ref name="ChamberlinCloud08" /> largely matches up with today's definition. Pulling from both The Institution of Engineering and Technology<ref name="FrenchCloud21">{{cite web |url=https://www.theiet.org/publishing/inspec/researching-hot-topics/cloud-computing-and-web-services/ |title=Cloud computing and web services |author=French, J. |publisher=The Institution of Engineering and Technology |date=2021 |accessdate=21 August 2021}}</ref> and Amazon Web Services<ref name="AWSCloud21">{{cite web |url=https://www.tutorialspoint.com/amazon_web_services/amazon_web_services_cloud_computing.htm |title=Amazon Web Services - Cloud Computing |publisher=TutorialsPoint |date=2021 |accessdate=21 August 2021}}</ref>, we come up with cloud computing as:


<blockquote>an internet-based computing paradigm in which standardized and [[Virtualization|virtualized]] resources are used to rapidly, elastically, and cost-effectively provide a variety of globally available, "always-on" computing services to users on a continuous or as-needed basis</blockquote>
Here's a recap of thinking on web services at the turn of the century:


Of course, those computing services come in a variety of flavors, the most common being [[Software as a service|software]], [[Platform as a service|platform]], and [[Infrastructure as a service|infrastructure]] "as a service" (SaaS, PaaS, and IaaS, respectively). These conveniently correspond to the underlying architectural layers of the services, with infrastructure at the base, platform on top of that, and software (or application) on top of that.
* "[act as] building blocks for creating open distributed systems"<ref name="GlassTheWeb00" />
* "quickly and cheaply make ... digital assets available worldwide"<ref name="GlassTheWeb00" />
* "catalyze a shift from client-server to peer-to-peer architectures"<ref name="GlassTheWeb00" />
* "reduce the cost of doing e-business, to deploy solutions faster, and to open up new opportunities"<ref name="KregerWeb01" />
* "[allow] applications to be integrated more rapidly, easily, and less expensively than ever before"<ref name="KregerWeb01" />


Figure 1 portrays a simplified visualization of cloud computing architecture layers, as well as examples of activities that happen on those layers. This concept has also been visualized by others using pyramids and pancake stacks of layers, but the concept remains the same. At the base is the computing infrastructure, including the physical data centers and their networking equipment, servers, [[hypervisor]]s, [[application programming interface]]s (APIs), and operating systems. This infrastructure is the foundation that supports not only applications users want to run but also that acts as the developmental foundation of users not wanting to implement their own infrastructure. On top of all that can be found platforms or middleware, which serve as software development and deployment environments (that include databases, web servers, load balancers, etc.) or connectivity tools for analytics, [[workflow]] management, system integration, and security management. And on top of that are applications, typically designed to run optimally in cloud environments and accessed via web browsers or apps using internet—i.e. networking—connectivity and computing devices.<ref name="MaurerCloud20">{{cite web |url=https://carnegieendowment.org/2020/08/31/cloud-security-primer-for-policymakers-pub-82597 |title=Cloud Security: A Primer for Policymakers |author=Maurer, T.; Hinck, G. |publisher=Carnegie Endowment for International Peace |date=31 August 2020 |accessdate=21 August 2021}}</ref>
We'll come back to that. For the next stop, however, we have to consider the case of Amazon and how they viewed web services at that time. Leading up to the twenty-first century, Amazon was beginning to expand beyond its book selling roots, opening up its marketplace to other third parties (affiliates) to sell their own goods on Amazon's platform. That effort required an expansion of IT infrastructure to support web-scale third-party selling, but as it turned out, a lot of that IT infrastructure, while reliable and cost-effective, had been previously added piecemeal, with many components getting "tangled" along the way. Amazon project leads and external partners were clamoring for better infrastructure services. This required untangling the IT and associated provider data into an internally scalable, centralized infrastructure that allowed for smoother communication and [[Information management|data management]] using well-documented APIs.<ref name="FurrierExclusive15">{{cite web |url=https://medium.com/@furrier/original-content-the-story-of-aws-and-andy-jassys-trillion-dollar-baby-4e8a35fd7ed |title=Exclusive: The Story of AWS and Andy Jassy’s Trillion Dollar Baby |author=Furrier, J. |work=Medium.com |date=29 January 2015 |accessdate=21 August 2021}}</ref><ref name="MillerHowAWS16">{{cite web |url=https://techcrunch.com/2016/07/02/andy-jassys-brief-history-of-the-genesis-of-aws/ |title=How AWS came to be |author=Miller, R. |work=TechCrunch |date=02 July 2016 |accessdate=21 August 2021}}</ref> By 2003, the company was indirectly acting as a services industry to its partners. "Why not act upon this strength?" was the sentiment that quickly developed that year, with Amazon choosing to use its internal compute, storage, and database infrastructure and related expertise to its advantage.<ref name="MillerHowAWS16" />  


Customers who require application hosting, internet-hosted software development platforms, or underlying computing infrastructure (e.g., data storage, computational time, etc.)—particularly when they can't or don't want to invest in their own hardware—are increasingly turning to the cloud computing paradigm. Even before a worldwide [[COVID-19]] [[pandemic]] started to take shape in late 2019, the global cloud services market was expected to reach $266.4 billion by the end of 2020, with Gartner expecting that to represent a 17 percent increase from 2019.<ref name="CostelloFore19">{{cite web |url=https://www.gartner.com/en/newsroom/press-releases/2019-11-13-gartner-forecasts-worldwide-public-cloud-revenue-to-grow-17-percent-in-2020 |title=Gartner Forecasts Worldwide Public Cloud Revenue to Grow 17% in 2020 |author=Costello, K.; Rimol, M. |publisher=Gartner |date=13 November 2020 |accessdate=21 August 2021}}</ref> As work-from-home practices expanded significantly in 2020 due to the pandemic, expectations that the trend would last post-pandemic pushed estimates of overall cloud-based workloads moving from physical work offices to the cloud to 55 percent by 2022, with the cloud services market reaching $1 trillion by 2030.<ref name="ReinickeThree20">{{cite web |url=https://markets.businessinsider.com/news/stocks/wedbush-reasons-own-cloud-stocks-coronavirus-pandemic-tech-buy-2020-3-1029045273#2-the-move-to-cloud-will-accelerate-more-quickly-amid-the-coronavirus-pandemic2 |title=3 reasons one Wall Street firm says to stick with cloud stocks amid the coronavirus-induced market rout |author=Reinicke, C. |work=Market Insider |date=30 March 2020 |accessdate=21 August 2021}}</ref> This growing migration to cloud computing has many implications for organizations of all types, including [[Laboratory|laboratories]].
At that point, the paradigm of web services expanded to include infrastructure as a service or IaaS, with compute, storage, and database services running over the internet for web developers to utilize.<ref name="FurrierExclusive15" /><ref name="MillerHowAWS16" /> "If you believe developers will build applications from scratch using web services as primitive building blocks, then the operating system becomes the internet,” noted AWS CEO Andy Jassy in a 2015 retrospective interview.<ref name="FurrierExclusive15" /> From that concept evolved the idea of determining what it would take to allow any entity to run their technology applications over their web-service-based IaaS platform. In August 2006, Amazon introduced its Amazon Elastic Compute Cloud (Amazon EC2), "a web service that provides resizable compute capacity in the cloud."<ref name="AWSAnnounc06">{{cite web |url=https://aws.amazon.com/about-aws/whats-new/2006/08/24/announcing-amazon-elastic-compute-cloud-amazon-ec2---beta/ |title=Announcing Amazon Elastic Compute Cloud (Amazon EC2) - beta |publisher=Amazon Web Services |date=24 August 2006 |accessdate=21 August 2021}}</ref><ref name="ButlerAmazon06">{{cite journal |title=Amazon puts network power online |journal=Nature |author=Butler, D. |volume=444 |issue=528 |year=2006 |doi=10.1038/444528a}}</ref> This quickly prompted others in academic and scientific fields to continue the conversation of turning IT and its infrastructure into a service.<ref name="ButlerAmazon06" /><ref name="KeITeS06">{{cite journal |title=ITeS - Transcending the Traditional Service Model |journal=Proceedings of the 2006 IEEE International Conference on e-Business Engineering |author=Ke, J.-s. |page=2 |year=2006 |doi=10.1109/ICEBE.2006.66}}</ref> In turn, conversations changed, discussing the opportunities inherent to "cloud computing," including Google and IBM partnering to virtualize computers on new data centers for boosting academic research and teaching new computer science students<ref name="LohrGoogle07">{{cite web |url=http://www.nytimes.com/2007/10/08/technology/08cloud.html?_r=1&or |archiveurl=http://www.csun.edu/pubrels/clips/Oct07/10-08-07E.pdf |format=PDF |title=Google and I.B.M. Join in 'Cloud Computing' Research |author=Lohr, S. |work=The New York Times |date=08 October 2007 |archivedate=08 October 2007 |accessdate=21 August 2021}}</ref><ref name="HandHead07">{{cite journal |title=Head in the clouds |journal=Nature |author=Hand, E. |volume=449 |issue=963 |year=2007 |doi=10.1038/449963a}}</ref>, IBM releasing a white paper on cloud computing<ref name="BossCloud07">{{cite web |url=http://download.boulder.ibm.com/ibmdl/pub/software/dw/wes/hipods/Cloud_computing_wp_final_8Oct.pdf |archiveurl=https://web.archive.org/web/20090206015244/http://download.boulder.ibm.com/ibmdl/pub/software/dw/wes/hipods/Cloud_computing_wp_final_8Oct.pdf |format=PDF |title=Cloud Computing |author=Boss, G.; Malladi, P.; Quan, D. et al. |publisher=IBM Corporation |date=08 October 2007 |archivedate=06 February 2009 |accessdate=21 August 2021}}</ref> and announcing its Blue Cloud initiative<ref name="LohrIBM07">{{cite web |url=https://www.nytimes.com/2007/11/15/technology/15blue.html |title=I.B.M. to Push 'Cloud Computing,' Using Data From Afar |author=Lohr, S. |work=The New York Times |date=15 November 2007 |accessdate=21 August 2021}}</ref>, and Google doubling down on its cloud-based software offerings in competition with Microsoft.<ref name="LohrGoogleGets07">{{cite web |url=https://www.nytimes.com/2007/12/16/technology/16goog.html |archiveurl=https://signallake.com/innovation/GoogleMicrosoft121607.pdf |format=PDF |title=Google Gets Ready to Rumble With Microsoft |author=Lohr, S.; Helft, M. |work=The New York Times |date=16 December 2007 |archivedate=16 December 2007 |accessdate=21 August 2021}}</ref>
 
In IBM's 2007 white paper, they described cloud computing as a "pool of virtualized computer resources" that can<ref name="BossCloud07" />:
 
*  "host a variety of different workloads, including batch-style back-end jobs and interactive, user-facing applications";
*  "allow workloads to be deployed and scaled-out quickly through the rapid provisioning of virtual machines or physical machines";
*  "support redundant, self-recovering, highly scalable programming models that allow workloads to recover from many unavoidable hardware/software failures";
*  "monitor resource use in real time to enable rebalancing of allocations when needed"; and
*  "be a cost efficient model for delivering information services, reducing IT management complexity, promoting innovation, and increasing responsiveness through real-time workload balancing."
 
In 2011, the National Institute of Standards and Technology (NIST) came up with a more standards-based definition to cloud computing. They described it as "a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction."<ref name="MellTheNIST11">{{cite web |url=https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf |format=PDF |title=The NIST Definition of Cloud Computing |author=Mell, P.; Grance, T. |publisher=NIST |date=September 2011 |accessdate=21 August 2021}}</ref> They went on to highlight the five essential characteristics further<ref name="MellTheNIST11" />:
 
* On-demand self-service: The unilateral provision of computing resources should be an automatic or nearly automatic process.
* Broad network access: Thin- or thick-client platforms, both hardwired and mobile, should allow for standardized, networkable access to those computing resources.
* Resource pooling: A multi-tenant model requires the provisioning of resources to serve a wide customer base, with a layer of abstraction that gives the user a sense of location independence from those resources.
* Rapid elasticity: The platform's resources should be readily and/or automatically scalable commensurate with demand, such that the user sees no negative impact in their activities.
* Measured service: The resources should be automatically controlled and optimized by a measured service or metering system, transparently providing accurate and timely information about resource usage.
 
When we compare these 2007 and 2011 definitions of cloud computing with the comments on web services by Glass and Kreger at the turn of the century (as well as our own derived definition prior), we can't help but see how the early vision for cloud computing has taken shape today. First, web services can indeed be paired with other technologies to form a distributed system, in this case a centralized and scalable computing infrastructure that can be used by practically anyone to run software, develop applications, and "host a variety of different workloads."<ref name="BossCloud07" /> Second, those workloads can be quickly deployed worldwide, wherever there is internet access, and typically at a fair price, when compared to the costs of on-premises data management.<ref name="ViolinoWhere20">{{cite web |url=https://www.infoworld.com/article/3532288/where-to-look-for-cost-savings-in-the-cloud.html |title=Where to look for cost savings in the cloud |author=Violino, B. |work=InfoWorld |date=16 March 2020 |accessdate=21 August 2021}}</ref> Third, new opportunities are indeed developing for organizations seeking to tap into the on-demand, rapid, scalable, and cost-efficient nature of cloud computing.<ref name="OjalaDiscover16">{{cite journal |title=Discovering and creating business opportunities for cloud services |journal=Journal of Systems and Software |author=Ojala, A. |volume=113 |pages=408–17 |year=2016 |doi=10.1016/j.jss.2015.11.004}}</ref><ref name="PetteyCloud20">{{cite web |url=https://www.gartner.com/smarterwithgartner/cloud-shift-impacts-all-it-markets/ |title=Cloud Shift Impacts All IT Markets |author=Pettey, C. |work=Smarter with Gartner |date=26 October 2020 |accessdate=21 August 2021}}</ref> And finally, benefits are being seen in the integration of applications via the cloud, particularly as more options for multicloud and hybrid cloud integration develop.<ref name="PetteyFiveApp19">{{cite web |url=https://www.gartner.com/smarterwithgartner/5-approaches-cloud-applications-integration/ |title=5 Approaches to Cloud Applications Integration |author=Pettey, C. |work=Smarter with Gartner |date=14 May 2019 |accessdate=21 August 2021}}</ref> The early vision that perhaps hasn't been realized is found in Glass' "shift from client-server to peer-to-peer architectures," though discussions about the promise of peer-to-peer cloud computing have occurred since.<ref name="BabaogluEscape14">{{cite journal |title=The People's Cloud |journal=IEEE Spectrum |author=Babaoglu, O.; Marzolla, M. |volume=51 |issue=10 |pages=50–55 |year=2014 |doi=10.1109/MSPEC.2014.6905491 |url=https://spectrum.ieee.org/computing/networks/escape-from-the-data-center-the-promise-of-peertopeer-cloud-computing}}</ref>
 
Though clearly linked to web services and the early vision of cloud computing in the 2000s, the cloud computing of the 2020s is a remarkably more advanced and continually evolving technology. However, it's still not without its challenges today. The data security, privacy, and governance of computing in general, and cloud computing in particular, will continue to require more rigorous approaches, as will reducing remaining data silos in organizations with pivots to hybrid cloud, multicloud, and serverless cloud implementations.<ref name="Goodison10Fut20">{{cite web |url=https://www.crn.com/news/cloud/10-future-cloud-computing-trends-to-watch-in-2021 |title=10 Future Cloud Computing Trends To Watch In 2021 |author=Goodison, D. |work=CRN |date=20 November 2020 |accessdate=21 August 2021}}</ref><ref name="DTCCCloud20">{{cite web |url=http://www.dtcc.com/-/media/Files/Downloads/WhitePapers/DTCC-Cloud-Journey-WP |format=PDF |title=Cloud Technology: Powerful and Evolving |author=DTCC |date=November 2020 |accessdate=21 August 2021}}</ref> But what is "hybrid cloud"? "Serverless cloud?" The next section goes into further detail.


==References==
==References==
{{Reflist|colwidth=30em}}
{{Reflist|colwidth=30em}}

Revision as of 18:29, 21 August 2021

Cloud computing has its strongest origins in the "web services" phase of internet development. In November 2000, Mind Electric CEO and distributed computing visionary Graham Glass, writing for IBM, described web services as "building blocks for creating open distributed systems" that "allow companies and individuals to quickly and cheaply make their digital assets available worldwide," while prognosticating that web services "will catalyze a shift from client-server to peer-to-peer architectures."[1] At that point, the likes of Microsoft and IBM were already developing toolkits for creating and deploying web services[1], with IBM releasing an initial high-level report in May 2001 on IBM's web services architecture approach. In that paper, web services were described by its author Heather Kreger as allowing "companies to reduce the cost of doing e-business, to deploy solutions faster, and to open up new opportunities," while also allowing "applications to be integrated more rapidly, easily, and less expensively than ever before."[2]

Here's a recap of thinking on web services at the turn of the century:

  • "[act as] building blocks for creating open distributed systems"[1]
  • "quickly and cheaply make ... digital assets available worldwide"[1]
  • "catalyze a shift from client-server to peer-to-peer architectures"[1]
  • "reduce the cost of doing e-business, to deploy solutions faster, and to open up new opportunities"[2]
  • "[allow] applications to be integrated more rapidly, easily, and less expensively than ever before"[2]

We'll come back to that. For the next stop, however, we have to consider the case of Amazon and how they viewed web services at that time. Leading up to the twenty-first century, Amazon was beginning to expand beyond its book selling roots, opening up its marketplace to other third parties (affiliates) to sell their own goods on Amazon's platform. That effort required an expansion of IT infrastructure to support web-scale third-party selling, but as it turned out, a lot of that IT infrastructure, while reliable and cost-effective, had been previously added piecemeal, with many components getting "tangled" along the way. Amazon project leads and external partners were clamoring for better infrastructure services. This required untangling the IT and associated provider data into an internally scalable, centralized infrastructure that allowed for smoother communication and data management using well-documented APIs.[3][4] By 2003, the company was indirectly acting as a services industry to its partners. "Why not act upon this strength?" was the sentiment that quickly developed that year, with Amazon choosing to use its internal compute, storage, and database infrastructure and related expertise to its advantage.[4]

At that point, the paradigm of web services expanded to include infrastructure as a service or IaaS, with compute, storage, and database services running over the internet for web developers to utilize.[3][4] "If you believe developers will build applications from scratch using web services as primitive building blocks, then the operating system becomes the internet,” noted AWS CEO Andy Jassy in a 2015 retrospective interview.[3] From that concept evolved the idea of determining what it would take to allow any entity to run their technology applications over their web-service-based IaaS platform. In August 2006, Amazon introduced its Amazon Elastic Compute Cloud (Amazon EC2), "a web service that provides resizable compute capacity in the cloud."[5][6] This quickly prompted others in academic and scientific fields to continue the conversation of turning IT and its infrastructure into a service.[6][7] In turn, conversations changed, discussing the opportunities inherent to "cloud computing," including Google and IBM partnering to virtualize computers on new data centers for boosting academic research and teaching new computer science students[8][9], IBM releasing a white paper on cloud computing[10] and announcing its Blue Cloud initiative[11], and Google doubling down on its cloud-based software offerings in competition with Microsoft.[12]

In IBM's 2007 white paper, they described cloud computing as a "pool of virtualized computer resources" that can[10]:

  • "host a variety of different workloads, including batch-style back-end jobs and interactive, user-facing applications";
  • "allow workloads to be deployed and scaled-out quickly through the rapid provisioning of virtual machines or physical machines";
  • "support redundant, self-recovering, highly scalable programming models that allow workloads to recover from many unavoidable hardware/software failures";
  • "monitor resource use in real time to enable rebalancing of allocations when needed"; and
  • "be a cost efficient model for delivering information services, reducing IT management complexity, promoting innovation, and increasing responsiveness through real-time workload balancing."

In 2011, the National Institute of Standards and Technology (NIST) came up with a more standards-based definition to cloud computing. They described it as "a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction."[13] They went on to highlight the five essential characteristics further[13]:

  • On-demand self-service: The unilateral provision of computing resources should be an automatic or nearly automatic process.
  • Broad network access: Thin- or thick-client platforms, both hardwired and mobile, should allow for standardized, networkable access to those computing resources.
  • Resource pooling: A multi-tenant model requires the provisioning of resources to serve a wide customer base, with a layer of abstraction that gives the user a sense of location independence from those resources.
  • Rapid elasticity: The platform's resources should be readily and/or automatically scalable commensurate with demand, such that the user sees no negative impact in their activities.
  • Measured service: The resources should be automatically controlled and optimized by a measured service or metering system, transparently providing accurate and timely information about resource usage.

When we compare these 2007 and 2011 definitions of cloud computing with the comments on web services by Glass and Kreger at the turn of the century (as well as our own derived definition prior), we can't help but see how the early vision for cloud computing has taken shape today. First, web services can indeed be paired with other technologies to form a distributed system, in this case a centralized and scalable computing infrastructure that can be used by practically anyone to run software, develop applications, and "host a variety of different workloads."[10] Second, those workloads can be quickly deployed worldwide, wherever there is internet access, and typically at a fair price, when compared to the costs of on-premises data management.[14] Third, new opportunities are indeed developing for organizations seeking to tap into the on-demand, rapid, scalable, and cost-efficient nature of cloud computing.[15][16] And finally, benefits are being seen in the integration of applications via the cloud, particularly as more options for multicloud and hybrid cloud integration develop.[17] The early vision that perhaps hasn't been realized is found in Glass' "shift from client-server to peer-to-peer architectures," though discussions about the promise of peer-to-peer cloud computing have occurred since.[18]

Though clearly linked to web services and the early vision of cloud computing in the 2000s, the cloud computing of the 2020s is a remarkably more advanced and continually evolving technology. However, it's still not without its challenges today. The data security, privacy, and governance of computing in general, and cloud computing in particular, will continue to require more rigorous approaches, as will reducing remaining data silos in organizations with pivots to hybrid cloud, multicloud, and serverless cloud implementations.[19][20] But what is "hybrid cloud"? "Serverless cloud?" The next section goes into further detail.

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 Glass, G. (November 2000). "The Web services (r)evolution, Part 1: Applying Web services to applications". IBM developerWorks. IBM. Archived from the original on 24 April 2001. https://web.archive.org/web/20010424015036/http://www-106.ibm.com/developerworks/library/ws-peer1.html. Retrieved 21 August 2021. 
  2. ↑ 2.0 2.1 2.2 Kreger, H. (May 2001). "Web Services Conceptual Architecture (WSCA 1.0)" (PDF). IBM Software Group. https://www.researchgate.net/profile/Heather-Kreger/publication/235720479_Web_Services_Conceptual_Architecture_WSCA_10/links/563a67e008ae337ef2984607/Web-Services-Conceptual-Architecture-WSCA-10.pdf. Retrieved 21 August 2021. 
  3. ↑ 3.0 3.1 3.2 Furrier, J. (29 January 2015). "Exclusive: The Story of AWS and Andy Jassy’s Trillion Dollar Baby". Medium.com. https://medium.com/@furrier/original-content-the-story-of-aws-and-andy-jassys-trillion-dollar-baby-4e8a35fd7ed. Retrieved 21 August 2021. 
  4. ↑ 4.0 4.1 4.2 Miller, R. (2 July 2016). "How AWS came to be". TechCrunch. https://techcrunch.com/2016/07/02/andy-jassys-brief-history-of-the-genesis-of-aws/. Retrieved 21 August 2021. 
  5. ↑ "Announcing Amazon Elastic Compute Cloud (Amazon EC2) - beta". Amazon Web Services. 24 August 2006. https://aws.amazon.com/about-aws/whats-new/2006/08/24/announcing-amazon-elastic-compute-cloud-amazon-ec2---beta/. Retrieved 21 August 2021. 
  6. ↑ 6.0 6.1 Butler, D. (2006). "Amazon puts network power online". Nature 444 (528). doi:10.1038/444528a. 
  7. ↑ Ke, J.-s. (2006). "ITeS - Transcending the Traditional Service Model". Proceedings of the 2006 IEEE International Conference on e-Business Engineering: 2. doi:10.1109/ICEBE.2006.66. 
  8. ↑ Lohr, S. (8 October 2007). "Google and I.B.M. Join in 'Cloud Computing' Research" (PDF). The New York Times. Archived from the original on 08 October 2007. http://www.csun.edu/pubrels/clips/Oct07/10-08-07E.pdf. Retrieved 21 August 2021. 
  9. ↑ Hand, E. (2007). "Head in the clouds". Nature 449 (963). doi:10.1038/449963a. 
  10. ↑ 10.0 10.1 10.2 Boss, G.; Malladi, P.; Quan, D. et al. (8 October 2007). "Cloud Computing" (PDF). IBM Corporation. Archived from the original on 06 February 2009. https://web.archive.org/web/20090206015244/http://download.boulder.ibm.com/ibmdl/pub/software/dw/wes/hipods/Cloud_computing_wp_final_8Oct.pdf. Retrieved 21 August 2021. 
  11. ↑ Lohr, S. (15 November 2007). "I.B.M. to Push 'Cloud Computing,' Using Data From Afar". The New York Times. https://www.nytimes.com/2007/11/15/technology/15blue.html. Retrieved 21 August 2021. 
  12. ↑ Lohr, S.; Helft, M. (16 December 2007). "Google Gets Ready to Rumble With Microsoft" (PDF). The New York Times. Archived from the original on 16 December 2007. https://signallake.com/innovation/GoogleMicrosoft121607.pdf. Retrieved 21 August 2021. 
  13. ↑ 13.0 13.1 Mell, P.; Grance, T. (September 2011). "The NIST Definition of Cloud Computing" (PDF). NIST. https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf. Retrieved 21 August 2021. 
  14. ↑ Violino, B. (16 March 2020). "Where to look for cost savings in the cloud". InfoWorld. https://www.infoworld.com/article/3532288/where-to-look-for-cost-savings-in-the-cloud.html. Retrieved 21 August 2021. 
  15. ↑ Ojala, A. (2016). "Discovering and creating business opportunities for cloud services". Journal of Systems and Software 113: 408–17. doi:10.1016/j.jss.2015.11.004. 
  16. ↑ Pettey, C. (26 October 2020). "Cloud Shift Impacts All IT Markets". Smarter with Gartner. https://www.gartner.com/smarterwithgartner/cloud-shift-impacts-all-it-markets/. Retrieved 21 August 2021. 
  17. ↑ Pettey, C. (14 May 2019). "5 Approaches to Cloud Applications Integration". Smarter with Gartner. https://www.gartner.com/smarterwithgartner/5-approaches-cloud-applications-integration/. Retrieved 21 August 2021. 
  18. ↑ Babaoglu, O.; Marzolla, M. (2014). "The People's Cloud". IEEE Spectrum 51 (10): 50–55. doi:10.1109/MSPEC.2014.6905491. https://spectrum.ieee.org/computing/networks/escape-from-the-data-center-the-promise-of-peertopeer-cloud-computing. 
  19. ↑ Goodison, D. (20 November 2020). "10 Future Cloud Computing Trends To Watch In 2021". CRN. https://www.crn.com/news/cloud/10-future-cloud-computing-trends-to-watch-in-2021. Retrieved 21 August 2021. 
  20. ↑ DTCC (November 2020). "Cloud Technology: Powerful and Evolving" (PDF). http://www.dtcc.com/-/media/Files/Downloads/WhitePapers/DTCC-Cloud-Journey-WP. Retrieved 21 August 2021. 
Retrieved from "https://www.limswiki.org/index.php?title=User:Shawndouglas/sandbox/sublevel45&oldid=43744"