nym on Nostr: API Size Matters One-size-fits-all doesn't apply to APIs. Instead, they come in all ...
API Size Matters
https://apichangelog.substack.com/p/api-size-mattersOne-size-fits-all doesn't apply to APIs. Instead, they come in all kinds of shapes and sizes. Even if it's true that during design time people try to come up with small APIs, over time they tend to grow. By size, I'm referring to the number of paths that REST APIs have, and not any other measure like the number of parameters, or the length of the responses. So, what can you consider a "normal" size for an API?

originally posted at
https://stacker.news/items/860964Published at
2025-01-23 08:24:38Event JSON
{
"id": "0507ec3f512e934f68a045315b9712637e86bc137cbb7a283a568c84a3b0bfba",
"pubkey": "bcea2b98506d1d5dd2cc0455a402701e342c76d70f46e38739aadde77ccef3c9",
"created_at": 1737620678,
"kind": 1,
"tags": [],
"content": "API Size Matters\nhttps://apichangelog.substack.com/p/api-size-matters\n\nOne-size-fits-all doesn't apply to APIs. Instead, they come in all kinds of shapes and sizes. Even if it's true that during design time people try to come up with small APIs, over time they tend to grow. By size, I'm referring to the number of paths that REST APIs have, and not any other measure like the number of parameters, or the length of the responses. So, what can you consider a \"normal\" size for an API?\n\n\n\noriginally posted at https://stacker.news/items/860964",
"sig": "783ada312b8dc4b37a3581cfb474d9fc625653077436a4cf96f330566a8a72372a012a31a077804ba5c4ff666023b9623dfd666c5e9660f0bb4db8a8bf3d2737"
}