Serverless

Choreography vs Orchestration in the land of serverless

Choreography and Orchestration are two modes of interaction in a microservices architecture. In orchestration, there is a controller (the ‘orchestrator’) that controls the interaction between services. It dictates the control flow of the business logic and is responsible for making sure that everything happens on cue. This follows the request-response paradigm. In choreography, every service …

Choreography vs Orchestration in the land of serverless Read More »

AppSync: how to inject table names into DynamoDB batch & transact operations

When working with CloudFormation, AWS recommends not to give explicit names to resources and let CloudFormation name them for you. This has several advantages: It’s harder for attackers to guess resource names such as S3 buckets or DynamoDB tables. You can deploy the same stack multiple times to the same account. This is useful when …

AppSync: how to inject table names into DynamoDB batch & transact operations Read More »

Are Lambda-to-Lambda calls really so bad?

TL;DR – Lambda-to-Lambda calls are generally a bad idea except for some select use cases, such as: You’re running the Apollo server in a Lambda function. To offload secondary responsibilities to another function by invoking asynchronous (that is, using Event as InvocationType). Avoid synchronous lambda-to-lambda calls If you utter the words “I call a Lambda …

Are Lambda-to-Lambda calls really so bad? Read More »

Production-Ready Serverless is back (with improved curriculum)!

My 4-week Production-Ready Serverless workshop is back! With an improved and more comprehensive curriculum based on student feedback from the last run in May, when over 50 students from around the world took part. This is a hands-on workshop where you will learn best practices for building serverless applications by building an e-commerce solution from …

Production-Ready Serverless is back (with improved curriculum)! Read More »

AppSync: how to error on DynamoDB conditional check failures

TL;DR To make an AppSync DynamoDB resolver throw exceptions on conditional check errors, we need to check $context.error in the response mapping template ourselves. Like this: #if ( $ctx.error ) #if ( $ctx.error.type.equals(“DynamoDB:ConditionalCheckFailedException”) ) $util.error(“your error message”) #else $util.error($ctx.error.message, $ctx.error.type) #end #end $utils.toJson($context.result) And now, the longer version. The problem AppSync lets us perform DynamoDB …

AppSync: how to error on DynamoDB conditional check failures Read More »

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close