Darryl R.’s Post

Ever deployed on a Friday? Or refactored code without tests? Let’s be honest, we’ve all been there! Patryk Kaczmarek is turning those classic developer mishaps into something productive with a fun service to log your fails and lessons learned. In Part 2 of his step-by-step tutorial series, discover how to level up a #serverless API on #AWS with #DynamoDB for data persistence—all powered by #Terraform. 👉 Read the blog post here: https://lnkd.in/dNXHxc7e #AWSLambda, #ServerlessComputing, #DevOpsTutorial, #DynamoDB

Using GraphQL for your API is a great approach in many cases compared to using a more traditional REST API. Using services like AppSync on AWS simplifies using GraphQL. Typed languages like TypeScript have become quite popular in recent years and people using those want to be able to use types whenever possible. There is a really neat tool called “GraphQL Code Generator” which can take a GraphQL schema and generate code from it - including types. The following article from Florian Fuchs shows how these tools can be used to achieve better type safety with AWS Lambda resolver code. https://lnkd.in/eHp6F8hi

🔥 Exciting news from 6 months ago! 🎉 🤔 In case you missed it, we introduced the Amplify GraphQL API as a CDK construct – and it's been a game-changer ever since! 🔥 ✨ Experience the convenience of a single source-of-truth for all your API and data needs 🚀 With access to L2 and L1 constructs, building powerful queries and mutations has never been easier 💻 Say goodbye to cold starts with seamless query and mutation execution 📢 Enjoy real-time updates and collaboration with PubSub capabilities 🛠️ Generate client library code effortlessly with built-in codegen ⚙️ Achieve parity with the GraphQL transformer for smooth integration. Even though it's been around for a while, the #Amplify #GraphQL API continues to revolutionize API development. If you haven't already, now's the perfect time to dive in! ➡ Learn more: https://go.aws/3Q6aqP6 #graphQL #amplify #CDK #APIDevelopment #aws #awscommunity

📌 Idempotency : A certain operation can be applied many times , without changing the result after the fist time the operation is applied, which means that operation can be retransmitted or retired with no additional side effort. ✅ Idempotency is particularly important in distributed systems, where messages may be retried due to failures, timeouts, or other issues. Idempotency ensures the system remains consistent without unintended side effects, even if a request is duplicated or repeated. ↗ When a user found API call failed, how can we handle it , and it can be depend on what are building and choose one of the following ways to handle it : 1. we ignore and more forward ; 2. we pass the observation error to the user ; 3. we retry on our own 🔗 Where can duplication occurs: Duplication caused by transmission issues, Duplication caused by receiver issues and Duplication caused by service issues. ✴ Idempotency key(token) : which is used to **retry** method to meet impotency API call, which can be common passed through **Request Header** or **Query Parameter**. 🎉 When you use **AWS Lambda** to build your distribute systems, you can consider using Powertools Idempotency utility  to make you Lambda functions idempotent. The following post from Rahul Pulikkot Nath give us one example about how to did it . https://lnkd.in/g-H9yqpv

Many AWS services support direct integrations with other ones. In the cases where this isn’t supported people usually put an AWS Lambda function in between. When API Gateway is used and needing to interact with other services directly you can use Mapping Templates which are blocks of Velocity Template Language (VTL) code. Many people try to avoid VTL but if the logic isn’t too complicated it is worth trying out in many cases. This article from Arpad Toth shows how you can interact directly with DynamoDB from API Gateway without having a Lambda function in the middle and improve performance. https://lnkd.in/ezhNw4Gi

About a year ago AWS added some nice improvements to logging with Lambda functions. One of the improvements was the ability to pick what Cloudwatch Log Group your function logs go to. This change makes it easier to aggregate logs from multiple functions. There will likely be cases where you have related Lambda functions that are part of a bigger solution. They could be processing various stages of a transaction. Being able to put the logs of all these together in the same group will make it much easier to track the overall flow and debug issues. In the article below, Girish Bhatia shows how to set this up and help debug/trace the flow of multiple Lambda function invocations. https://lnkd.in/eSSRskwe

Seamless Integration: Connecting AWS Lambda to RDS and Writing Data Effortlessly https://lnkd.in/e-ksKCK9

Learn by example! Using AWS #serverless components to build a data processing pipeline is a really good fit in many cases. Tools like Glue and Athena combined with AWS Lambda, S3, API Gateway and more can be used to build a nice platform. Here Dr. Yaroslav Zhbankov details how to set all this up using GitHub Actions and Terraform Infrastructure as Code and he even includes the source code in a GitHub repo. Explore the code and try it out for yourself. Maybe this will be the start of a similar project you have been thinking about. https://lnkd.in/eUEZ-gdn

Excited to see published this two-parts blog post I co-wrote with my colleague Stefano Sandona'! We describe in detail how to implement AWS Lake Formation third party services and custom applications integration. In part 1, we lay out the theoretical background and create a sample analytical engine with AWS #lambda. In part 2, we create and deploy a web application as the front-end for the engine, we use AWS #amplify with a GraphQL API implemented with AWS #appsync. Full code is provided, so you can try and test the solution in your accounts. AWS Lake Formation third-party services integration is perfect for customers and partners alike that want to leverage AWS data platforms' governance and security layers. part 1: https://lnkd.in/dWURvipZ part 2: https://lnkd.in/dAxfaNhu Let us know what you think :)

In this post I used terraform to create a graphql api using AWS AppSync, and we used JavaScript instead of Apache Velocity Templates for one of our resolvers, for another resolver we use lambda function as a data source. https://lnkd.in/dE_RzjgG #aws #terraform #lambda #graphql