julianmichel.dev

  • About me
  • Cookie Policy (EU)
  • Impressum
  • Privacy Policy
  • AppSync Merged API – Our real project experience as part of our hackathon

    AWS released a new feature for GraphQL APIs in May: Multiple AppSync APIs can be merged into one overall API. Our AI Hackathon gave us the opportunity to test the new Merged API feature in a real-world project. Why are Merged APIs such a useful feature? When designing complex software, it is common to break…

    June 29, 2023
  • Quickly recover from failures using automated SQS DLQ redrive

    Two years ago at re:Invent, AWS announced DLQ redrive to move messages from a dead letter queue (DLQ) to the original queue. Previously, this feature was only available using the AWS console. Now, DLQ redrive is available using AWS SDK and CLI. The new feature provides the ability to automatically handle invalid messages in DLQs…

    June 10, 2023
  • Building a smart home sensor application with AWS AppSync and AWS Amplify components

    Collecting sensor data such as temperature values is an example of smart home use cases. To display sensor data in real time, the use of AWS AppSync / GraphQL with its real-time message transmission capabilities is a good choice. This blog article describes how to implement a GraphQL backend using AWS AppSync. An Angular-based web…

    April 11, 2023
  • Adding Credly badges to AWS re:Post if email addresses do not match

    You can add your AWS certifications to AWS re:Post to show them on your profile and earn reputation points. In my case, I couldn’t add all certificates because some of them were issued when I was using an old email address. Each Credly badge contains an email address that will not be changed even if…

    February 1, 2023

julianmichel.dev

Proudly powered by WordPress

Manage Cookie Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}