site-logo

JAWS PANKRATION 2024

site-logo
HomeNewsTimetableCfPCommitteePromotionFollow UpPrivacy Policy

Simplifying AWS Architectures: Exploring Lambda-less Solutions

Lv200

Lv200

8/24/2024 21:20 (UTC)
Session Info

Nowadays serverless architecture goes beyond Lambda. And Lambda-less direct integrations are becoming popular too.

In this talk we will look into the Lambda-less direct integrations and how they can impact your system architecture for performance, cost and maintenance.

Pubudu Jayawardana

Pubudu Jayawardana

- AWS Community Builders -

Session Category
Application integration
Computing
etc
AWS Services
Lambda
APIGW
SQS
SNS
S3
etc
Session Materials
    Session Archive
    Session Summary (by Amazon Bedrock)
      The speaker discusses Lambda-less or direct integrations in AWS, which allow developers to replace some Lambda functions with native AWS features. This approach further delegates maintenance responsibilities, reducing the need to manage code and runtime environments. Two examples are provided: 1. API Gateway: Instead of using a Lambda function to transform incoming requests and put data into a DynamoDB table, developers can use direct integration. This involves changing the API integration type to AWS service, specifying parameters, and using Velocity Template Language (VTL) to transform the request. 2. Step Functions: Direct integration can replace Lambda functions for calling specific AWS services within state machine executions. Step Functions now support SDK integration for around 220 AWS services, eliminating the need for intermediate Lambda functions. Advantages of direct integrations include: - Simplified architecture - Lower execution costs - Reduced total cost of ownership - Improved performance for high-volume calls - No impact on Lambda quotas Disadvantages include: - Difficulty in testing integrations - Complexity of VTL and lack of developer tooling - Potential for hidden business logic in mapping templates - Challenges in debugging The speaker advises that direct integrations are suitable for static functionality without complex business logic. However, the choice between Lambda and direct integrations depends on the specific use case and current needs. The presentation concludes by acknowledging that no architecture is perfect, and developers should choose the most suitable solution for their particular situation.

    Back

    ©JAWS-UG (AWS User Group - Japan). All rights reserved.