InfoQ Homepage Serverless Content on InfoQ
-
Server-Side Wasm: Today and Tomorrow - Q&A with Connor Hicks
At QCon this year, Connor Hicks presented the opportunities linked to using Web Assembly outside of the browser. Hicks addressed current and future server-side use cases for WebAssembly. He explained how Wasm and its ecosystem allow developers to craft serverless applications by declaratively composing serverless functions written in different languages.
-
Why the Serverless Revolution Has Stalled
Are traditional servers dead? Far from it. This article looks at why, despite serverless models finding great utility in specific circumstances, there's a barrier to more widespread adoption.
-
Azure + Spring Boot = Serverless - Q&A with Julien Dubois
Microsoft seems to prove over and over again its focus on cloud and the Java ecosystem is the new normal. Even though Java has been amongst the supported languages for Azure functions for some time now, Julien Dubois experimented with Spring Boot and Azure to see what this combination means for Azure serverless computing. InfoQ reached out to him to explore further his experience on this topic.
-
The Right Way of Tracing AWS Lambda Functions
With an emphasis on distributed tracing, this article discusses best practices for gaining and leveraging observability into AWS Lambda functions.
-
Software Architecture and Design InfoQ Trends Report—April 2020
An overview of how the InfoQ editorial team sees the Software Architecture and Design topic evolving in 2020, with a focus on fundamental architectural patterns, framework usage, and design skills.
-
Adoption of Cloud-Native Architecture, Part 1: Architecture Evolution and Maturity
In this article, authors Srini Penchikala and Marcio Esteves discuss what organizations should assess when adopting cloud native architectures for hosting their applications on cloud. It focuses on architecture hosting models. They also discuss how architecture patterns like microservices, containers, serverless, and service mesh can help with organizational adoption of cloud native solutions.
-
Q&A with Gojko Adzic on the Book Running Serverless
In the book Running Serverless, Gojko Adzic introduces the basic concepts of serverless including detailed step-by-step instructions to get started on AWS, but he also goes beyond the basics and explains subjects like storage, session state, and event handling.
-
Kubernetes Workloads in the Serverless Era: Architecture, Platforms, and Trends
Explore how microservices architecture has evolved into cloud-native architecture, where many of the infrastructure concerns are provided by Kubernetes in combination with additional abstractions provided by service mesh and serverless frameworks. In addition, the serverless ecosystem is evolving by exploring standard and open packaging, runtimes, and event formats.
-
Understanding Serverless: Tips and Resources for Building Servicefull Applications
There are still many misconceptions and concerns regarding serverless solutions. Vendor lock-in, tooling, cost management, cold starts, monitoring and the development lifecycle are all hot topics where serverless technologies are concerned. This article shares tips and resources to guide serverless newcomers towards building powerful, flexible and cost-effective serverless applications.
-
Four Techniques Serverless Platforms Use to Balance Performance and Cost
There are two aspects that have been key to the rapid adoption of serverless computing: the performance and the cost model. This article looks at those aspects, the tradeoffs, and opportunity ahead.
-
Architecture and Design InfoQ Trends Report - January 2019
An overview of how the InfoQ editorial team sees the “architecture and design” (A&D) topic evolving in 2019, which focuses on fundamental architectural patterns, framework usage, and design skills.
-
The Serverless Sea Change
This article defines and explains how serverless is different from other application architectures and then walks through a "proof" of sorts to show that serverless application architectures, when done properly, are superior to non-serverless architectures. Finally, it concludes with a number of rules of thumb to help architects and developers realize the benefits of serverless.