DataOverload

AI slop

Code-First vs Design-First, tools you should use, and more

Hey - get in touch with me at Zuplo. If this is for a charity, we might be able to swing you a really cheap deal.

Cool project! Love the OpenAPI 3 support

This is me! I actually just made a blog version of this with my code samples linked: https://zuplo.com/blog/2025/03/24/apis-at-the-edge

Here's some tips I had on ensuring you can make changes or rollback changes to your API without breaking your consumer's trust.

There is now an official RFC for this: https://datatracker.ietf.org/doc/html/rfc9745

There are many SDK generators out there (even OSS) - what makes you special?

I have a project I work on every now and then that consumes arazzo specs: https://github.com/AdrianMachado/arazzo-runner Essentially its an executor for Arazzo

I'm working on a gateway called Zuplo that is Openapi-native and can synchronize with your generated OpenAPI docs too

You can write/generate OpenAPI in JSON. There are also many GUIs out there

Totally agree - I think the agents are honestly incentivized to not identify themselves

This was predictable vs creating a backdoor

FastAPI + Render + Zuplo tutorials from the FastAPI expert Marcelo Trylesinski

Hey folks - I tried to make the most comprehensive guide to API rate limiting out there. There's definitely some less explored topics like the new rate limiting header RFCs so even if you're experience with rate limiting - you might learn something new

Neat!

Quick tutorial I wrote on recreating the Supabase API experience using any hosted postgres. In this case I used neon for ease of setup, but the implementation can be adapted using the node `pg` module.

We switched from Fly to CF workers a while ago, and never looked back

You can replace the @neondatabase/serverless module with the node Postgres module (pg). Here's a sample of what that would look like: https://github.com/subzerocloud/showcase/blob/main/vercel-po...

Good guide on how to avoid having too many query params

Here's the IETF Draft proposal as well: https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-dep... - not an RFC yet

Author here - I actually plan on covering the deprecation header in a different post on sunsetting

Useful tips and examples for informing end users of an impending deprecation as a dev

Ooh, have a repo link?

If folks are looking for interactive API docs, I made this using their OpenAPI spec: https://zudoku.dev/demo?api-url=https://raw.githubuserconten...

Repo: https://github.com/zuplo-samples/xAI-OpenAPI/tree/main

Same here, I actually made a tool for this called www.jsonmergepatch.com - give it a try

You might like JSON Merge Patch then - much simpler syntax that avoids the URL stuff

Thanks for sharing, I'll try and find time to compare and write about it

It sort of is like a URL here's some more examples with both relative and absolute queries https://opis.io/json-schema/2.x/pointers.html

Check out JSON Merge Patch