Your APIs Are Setup Wrong!

@jordankodes

7.1K followers · usually 11.6K views a post

Views

74.8K

Likes

5.8K

Comments

27

Shares

353

Selling · SaaS › Developer Tool

—

Why it worked

The video addresses a common pain point for developers (incorrect API setup leading to data duplication) and offers a clear, actionable solution (using idempotency keys). The use of code snippets and diagrams makes the technical concept easy to understand, and the direct address to the viewer creates engagement.

Summary

The video explains the concept of API idempotency and why it's crucial for preventing duplicate data entries. It demonstrates how to implement idempotency by sending an 'Idempotency-Key' with API requests to ensure operations are executed safely, even if retried.

Structure

1Introduction to API setup errors
2Problem: Blindly sending requests leads to duplication
3Solution: Learn about idempotency
4Definition of idempotency
5Implementation: Use an 'Idempotency-Key'
6Example of idempotency in action
7Call to action: Follow for more tips

Product placement

The video discusses the concept of API idempotency and shows code examples of how to implement it using an 'Idempotency-Key' header in API requests. It also shows diagrams illustrating deduplication and the flow of an idempotent operation in a distributed system.

Original caption

api idempotency, data integrity backend, duplicate api requests, react useeffect fetch issue, backend reliability, prevent duplicate orders, software engineering tips, scalable api design, nodejs backend best practices, database consistency, distributed systems basics

More from @jordankodes

Their other posts in the index, biggest breakout first.

Call to action

Follow and like for more.

On-screen text

Your APIs Are Setup Wrong! BUILDING IF UP SECONDS. JavaScript await fetch("/api/order") await fetch("/api/order") RETRY BLINDLY AND READY CONDITIONS. USERS RETRY CALLS CAN BEING IS NEED IDEMPOTENCY. In software, idempotency means that an operation produces the same outcome no matter how many times it is executed. If an action runs once or fifty times, the system state remains identical after the first successful attempt. API Design No Idempotency Idempotency Google Cloud IDEMPOTENCY OPERATION OUTCOME MANY EXECUTED. JavaScript POST /order Idempotency-Key: 123 YOU SEND POTENCY DATA DEDUPLICATED. FIRST DATABASE. RETRY POTENCY DATABASE WANT SURE MORE.

Transcript

If you're building an app, here's how I can tell if your APIs are set up wrong in 5 seconds. If I see anything like this retry logic that blindly sends requests and your backend is not ready for real-world conditions. Users, retry calls, calls can fail. This can lead to the same data being duplicated, which is not what you want. You need to learn about idempotency. In software, idempotency means that an operation produces the same outcome no matter how many times it is executed. If an action runs once or fifty times, the system state remains identical after the first successful attempt. Idempotency is an operation that produces the same outcome no matter how many times it is executed. So just make sure whenever you call your API, you send an idempotency key. This ensures that your data stays deduplicated. Notice on the first try here, it hits the database. On the retry, idempotency key found, so your database was never touched. You want to make sure first. If you want more tips like this, make sure to follow and like for more.