“Even simple serverless applications have complex architecture diagrams”, so what?
I often hear people complain that even simple serverless architectures look complex on paper.
Let me tell you why this misses the point.
I often hear people complain that even simple serverless architectures look complex on paper.
Let me tell you why this misses the point.
I have some exciting news to share with you. That after some initial delays, the AppSync Masterclass is now open for Early Access with 40% launch discount. First of all, thank you so much for your patience, it’s taken us a bit longer than we expected but we’re here, at last. You can purchase the …
AppSync has built-in logging integration with CloudWatch Logs (see here for more details on the logging options). You can set the Field resolver log level to NONE, ERROR or ALL. When the field resolver log level is set to NONE or ERROR, you don’t get a lot of value from the AppSync logs. For example, …
I previously wrote about five reasons you should consider AppSync over API Gateway. One thing that API Gateway supports but you can’t do with AppSync out-of-the-box yet is custom domain names. Your shiny new AppSync API is available at XYZ.appsync-api.us-east-1.amazonaws.com/graphql, but you really want people to use your own domain instead because dev.example.com/graphql is much …
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 »
I have been working on a large AppSync project for a client these past few months. The initial version of the app was built in just a few weeks, but the client has commissioned additional features and the project has kept growing. At the time of writing, this project has over 200 AppSync resolvers and …
How I scaled an AppSync project to 200+ resolvers Read More »
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 »
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 …
I have been working with a US client to build a first-of-its-kind application to manage your consent to share your data amongst healthcare providers in your state. The project falls within HIPAA, so we need to meet all the HIPAA compliance requirements, including having a full history of the user data. To meet that audit …
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 »
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.