Relevant bibliographies by topics / AWS Serverless

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers

Academic literature on the topic 'AWS Serverless'

Author: Grafiati
Published: 30 May 2022
Last updated: 31 May 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'AWS Serverless.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "AWS Serverless"

1

Ratkov, Aleksandar. "DIZAJN SERVERLESS WEB APLIKACIJA NA AMAZON PLATFORMI." Zbornik radova Fakulteta tehničkih nauka u Novom Sadu 34, no. 11 (November 3, 2019): 2009–11. http://dx.doi.org/10.24867/05be16ratkov.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Risco, Sebastián, and Germán Moltó. "GPU-Enabled Serverless Workflows for Efficient Multimedia Processing." Applied Sciences 11, no. 4 (February 5, 2021): 1438. http://dx.doi.org/10.3390/app11041438.

Full text
Abstract:
Serverless computing has introduced scalable event-driven processing in Cloud infrastructures. However, it is not trivial for multimedia processing to benefit from the elastic capabilities featured by serverless applications. To this aim, this paper introduces the evolution of a framework to support the execution of customized runtime environments in AWS Lambda in order to accommodate workloads that do not satisfy its strict computational requirements: increased execution times and the ability to use GPU-based resources. This has been achieved through the integration of AWS Batch, a managed service to deploy virtual elastic clusters for the execution of containerized jobs. In addition, a Functions Definition Language (FDL) is introduced for the description of data-driven workflows of functions. These workflows can simultaneously leverage both AWS Lambda for the highly-scalable execution of short jobs and AWS Batch, for the execution of compute-intensive jobs that can profit from GPU-based computing. To assess the developed open-source framework, we executed a case study for efficient serverless video processing. The workflow automatically generates subtitles based on the audio and applies GPU-based object recognition to the video frames, thus simultaneously harnessing different computing services. This allows for the creation of cost-effective highly-parallel scale-to-zero serverless workflows in AWS.
APA, Harvard, Vancouver, ISO, and other styles
3

Roobini, M. S., Selvasurya Sampathkumar, Shaik Khadar Basha, and Anitha Ponraj. "Serverless Computing Using Amazon Web Services." Journal of Computational and Theoretical Nanoscience 17, no. 8 (August 1, 2020): 3581–85. http://dx.doi.org/10.1166/jctn.2020.9235.

Full text
Abstract:
In the last decade cloud computing transformed the way in which we build applications. The boom in cloud computing helped to develop new software design and architecture. Helping the developers to focus more on the business logic than the infrastructure. FaaS (function as a service) compute model it gave developers to concentrate only on the application code and rest of the factors will be taken care by the cloud provider. Here we present a serverless architecture of a web application built using AWS services and provide detail analysis of lambda function and micro service software design implemented using these AWS services.
APA, Harvard, Vancouver, ISO, and other styles
4

Pogiatzis, Antreas, and Georgios Samakovitis. "An Event-Driven Serverless ETL Pipeline on AWS." Applied Sciences 11, no. 1 (December 28, 2020): 191. http://dx.doi.org/10.3390/app11010191.

Full text
Abstract:
This work presents an event-driven Extract, Transform, and Load (ETL) pipeline serverless architecture and provides an evaluation of its performance over a range of dataflow tasks of varying frequency, velocity, and payload size. We design an experiment while using generated tabular data throughout varying data volumes, event frequencies, and processing power in order to measure: (i) the consistency of pipeline executions; (ii) reliability on data delivery; (iii) maximum payload size per pipeline; and, (iv) economic scalability (cost of chargeable tasks). We run 92 parameterised experiments on a simple AWS architecture, thus avoiding any AWS-enhanced platform features, in order to allow for unbiased assessment of our model’s performance. Our results indicate that our reference architecture can achieve time-consistent data processing of event payloads of more than 100 MB, with a throughput of 750 KB/s across four event frequencies. It is also observed that, although the utilisation of an SQS queue for data transfer enables easy concurrency control and data slicing, it becomes a bottleneck on large sized event payloads. Finally, we develop and discuss a candidate pricing model for our reference architecture usage.
APA, Harvard, Vancouver, ISO, and other styles
5

Muller, Lisa, Christos Chrysoulas, Nikolaos Pitropakis, and Peter J. Barclay. "A Traffic Analysis on Serverless Computing Based on the Example of a File Upload Stream on AWS Lambda." Big Data and Cognitive Computing 4, no. 4 (December 10, 2020): 38. http://dx.doi.org/10.3390/bdcc4040038.

Full text
Abstract:
The shift towards microservisation which can be observed in recent developments of the cloud landscape for applications has led towards the emergence of the Function as a Service (FaaS) concept, also called Serverless. This term describes the event-driven, reactive programming paradigm of functional components in container instances, which are scaled, deployed, executed and billed by the cloud provider on demand. However, increasing reports of issues of Serverless services have shown significant obscurity regarding its reliability. In particular, developers and especially system administrators struggle with latency compliance. In this paper, following a systematic literature review, the performance indicators influencing traffic and the effective delivery of the provider’s underlying infrastructure are determined by carrying out empirical measurements based on the example of a File Upload Stream on Amazon’s Web Service Cloud. This popular example was used as an experimental baseline in this study, based on different incoming request rates. Different parameters were used to monitor and evaluate changes through the function’s logs. It has been found that the so-called Cold-Start, meaning the time to provide a new instance, can increase the Round-Trip-Time by 15%, on average. Cold-Start happens after an instance has not been called for around 15 min, or after around 2 h have passed, which marks the end of the instance’s lifetime. The research shows how the numbers have changed in comparison to earlier related work, as Serverless is a fast-growing field of development. Furthermore, emphasis is given towards future research to improve the technology, algorithms, and support for developers.
APA, Harvard, Vancouver, ISO, and other styles
6

Giménez-Alventosa, V., Germán Moltó, and Miguel Caballer. "A framework and a performance assessment for serverless MapReduce on AWS Lambda." Future Generation Computer Systems 97 (August 2019): 259–74. http://dx.doi.org/10.1016/j.future.2019.02.057.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Andi, Hari Krishnan. "Analysis of Serverless Computing Techniques in Cloud Software Framework." September 2021 3, no. 3 (August 20, 2021): 221–34. http://dx.doi.org/10.36548/jismac.2021.3.004.

Full text
Abstract:
This paper describes briefly about the concept of serverless cloud computing model, its usage in IT industries and its benefits. In the traditional model the developer is responsible for resource allocation, managing servers and owning of servers, and it included three models based upon the service such as IaaS, PaaS and SaaS. In IaaS (Infrastructure as a Service) the content storage and accessing of network is carried out by the cloud provider, SaaS (Software as a Service) here different software’s are provided to the user as a service, PaaS (Platform as a Service), the developer gets access to certain services for carrying out organizing process and run it accordingly. In serverless cloud computing, the developer need not worry about owning, management, and maintenance of servers as it is carried out by the cloud service provider. Hence by using this model, the time that is needed for a system to reach the market is very much reduced and is cost effective. Serverless architecture includes three categories namely, AWS Lambda, Azure, and Google cloud. It also includes certain challenges such as it cannot be used in the case where a process takes longer time to run and it is discussed below in this paper.
APA, Harvard, Vancouver, ISO, and other styles
8

Malawski, Maciej, Adam Gajek, Adam Zima, Bartosz Balis, and Kamil Figiela. "Serverless execution of scientific workflows: Experiments with HyperFlow, AWS Lambda and Google Cloud Functions." Future Generation Computer Systems 110 (September 2020): 502–14. http://dx.doi.org/10.1016/j.future.2017.10.029.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Bebortta, Sujit, Saneev Kumar Das, Meenakshi Kandpal, Rabindra Kumar Barik, and Harishchandra Dubey. "Geospatial Serverless Computing: Architectures, Tools and Future Directions." ISPRS International Journal of Geo-Information 9, no. 5 (May 7, 2020): 311. http://dx.doi.org/10.3390/ijgi9050311.

Full text
Abstract:
Several real-world applications involve the aggregation of physical features corresponding to different geographic and topographic phenomena. This information plays a crucial role in analyzing and predicting several events. The application areas, which often require a real-time analysis, include traffic flow, forest cover, disease monitoring and so on. Thus, most of the existing systems portray some limitations at various levels of processing and implementation. Some of the most commonly observed factors involve lack of reliability, scalability and exceeding computational costs. In this paper, we address different well-known scalable serverless frameworks i.e., Amazon Web Services (AWS) Lambda, Google Cloud Functions and Microsoft Azure Functions for the management of geospatial big data. We discuss some of the existing approaches that are popularly used in analyzing geospatial big data and indicate their limitations. We report the applicability of our proposed framework in context of Cloud Geographic Information System (GIS) platform. An account of some state-of-the-art technologies and tools relevant to our problem domain are discussed. We also visualize performance of the proposed framework in terms of reliability, scalability, speed and security parameters. Furthermore, we present the map overlay analysis, point-cluster analysis, the generated heatmap and clustering analysis. Some relevant statistical plots are also visualized. In this paper, we consider two application case-studies. The first case study was explored using the Mineral Resources Data System (MRDS) dataset, which refers to worldwide density of mineral resources in a country-wise fashion. The second case study was performed using the Fairfax Forecast Households dataset, which signifies the parcel-level household prediction for 30 consecutive years. The proposed model integrates a serverless framework to reduce timing constraints and it also improves the performance associated to geospatial data processing for high-dimensional hyperspectral data.
APA, Harvard, Vancouver, ISO, and other styles
10

Lee, Soohyun, Jeremy Johnson, Carl Vitzthum, Koray Kırlı, Burak H. Alver, and Peter J. Park. "Tibanna: software for scalable execution of portable pipelines on the cloud." Bioinformatics 35, no. 21 (May 11, 2019): 4424–26. http://dx.doi.org/10.1093/bioinformatics/btz379.

Full text
Abstract:
Abstract Summary We introduce Tibanna, an open-source software tool for automated execution of bioinformatics pipelines on Amazon Web Services (AWS). Tibanna accepts reproducible and portable pipeline standards including Common Workflow Language (CWL), Workflow Description Language (WDL) and Docker. It adopts a strategy of isolation and optimization of individual executions, combined with a serverless scheduling approach. Pipelines are executed and monitored using local commands or the Python Application Programming Interface (API) and cloud configuration is automatically handled. Tibanna is well suited for projects with a range of computational requirements, including those with large and widely fluctuating loads. Notably, it has been used to process terabytes of data for the 4D Nucleome (4DN) Network. Availability and implementation Source code is available on GitHub at https://github.com/4dn-dcic/tibanna. Supplementary information Supplementary data are available at Bioinformatics online.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "AWS Serverless"

1

Mengozzi, Federico. "Gli strumenti Serverless di AWS." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2021. http://amslaurea.unibo.it/23448/.

Full text
Abstract:
Il serverless è un trend del cloud computing che si sta diffondendo rapidamente. I cloud provider offrono tutte le risorse che servono per eseguire applicazioni. Lasciando agli sviluppatori la possibilità di concetrarsi solo sulla creazione del prodotto. In questo lavoro, dopo una breve introduzione al serverless e ai microservizi, analizzerò nel dettaglio i servizi AWS che sono alla base dello sviluppo serverless con Amazon. Offrirò due esempi, di come AWS è utilizzato in production per risolvere vecchi problemi in modi nuovi e creativi. Infine, mostrerò una semplice applicazione serverless per mostrare i vantaggi che creare architetture serverless su AWS fornisce.
APA, Harvard, Vancouver, ISO, and other styles
2

Grumuldis, Algirdas. "Evaluation of “Serverless” Application Programming Model : How and when to start Serverles." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-247625.

Full text
Abstract:
Serverless is a fascinating trend in modern software development which consists of pay-as-you-go, autoscaling services. Promised reduction in operational and development costs attracts not only startups but also enterprise clients despite that serverless is a relatively fresh field where new patterns and services continue to emerge. Serverless started as independent services which solve specific problems (highly scalable storage and computing), and now it's become a paradigm shift how systems are built. This thesis addressed questions when and how to start with serverless by reviewing available literature, conducting interviews with IT professionals, analyzing available tools, identifying limitations of serverless architecture and providing checklist when serverless is applicable. The focus was on AWS serverless stack, but main findings are generic and hold for all serverless providers serverless delivers what it promises, however, the devil is in the detail. Providers are continuously working to resolve limitations or building new services as solutions in order to make serverless the next phase of cloud evolution.
Serverless är en fascinerande trend inom nutida mjukvaruutveckling som består av pay-as-you-go, autoscaling-tjänster. Löftet om reducerade kostnader för drift och utveckling attraherar såväl startupföretag som storföretag, trots att serverless är ett relativt nytt område där nya inriktningar och tjänster fortsätter att uppkomma. Serverless började som en oberoende tjänst som löste specifika problem (högt skalbar lagring och databehandling), och har nu blivit ett paradigmskifte för hur system byggs. Denna uppsats sökte svar på frågor om när och hur man ska börja med serverless genom att granska tillgängliga publikationer, genomföra intervjuer med IT-experter, analysera tillgängliga verktyg och identifiera begränsningarna i serverless-arkitekturen. Fokus ligger på AWS serverless stack, men de huvudsakliga slutsatserna är generiska och gäller för alla serverless-leverantörer – serverless håller vad den lovar, men djävulen bor i detaljerna. Tjänsteleverantörerna jobbar oavbrutet med att lösa begränsningarna eller skapa nya tjänster och lösningar som ska göra serverless till nästa fas i molnevolutionen.
APA, Harvard, Vancouver, ISO, and other styles
3

Landin, Gustav. "AWS Lambda function performance measurement : A performance measurement of AWS Lambda functions using Serverless Framework and Express.js." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-104960.

Full text
Abstract:
Serverless is a buzzword and many organizations have already adopted serverless technologies. In 2020 the Serverless framework introduced Serverless Components, making it possible for the user to build or convert an existing application using Express.js when writing AWS Lambda functions. This study consists of a performance measurement of AWS Lambda functions using Serverless Framework and Express.js, containing different Use Cases for each application and in different time periods. The results show that there are huge differences in response time when comparing these two applications when looking at cold-starts. For the already warm containers, there are larger fluctuations for the application using the express component. For the initialization duration there were very similar results between the two applications. No significant difference between different Use Cases or time periods could be found.
APA, Harvard, Vancouver, ISO, and other styles
4

Moyer, Daniel William. "Punching Holes in the Cloud: Direct Communication between Serverless Functions Using NAT Traversal." Thesis, Virginia Tech, 2021. http://hdl.handle.net/10919/103627.

Full text
Abstract:
A growing use for serverless computing is large parallel data processing applications that take advantage of its on-demand scalability. Because individual serverless compute nodes, which are called functions, run in isolated containers, a major challenge with this paradigm is transferring temporary computation data between functions. Previous works have performed inter-function communication using object storage, which is slow, or in-memory databases, which are expensive. We evaluate the use of direct network connections between functions to overcome these limitations. Although function containers block incoming connections, we are able to bypass this restriction using standard NAT traversal techniques. By using an external server, we implement TCP hole punching to establish direct TCP connections between functions. In addition, we develop a communications framework to manage NAT traversal and data flow for applications using direct network connections. We evaluate this framework with a reduce-by-key application compared to an equivalent version that uses object storage for communication. For a job with 100+ functions, our TCP implementation runs 4.7 times faster at almost half the cost.
Master of Science
Serverless computing is a branch of cloud computing where users can remotely run small programs, called "functions," and pay only based on how long they run. A growing use for serverless computing is running large data processing applications that use many of these serverless functions at once, taking advantage of the fact that serverless programs can be started quickly and on-demand. Because serverless functions run on isolated networks from each other and can only make outbound connections to the public internet, a major challenge with this paradigm is transferring temporary computation data between functions. Previous works have used separate types of cloud storage services in combination with serverless computing to allow functions to exchange data. However, hard-drive--based storage is slow and memory-based storage is expensive. We evaluate the use of direct network connections between functions to overcome these limitations. Although functions cannot receive incoming network connections, we are able to bypass this restriction by using a standard networking technique called Network Address Translation (NAT) traversal. We use an external server as an initial relay to setup a network connection between two functions such that once the connection is established, the functions can communicate directly with each other without using the server anymore. In addition, we develop a communications framework to manage NAT traversal and data flow for applications using direct network connections. We evaluate this framework with an application for combining matching data entries and compare it to an equivalent version that uses storage based on hard drives for communication. For a job with over 100 functions, our implementation using direct network connections runs 4.7 times faster at almost half the cost.
APA, Harvard, Vancouver, ISO, and other styles
5

Ажаж, А. Ф., and Геннадий Викторович Гейко. "Исследование Web-приложения для системы управления гостиничным комплексом." Thesis, Національний технічний університет "Харківський політехнічний інститут", 2019. http://repository.kpi.kharkov.ua/handle/KhPI-Press/46909.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Andersson, Jonas. "Using React Native and AWS Lambda for cross-platform development in a startup." Thesis, Linköpings universitet, Programvara och system, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-143670.

Full text
Abstract:
When developing mobile applications, the tradition has been to write code specific (native) for each platform they are running on. Usually it’s about writing two separate applications for the biggest platforms, Android and iOS. There exist alternatives to this approach that uses the same code for different platforms. React Native is a relatively new cross-platform development framework that makes it possible to use the same code for application to Android and iOS. It also uses native UI-elements as a possible solution for performance issues that is often associated with cross-plattform development. This thesis evaluates React Native and compares it against native Android. The implementation is done by replicating the main functionality from a social media application written as a native Android application. However, the application is not made as an exact replica since that could limit the solutions in React Native. The evaluation is done in a Startup company and therefore focuses on aspects important in a Startup. Another issue when developing a mobile application is what type of backend that shall be used. Performance, scalability and complexity are all important aspects when choosing a framework or language as a base for the backend architecture.There do exist theoretical frameworks that could be used when building the backend. However, these frameworks require resources that are often missing in a Startup. AWS Lambda is a platform that claims to be a cost-effective way of building a scalable application. In this thesis AWS Lambda is evaluated to see if it can be used to create an automatically scaled backend for this type of social media application. The conclusion of the React Native evaluation is that it can be a suitable alternative to native Android development. If the team has previous experience in web development but lack experience in mobile application development it can be a wise choice since it removes the need to learn two frameworks in native Android and native iOS development. React Native is also good to fast create functional prototypes which can be shown to potential investors. The biggest drawback is performance in animations. However, there are often ways to work around that. In our case this drawback did not affect the user experience of the end application. The evaluation of AWS Lambda concludes that it is not for every project. In this thesis, the application was a bit too database heavy and therefore the autoscaling ability did not work properly. However, for a service that needs a lot of computing power, AWS Lambda could be a good fit. It could also be a suitable alternative if someone in the team has previous experience in the AWS environment.
APA, Harvard, Vancouver, ISO, and other styles
7

Bertin, Matteo. "Cross-platform and Cloud-oriented Mobile Software Development with React Native and AWS." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/18655/.

Full text
Abstract:
Nell'ultima decade il mercato mobile ha visto una rapida e costante crescita nei volumi di dispositivi mobili distribuiti nel mondo, nonché al numero di utenze, e questo trend non accenna a diminuire. In un mercato dominato dai sistemi operativi mobile Android e iOS, lo sviluppo ed il supporto di applicativi mobile per entrambe le piattaforme consente una copertura degli utenti superiore al 97%. Tuttavia, l'accesso alle risorse necessarie per lo sviluppo di applicativi mobile cross-piattaforma e con funzionalità di cloud computing risulta complessa, se non proibitiva per costi e tempistiche progettuali. Tradizionalmente, ciascuna piattaforma mobile richiederebbe l'utilizzo di linguaggi di programmazione specifici per lo sviluppo di applicativi. La scelta del framework di sviluppo React Native ha consentito una rapida prototipizzazione di un applicativo mobile per le piattaforme Android ed iOS. La sua adozione ha consentito inoltre l'ingente riutilizzo di codice tra le piattaforme. Non è stata necessaria la conoscenza pregressa di programmazione nativa Android o iOS, favorendo inoltre eventuali contributi futuri alla baseline del progetto da parte di sviluppatori web senza requisiti di programmazione mobile. La configurazione e l'accesso alle API dei servizi di back-end da parte del client React Native è stata eseguita con successo per mezzo del framework AWS Amplify. Il back-end è costituito da uno stack di webservices AWS, comprendente AWS Amazon API Gateway, AWS Lambda, AWS Amazon DynamoDB, AWS Amazon Cognito e AWS Amazon S3. La realizzazione di un applicativo Android nativo, avente funzionalità equivalenti a quello realizzato con React Native e connesso al medesimo back-end AWS, consentirà l'esecuzione dei test comparativi tra i due differenti framework di sviluppo mobile. Tutti i test verranno condotti su di un device fisico avente sistema operativo Android. Verrà quindi riportata la descrizione dei test e dei risultati ottenuti, assieme alla loro valutazione.
APA, Harvard, Vancouver, ISO, and other styles
8

Eriksson, Pontus. "Building a System for Driving and Rest Times from Activity Changes." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-450875.

Full text
Abstract:
This project explores an improved design for a system that tracks drive and rest time data for heavy vehicle drivers. Tracking rest and driving time data for drivers of heavy vehicles is important since it allows for the drivers to ensure that they are following the laws related to how often they must take breaks. The system built in this project is external to the vehicles. It relies on sending smaller status updates then previously, thus decreasing the data required to track the drive and rest times. The system was evaluated in terms of how much data it saves compared to a system that sends full status updates, it was also evaluated on how the cost scales with an increased load on the system.
APA, Harvard, Vancouver, ISO, and other styles
9

Principini, Gianluca. "Data Mesh: decentralizzare l'ownership dei dati mantenendo una governance centralizzata attraverso l'adozione di standard di processo e di interoperabilità." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2021.

Find full text
Abstract:
Nel corso degli ultimi due decenni i progressi delle tecnologie cloud hanno consentito alle imprese di poter puntare su nuovi paradigmi implementativi per le Data Platform. Tuttavia, questi sono caratterizzati da centralizzazione e monoliticità, stretto accoppiamento tra gli stage di pipeline e da un'ownership dei dati centralizzata in team di data engineers altamente specializzati, ma lontani dal dominio. Queste caratteristiche, con l'aumentare delle sorgenti e dei consumatori dei dati, evidenziano un collo di bottiglia che rischia di pregiudicare la buona riuscita di progetti che spesso comportano grossi investimenti. Problemi simili sono stati affrontati dall'ingegneria del software con l'adozione del Domain Driven Design, con il passaggio da architetture monolitiche ad architetture orientate ai servizi e sistemi basati su microservizi, che ben si prestano ad operare in ambienti cloud. Nella tesi, svolta nel contesto aziendale di Agile Lab, viene illustrato come le stesse migliorie possano essere applicate alla progettazione delle Data Platform adottando il paradigma del Data Mesh, in cui ciascun dominio espone dati analitici attraverso i Data Product. Per dimostrare come sia possibile ridurre gli attriti nella predisposizione dell'infrastruttura di un Data Product attraverso l'adozione di standard di processo e di interoperabilità, che guidino l'interazione tra le diverse componenti all'interno della piattaforma, viene illustrata la progettazione e l'implementazione di un meccanismo di Infrastructure as Code per le risorse di observability di quest'ultimo.
APA, Harvard, Vancouver, ISO, and other styles
10

Carli, Cristian. "Un esempio reale: dal mondo on premise a quello cloud su Amazon AWS." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2021. http://amslaurea.unibo.it/23087/.

Full text
Abstract:
L’obiettivo di questa tesi è quello di fornire una panoramica sul mondo del cloud computing sfruttando come esempio un progetto reale a cui ho lavorato presso l’azienda dove sono assunto: Touchwindow. Il progetto a cui ho preso parte nello sviluppo consiste nella creazione di spazi interattivi all’interno dei ristoranti della nota catena McDonald’s. In circa 3 anni di sviluppo ho realizzato 5 videogiochi, ho implementato la Web Api sul cloud utilizzando i servizi serverless offerti dal provider Amazon AWS, ho realizzato il sistema di aggiornamento basato su storage cloud, ho implementato un sistema di scrittura delle statistiche di gioco su Mongo Db e curato l’infrastruttura cloud in tutti i dettagli. Nel proseguo di questa tesi si vedranno tutte le parti che ho realizzato con particolare focus sul mondo del cloud computing, i suoi benefici e gli strumenti che può offrire. Si vedrà come realizzare una Web Api completamente serverless in grado di scalare le risorse in automatico, spazi di memoria a banda illimitata, database gestiti automaticamente e servizi di computazione istantanei senza server dedicati.
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "AWS Serverless"

1

Serverless Architectures on AWS. Manning Publications Company, 2019.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Sbarski, Peter. Serverless Architectures on AWS: With examples using AWS Lambda. Manning Publications, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

AWS Lambda in Action: Event-driven serverless applications. Manning Publications, 2016.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Zanon, Diego. Building Serverless Web Applications: Develop scalable web apps using the Serverless Framework on AWS. Packt Publishing - ebooks Account, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Elger, Peter Peter, and Eoin Eoin Shanaghy. AI As a Service: Serverless Machine Learning with AWS. Manning Publications Company, 2020.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Serverless Applications with Node.js: Using AWS Lambda and Claudia.js. Manning Publications, 2019.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Barguzar, Abdulwahid Abdulhaque. Building Serverless Python Web Services with Zappa: Build and deploy serverless applications on AWS using Zappa. Packt Publishing, 2018.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Klems, Markus. AWS Lambda Quick Start Guide: Learn how to build and deploy serverless applications on AWS. Packt Publishing, 2018.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Dabit, Nader. Full Stack Serverless: Modern Application Development with React, AWS, and GraphQL. O'Reilly Media, 2020.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Chowhan, Kuldeep. Hands-On Serverless Computing: Build, run and orchestrate serverless applications using AWS Lambda, Microsoft Azure Functions, and Google Cloud Functions. Packt Publishing, 2018.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "AWS Serverless"

1

Pothecary, Ryan. "Serverless." In Running Microsoft Workloads on AWS, 139–59. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-6628-1_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Vijayakumar, Thurupathan. "Serverless APIs." In Practical API Architecture and Development with Azure and AWS, 133–58. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-3555-3_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mardan, Azat. "Serverless Node with AWS Lambda." In Practical Node.js, 473–94. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-3039-8_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Murphy, Seán, Leonardas Persaud, William Martini, and Bill Bosshard. "On the Use of Web Assembly in a Serverless Context." In Agile Processes in Software Engineering and Extreme Programming – Workshops, 141–45. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58858-8_15.

Full text
Abstract:
Abstract This paper considers how WASM can be run in different serverless contexts. A comparison of different serverside WASM runtime options is considered, specifically focused on , and . Next, different options for running WASM within two serverless platforms – Openwhisk and AWS Lambdai – are compared. Initial results show that a solution which uses the built-in WASM supports is found to work better than using the dedicated WASM runtimes but this has limitations and providing more direct integration with WASM runtimes should be explored further.
APA, Harvard, Vancouver, ISO, and other styles
5

Grzesik, Piotr, and Dariusz Mrozek. "Serverless Nanopore Basecalling with AWS Lambda." In Computational Science – ICCS 2021, 578–86. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-77964-1_44.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Choudhary, Brijesh, Chinmay Pophale, Aditya Gutte, Ankit Dani, and S. S. Sonawani. "Case Study: Use of AWS Lambda for Building a Serverless Chat Application." In Proceeding of International Conference on Computational Science and Applications, 237–44. Singapore: Springer Singapore, 2020. http://dx.doi.org/10.1007/978-981-15-0790-8_24.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "AWS Serverless"

1

Ephanov, A. "Going Serverless: Geostatistical Inversion on AWS." In Digital Subsurface Conference in Latin America. European Association of Geoscientists & Engineers, 2021. http://dx.doi.org/10.3997/2214-4609.202181008.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Ortiz, Ariel. "Architecting Serverless Microservices on the Cloud with AWS." In SIGCSE '19: The 50th ACM Technical Symposium on Computer Science Education. New York, NY, USA: ACM, 2019. http://dx.doi.org/10.1145/3287324.3287533.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Rinta-Jaskari, Eetu, Christopher Allen, Tamara Meghla, and Davide Taibi. "Testing Approaches And Tools For AWS Lambda Serverless-Based Applications." In 2022 IEEE International Conference on Pervasive Computing and Communications Workshops and other Affiliated Events (PerCom Workshops). IEEE, 2022. http://dx.doi.org/10.1109/percomworkshops53856.2022.9767473.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Nicolas da Silva, Matheus, and Marcus Carvalho. "Análise de Mecanismos de Serverless Computing em Ambientes de Nuvens Computacionais." In XXXVII Simpósio Brasileiro de Redes de Computadores e Sistemas Distribuídos. Sociedade Brasileira de Computação - SBC, 2019. http://dx.doi.org/10.5753/sbrc_estendido.2019.7791.

Full text
Abstract:
The objective of this work is to present the analysis of one of the most promising cloud application paradigms that emerged in this model - Serverless Computing. Being a new approach to cloud computing, it is much discussed because of its characteristics in the world of computer systems industry. Based on the exploratory research, this work was developed with the purpose of investigating the characteristics of serverless computing and performing a quantitative experiment in the AWS Lambda environment, investigating a phenomenon present in this approach, cold-start.
APA, Harvard, Vancouver, ISO, and other styles
5

Gandhi, Saloni, Anuja Gore, Sakshi Nimbarte, and Jibi Abraham. "Implementation and Analysis of a Serverless Shared Drive with AWS Lambda." In 2018 4th International Conference for Convergence in Technology (I2CT). IEEE, 2018. http://dx.doi.org/10.1109/i2ct42659.2018.9058237.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Kaplunovich, Alex, and Yelena Yesha. "Automatic Hyperparameter Optimization for Arbitrary Neural Networks in Serverless AWS Cloud." In 2021 12th International Conference on Information and Communication Systems (ICICS). IEEE, 2021. http://dx.doi.org/10.1109/icics52457.2021.9464618.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pelle, István, János Czentye, János Dóka, and Balázs Sonkoly. "Dynamic latency control of serverless applications operated on AWS lambda and greengrass." In SIGCOMM '20: Annual conference of the ACM Special Interest Group on Data Communication on the applications, technologies, architectures, and protocols for computer communication. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3405837.3411381.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Linebarger, John. "A Smorgasbord of Serverless Technologies." In Proposed for presentation at the AWS/DOE Virtual Fusion VIII Conference held October 27-28, 2020 in Albuquerque, NM. US DOE, 2020. http://dx.doi.org/10.2172/1830933.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Reisman, Ronald. "Blockchain Serverless Public/Private Key Infrastructure for ADS-B Security, Authentication, and Privacy." In AIAA Scitech 2019 Forum. Reston, Virginia: American Institute of Aeronautics and Astronautics, 2019. http://dx.doi.org/10.2514/6.2019-2203.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Reisman, Ronald. "Correction: Blockchain Serverless Public/Private Key Infrastructure for ADS-B Security, Authentication, and Privacy." In AIAA Scitech 2019 Forum. Reston, Virginia: American Institute of Aeronautics and Astronautics, 2019. http://dx.doi.org/10.2514/6.2019-2203.c1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'AWS Serverless' for particular source types:
Journal articles Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography