BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage FaaS Content on InfoQ

Articles

RSS Feed
  • AWS Lambda under the Hood

    Mike Danilov, a senior principal engineer at AWS, presented on AWS Lambda and what is under the hood during QCon San Francisco 2023. This article represents the talk, which will start with an introduction to Lambda itself to outline the key concepts of the service and its fundamentals, which will facilitate a deep dive into the understanding of the system.

  • Containers and Serverless—Rivals or Cohorts?

    This article will try to decode these technologies and explore how developers should consider containers or serverless functions within their tech stack. For example, if your application has a longer startup time, then a container would suit the need better. Highly efficient stateless functions that need to scale up and down massively would benefit from running serverless functions.

  • Lambda Throttling - How to Avoid It?

    This article aims to explain best practices if you have throttled your application and services and suggestions for how to handle these cases. We performed an in-house experiment at Jit (a SaaS-based DevSecOps platform) built on serverless to learn how our application behaves.

  • Choosing the Right Cloud Infrastructure for Your SaaS Start-up

    As a solutions architect, I have been designing SaaS applications for years and I have seen start-ups struggle to find the right cloud infrastructure and improve their product offering. These experiences prompted me to write this article as a tool to help companies make a pragmatic fact and data-driven decision.

  • Building Workflows with AWS Step Functions

    AWS Step Functions use a state machine to represent the workflow. A workflow consists of a set of tasks, each of which represents a discrete activity to be performed. Each task is defined by a state of the state machine. In this article, we will learn about the main concepts of AWS Step Functions and apply those to build a workflow for a sample business process: Order Fulfillment.

  • Why AWS Lambda Pricing Has to Change for the Enterprise

    AWS Lambda users pay only when their code is run. This can result in massive cost savings over long-running workloads. The advantages start to disappear quickly when AWS Lambda is employed for batch processing. Enterprises can gain significantly from the scalability of FaaS - yet a price comparison between EC2, Lambda, and Fargate, the AWS-managed container service, reveals an ugly truth.

  • Serverless Functions for Microservices? Probably Yes, But Stay Flexible to Change

    When designing cloud-native systems, it is important to accommodate freedom to change deployment strategy, from FaaS to containers or VMs, for potentially significant savings on cloud bills.

  • 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.

  • 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.

BT