2024 was the year I got back and amongst the community, and it felt great to be back! If numbers tell a story, then my 2024 numbers is the story of a busy bee :-P - launched 2 MVPs for clients - 52% newsletter open rate - 350+ workshop students - $10,000 wasted on ads ? - 33 blog posts - 353k blog views - 255k blog visitors - 13k newsletter readers - 50 newsletter issues - 31 public talks - 16 podcast episodes, 17k listens, 26k views - 34 YouTube videos, 130k views, 6500 hours watched - 420 LinkedIn posts [...]

There is more than one way to test user journeys that span multiple bounded contexts. Your choice depends on organizational structure, team responsibilities, and the maturity of your testing practices. Ultimately, every part of the user journey should be tested, whether it's done piecemeal by individual teams or centrally by a QA/cross-functional team. In this article, let's look at several ways you can approach this problem, depending on if you have full-stack teams or specialised frontend and backend tea[...]

The ability to invalidate a user's session with immediate effect is a common enterprise requirement. However, this goes against how token-based authentication is designed to work. JWT tokens are stateless and are typically short-lived (for security reasons) but can be refreshed with refresh tokens. So, is it possible to invalidate Cognito-issued JWT tokens? The short answer is no. The long answer is yes, you can achieve this effect with some work and some performance overhead. How? Well, come in and find [...]

If you’re using CDK, you should use L3 constructs to encapsulate common patterns and best practices in your architecture. However, sometimes you'd find a 3rd-party L3 construct that does most of what you want, but you need to customize how it configures some of its resources. That can be tricky because you don't own the source code, and the construct author might not be willing to make the changes you want. In this article, let me show you an easy and effective way to do this without having to clone and ma[...]

Here is the biggest mistake many teams make when they try to adopt serverless and why they ultimately fail. Don't make the same mistake. The post I’m sorry, but the way you adopt serverless is wrong appeared first on theburningmonk.com.