Weekly update 47
Tags: me, weeklyupdate
Published: 2020-08-15 15:05:42

---
title: Weekly update 47
published: true
date: 2020-08-14 23:44:00 UTC
tags: Me,WeeklyUpdate
canonical_url: https://theburningmonk.com/2020/08/weekly-update-47/
---

Hi, welcome to another weekly update!

### Real-World Serverless podcast

Since the last update, we have 4 new episodes for you:

- [#21: From K8 to Serverless at Wealth Wizards](https://www.buzzsprout.com/877747/4153682)
- [#22: Real-World Serverless with Gojko Adzic](https://www.buzzsprout.com/877747/4218644)
- [#23: Serverless at Alma Media with Ari Palo](https://www.buzzsprout.com/877747/4615985)
- [#24: Serverless at Stedi with Zack Kanter](https://www.buzzsprout.com/877747/4615988)

### New blog posts

[**Choreography vs Orchestration in the land of serverless**](https://dev.to/aws-heroes/choreography-vs-orchestration-in-the-land-of-serverless-f58). In this post, I compare and contrast the two modes of interaction within a microservices architecture – orchestration and choreography. Both have strong trade-offs. And while choreography is great at building loosely-coupled systems, it distributes the business all over the place, making it harder to understand the system behaviour end-to-end. The TL;DR is that, when it comes to implementing business workflows, you _should prefer orchestration within the bounded context of a microservice, but prefer choreography between bounded contexts_.

[**Five reasons you should consider AppSync over API Gateway**](https://lumigo.io/aws-serverless-ecosystem/aws-appsync-five-reasons-you-should-consider-it-over-api-gateway/). API Gateway is the de facto way to build APIs using serverless technologies on AWS. However, I have really grown to like AppSync and the productivity it affords me, which (amongst other things) has allowed me to [build the backend for a new social network in just a few weeks](https://www.youtube.com/watch?v=evsz__BDprs). And in post, I shared 5 reasons that you should seriously consider using AppSync and GraphQL instead for your next API.

[**How I scaled an AppSync project to 200+ resolvers**](https://dev.to/aws-heroes/how-i-scaled-an-appsync-project-to-200-resolvers-38ja). A common problem people run into as their AppSync API becomes more complex is that they’ll run into the 200 resources limit on CloudFormation. I worked on a client project recently where the AppSync project grew to over 200 resolvers and 600 CloudFormation resources. In this post, I discussed the evolution of my strategy for splitting this project into nested stacks so it can continue to grow as the business demands it.

[**AppSync: how to inject table names into DynamoDB batch & transact operations**](https://dev.to/aws-heroes/appsync-how-to-inject-table-names-into-dynamodb-batch-transact-operations-2l0a). This is yet another common problem that people run into when working with AppSync. Fortunately, the solution is fairly straight forward when you use the Serverless framework and the serverless-appsync-plugin to manage your resolvers and templates.

[**Debugging AWS Lambda timeouts**](https://lumigo.io/blog/debugging-aws-lambda-timeouts/). Timeouts are one of the trickier problems to debug with Lambda. For starters, they get swallowed up with other generic errors and you don’t get an error log message from your application, which makes them quite hard to spot. Also, it can be difficult to track down on which operation was responsible for causing your function to timeout, especially if your function has to communicate with multiple systems. In this post, I outlined several ways you can quickly detect Lambda timeouts and find the root cause.

### Upcoming webinar

I’m running a [free webinar](https://info.lumigo.io/webinar-debugging-aws-lambda-timeouts) on 19th August on how to debug and mitigate AWS Lambda timeouts. During the session, I will demo the techniques discussed in the aforementioned blog post, and also show you a simple technique (with just a few lines of code) that can mitigate timeouts altogether in many cases.

[![](https://theburningmonk.com/wp-content/uploads/2020/08/img_5f37219790001.png)](https://info.lumigo.io/webinar-debugging-aws-lambda-timeouts)

You can register for the session [here](https://info.lumigo.io/webinar-debugging-aws-lambda-timeouts), and I hope to see you there!

### Upcoming workshop

And of course, don’t forget that my [**Production-Ready Serverless workshop**](https://homeschool.dev/class/production-ready-serverless/?utm_source=Yan&utm_medium=blog) is coming back on September 1st!

[![](https://theburningmonk.com/wp-content/uploads/2020/07/img_5f2292bd57b26.png)](https://homeschool.dev/class/production-ready-serverless/?utm_source=Yan&utm_medium=blog)

It’s still not too late to [**register**](https://homeschool.dev/class/production-ready-serverless/?utm_source=Yan&utm_medium=blog) and learn how to build production-ready serverless applications, including:

- how to choose the right authentication method for API Gateway
- API Gateway best practices
- testing strategies for serverless applications
- how to build event-driven architectures with Lambda and EventBridge
- how to include SNS & EventBridge in end-to-end tests
- how to handle secrets securely
- security best practices for serverless applications
- how to build observability into your application so you can debug problems in production
- how to right-size memory size to get the best performance and cost
- costly mistakes you need to watch out for and avoid in your serverless architecture

Oh, and don’t forget, as a reader for this blog you get a special **15% discount** with the code **yanprs15**.

If you prefer a more instructor-led workshop, instead of studying by yourself, then I’m also running a 2-day, instructor-led version of the same workshop on **October 8th-9th**. Click [**here**](https://www.eventbrite.co.uk/e/production-ready-serverless-2-days-incl-vat-tickets-88733037905) for more details and to register, and the same **yanprs15** promo code is also valid for this workshop too.

### AWS updates

AWS made some pretty significant announcements recently, so I want to recap a few that might interest you here.

- **[Lambda now supports Amazon MSK (managed Kafka) as an event source](https://aws.amazon.com/about-aws/whats-new/2020/08/aws-lambda-now-supports-amazon-managed-streaming-for-apache-kafka-as-an-event-source/)** similar to how Kinesis works.
- **[Massive update on Step Functions](https://aws.amazon.com/blogs/aws/aws-step-functions-adds-updates-to-choice-state-global-access-to-context-object-dynamic-timeouts-result-selection-and-intrinsic-functions-to-amazon-states-languages/)** – including new choice state operators, access to context object ($$) anywhere,  string interpolation.
- **[AppSync adds direct Lambda resolver](https://aws.amazon.com/blogs/mobile/appsync-direct-lambda/)**, removing the need for custom VTL templates.
- AppSync allows you to use $context.source in cache keys, so you can add caching to nested resolvers too.

### Thank you to my patrons

Finally, I want to give a shout out to my patrons:

_Andre Silva, Bala Chalasani, Boseok In, Dome Jantaphat, Dragan Cabarkapa, Ebru Cucen, Efi Merdler-Kravitz, Eric Allam, Hrafnkell Palsson, Jermaine Watkins, Jon Barber, Jonathan Kosgei, Jürgen Wagner, Kevin Woods, Marko @ Serverless Life, Michael J Lyons, Michael Wills, Peter Miller, Shawn MacIntyre, Tajinder Singh, Tendies123, Will Saunders, Yinan Xue_

Thank you guys so much for your continued support!

---

The post [Weekly update 47](https://theburningmonk.com/2020/08/weekly-update-47/) appeared first on [theburningmonk.com](https://theburningmonk.com).

 ![](http://feeds.feedburner.com/~r/theburningmonk/~4/PsCPSjVtWOw)