home.social

#apidesign — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #apidesign, aggregated by home.social.

  1. rate limiting is one of those things every API needs but half implement wrong. fixed window leaks at the boundary. sliding window is better. token bucket handles bursts best. return 429 with Retry-After — that one header saves your consumers so much pain. #apidesign #developer #programming

  2. rate limiting is one of those things every API needs but half implement wrong. fixed window leaks at the boundary. sliding window is better. token bucket handles bursts best. return 429 with Retry-After — that one header saves your consumers so much pain. #apidesign #developer #programming

  3. rate limiting is one of those things every API needs but half implement wrong. fixed window leaks at the boundary. sliding window is better. token bucket handles bursts best. return 429 with Retry-After — that one header saves your consumers so much pain. #apidesign #developer #programming

  4. rate limiting is one of those things every API needs but half implement wrong. fixed window leaks at the boundary. sliding window is better. token bucket handles bursts best. return 429 with Retry-After — that one header saves your consumers so much pain. #apidesign #developer #programming

  5. Ever shipped an API and regretted your generic signatures later? Wildcards everywhere. Confusing bounds. Mental overhead. Michel Charpentier breaks down why variance matters—and why #Java still feels heavy here.

    Read + apply: javapro.io/2026/01/27/what-i-s

    #APIDesign #Generics #JVM

  6. Ever shipped an API and regretted your generic signatures later? Wildcards everywhere. Confusing bounds. Mental overhead. Michel Charpentier breaks down why variance matters—and why #Java still feels heavy here.

    Read + apply: javapro.io/2026/01/27/what-i-s

    #APIDesign #Generics #JVM

  7. Ever shipped an API and regretted your generic signatures later? Wildcards everywhere. Confusing bounds. Mental overhead. Michel Charpentier breaks down why variance matters—and why #Java still feels heavy here.

    Read + apply: javapro.io/2026/01/27/what-i-s

    #APIDesign #Generics #JVM

  8. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  9. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  10. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  11. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  12. If this resonates, share your service template patterns or open an issue with gaps you hit in production.
    If gogen helps, a star and field feedback help prioritize what to improve next.
    #OpenSource #GoLang #BackendEngineering #Observability #APIDesign #CloudNative #DistributedSystems

  13. Currently integrating with an API that uses pagination.

    To get the next page of results you just provide a page=x parameter.

    The number of pages info is in the results, so you can use that to build the pagination engine.

    What happens if you go over the number of pages available? You get the last page of results again, with a 200 response code.

    Fair play I guess. A simple trap to catch the idiot developer who can't count :D

  14. REST 已老,AI 时代的智能体需要怎样的 API? 本文永久链接 – https://tonybai.com/2026/04/03/agentic-api-in-action 大家好,我是Tony Bai。 在过去的十几年里,如果...

    #技术志 #ActionDriven #AgentExperience #AgenticAPI #AIAgent #APIAggregation #APIDesign #API聚合 #API设计 #AX #BusinessLogic

    Origin | Interest | Match
  15. 🎥 𝗩𝗶𝗱𝗲𝗼 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝘄𝗶𝘁𝗵 𝗘𝗿𝗶𝗸 𝗪𝗶𝗹𝗱𝗲 & 𝗧𝗵𝗶𝗹𝗼 𝗙𝗿𝗼𝘁𝘀𝗰𝗵𝗲𝗿 𝗼𝗻 𝘁𝗵𝗲 𝗖𝗣𝗦𝗔-𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗟𝗲𝘃𝗲𝗹 𝗠𝗼𝗱𝘂𝗹𝗲 𝗔𝗣𝗜 – 𝗥𝗲𝗮𝗹 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗶𝗻𝘁𝗼 𝗠𝗼𝗱𝗲𝗿𝗻 𝗔𝗣𝗜 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 ✨

    #APIs drive scalable systems, business value, and AI-ready architectures. Erik Wilde and Thilo Frotscher, two of the module’s curators, share insights on design, governance, DX & AX, and building APIs that truly work.

    Watch the full interview 👉 t1p.de/td3mh

    #iSAQB #Softwarearchitecture #CPSA #AI #API #APIDesign

  16. Mastering FastAPI Request Bodies: Handling User Profiles and Token Authentication

    In 2026, building scalable backend services requires a robust understanding of how API endpoints process complex payloads. This session explores the standard patterns for managing data models and secu...

    📺 Watch here: youtube.com/watch?v=ABt48n3S7UA

    ##FastAPI ##Python ##BackendDevelopment ##APIDesign

  17. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment by GitforGits | Asian Publishing House is the featured book on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #Ai #ApiDesign #Docker #Python #SystemIntegration

  18. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment by GitforGits | Asian Publishing House is the featured book on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #Ai #ApiDesign #Docker #Python #SystemIntegration

  19. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment by GitforGits | Asian Publishing House is the featured book on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #Ai #ApiDesign #Docker #Python #SystemIntegration

  20. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment by GitforGits | Asian Publishing House is the featured book on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #Ai #ApiDesign #Docker #Python #SystemIntegration

  21. I always struggle to determine if my API server should return *400 Bad Request* or *422 Unprocessable Content* for bad input. Meanwhile, SonarCloud returns *404 Not Found* if I'm not authenticated.
    #SoftwareDevelopment #ApiDesign

  22. "Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.

    The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.

    Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."

    apichangelog.substack.com/p/ma

    #API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience

  23. "Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.

    The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.

    Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."

    apichangelog.substack.com/p/ma

    #API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience

  24. "Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.

    The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.

    Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."

    apichangelog.substack.com/p/ma

    #API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience

  25. "Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.

    The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.

    Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."

    apichangelog.substack.com/p/ma

    #API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience

  26. "Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.

    The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.

    Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."

    apichangelog.substack.com/p/ma

    #API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience

  27. "In a previous post on agent experience (AX), we wrote that “Artificial intelligence tools are bad at inferring context or reading between the lines,” and that “content designed for consumption by AI should look less like a blog post and more like a legal contract. Great agent experience is all about being as clear and predictable as possible.”

    Where possible, we need to eliminate assumptions that only make sense to human readers. LLMs aren’t as forgiving of undocumented constraints, inconsistencies, or vague descriptions as a human reader might be. If you’re struggling with that, we can lean on AI tools — it makes sense that AI would know what AI likes, right? — for identifying some of these gaps.

    When we covered AI assistants for API developers, for example, we identified LintGPT as a useful tool for its ability to automate the creation of an API style guide, enforce specification standards, and even catch breaking changes before deployment.

    API specifications are no longer just documentation. They’re living contracts with machines, which increasingly have the power to read and interact with said contracts. Improving clarity, consistency, and precision might create a few initial headaches, but it opens the door to smarter tooling, faster iteration, and APIs taking pride of place in an increasingly AI-driven ecosystem."

    nordicapis.com/how-llms-are-ch

    #AI #GenerativeAI #LLMs #APIs #APIDesign #APISpecifications

  28. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment House is a new release on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #ai #ApiDesign #Docker #Python #SystemIntegration

  29. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment House is a new release on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #ai #ApiDesign #Docker #Python #SystemIntegration

  30. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment House is a new release on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #ai #ApiDesign #Docker #Python #SystemIntegration

  31. Build GenAI Agents with OpenAI + vLLM: Develop portable AI agents in Python with structured outputs, tool calling, OpenAI Agents SDK, vLLM, model switching, CLI, API, and Docker deployment House is a new release on Leanpub!

    Link: leanpub.com/aiagentwithopenaiv

    #ai #ApiDesign #Docker #Python #SystemIntegration

  32. Validation logic drifting between frontend, backend, and batch jobs is a real production problem.

    This article shows how to move validation into your Protobuf schema using Protovalidate, and enforce the same rules in Quarkus, JavaScript, Python, and more.

    Schema as contract. Validation as infrastructure.

    👉 the-main-thread.com/p/protobuf

    #Java #Quarkus #Protobuf #APIDesign #SchemaFirst #BackendEngineering #FOSS

  33. 🧩 𝗔𝗣𝗜𝘀 𝗮𝘀 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗕𝗹𝗼𝗰𝗸𝘀 – 𝗡𝗲𝘄 𝗔𝗿𝘁𝗶𝗰𝗹𝗲 𝗯𝘆 𝗘𝗿𝗶𝗸 𝗪𝗶𝗹𝗱𝗲, 𝗧𝗵𝗶𝗹𝗼 𝗙𝗿𝗼𝘁𝘀𝗰𝗵𝗲𝗿 & 𝗙𝗮𝗹𝗸 𝗦𝗶𝗽𝗽𝗮𝗰𝗵 ✨

    #APIs are far more than technical interfaces. In their latest article, @sippsack , Erik Wilde, and Thilo Frotscher explain how APIs become strategic building blocks for modular IT landscapes, scalable systems, and sustainable digital business models. 💡

    Read the full article on the #iSAQB blog 👉 t1p.de/0x4ss

    #SoftwareArchitecture #APIDesign #APIGovernance #OpenAPI #AsyncAPI

  34. Ever shipped an API and regretted your generic signatures later? Wildcards everywhere. Confusing bounds. Mental overhead. Michel Charpentier breaks down why variance matters—and why #Java still feels heavy here.

    Read + apply: javapro.io/2026/01/27/what-i-s

    #APIDesign #Generics #JVM

  35. Infinite scroll usually fails for boring reasons.

    Offset pagination looks fine in the first demo. Then users scroll deeper, queries get slower, and the database starts doing more work for every request.

    This article walks through building cursor pagination with Quarkus and PostgreSQL. Not as a pattern diagram, but as a real API that stays fast no matter how far you scroll.

    the-main-thread.com/p/quarkus-

    #Java #Quarkus #PostgreSQL #BackendEngineering #APIDesign #Performance

  36. API keys fail quietly.

    Most systems still treat them as binary switches:
    valid key → full access.

    That works right up until a partner link, free tier, or internal tool suddenly unlocks paid or admin features.

    This article walks through a Quarkus design where API keys act as identities with feature-level permissions, not just shared secrets.

    the-main-thread.com/p/quarkus-

    #Java #Quarkus #APIDesign #SoftwareArchitecture

  37. "even with all that #GraphQL has to offer, #APIdesign remains difficult.

    Over time, we’ve developed some proven design philosophies and patterns for easier schema migrations, exposing errors, and avoiding ambiguous or misleading type names."

    the-guild.dev/graphql/hive/blo

  38. Legacy modernization fails at implicit boundaries, not scale. Learn how API contracts, validation, and error handling prevent silent production failures. hackernoon.com/legacy-moderniz #apidesign

  39. #SpecDrivenDevelopment flips traditional architecture by making specs executable & authoritative.

    Declared intent - validated code via AI-assisted generation, delivering real architectural determinism.

    Continuous enforcement kills drift - but demands stronger schema design & contract-first discipline.

    #InfoQbit.ly/3YCprvu

    #SoftwareArchitecture #APIs #APIDesign #AI #GenAI #CodeGeneration

  40. #SpecDrivenDevelopment flips traditional architecture by making specs executable & authoritative.

    Declared intent - validated code via AI-assisted generation, delivering real architectural determinism.

    Continuous enforcement kills drift - but demands stronger schema design & contract-first discipline.

    #InfoQbit.ly/3YCprvu

    #SoftwareArchitecture #APIs #APIDesign #AI #GenAI #CodeGeneration

  41. #SpecDrivenDevelopment flips traditional architecture by making specs executable & authoritative.

    Declared intent - validated code via AI-assisted generation, delivering real architectural determinism.

    Continuous enforcement kills drift - but demands stronger schema design & contract-first discipline.

    #InfoQbit.ly/3YCprvu

    #SoftwareArchitecture #APIs #APIDesign #AI #GenAI #CodeGeneration

  42. #SpecDrivenDevelopment flips traditional architecture by making specs executable & authoritative.

    Declared intent - validated code via AI-assisted generation, delivering real architectural determinism.

    Continuous enforcement kills drift - but demands stronger schema design & contract-first discipline.

    #InfoQbit.ly/3YCprvu

    #SoftwareArchitecture #APIs #APIDesign #AI #GenAI #CodeGeneration

  43. Retries are not harmless.

    Without idempotency, they silently corrupt data: duplicate orders, double charges, broken workflows.

    I wrote a deep, hands-on guide explaining idempotency keys, the IETF standard, and how to implement them correctly in Java with Quarkus — including concurrency, in-flight requests, TTL cleanup, and real failure scenarios.

    the-main-thread.com/p/java-ide

    #Java #Quarkus #DistributedSystems #APIDesign #HTTP #IETF #SoftwareArchitecture

  44. Why are “simple” bugs so hard to trace? ask @ties_ven. Often, state complexity—not code complexity—is to blame.

    Learn how immutability forces explicitness, enables local reasoning, & cuts cognitive overhead in #Java: javapro.io/2025/09/24/state-ma

    #CleanCode #APIDesign #TypeSafety

  45. How do you avoid illegal object states without runtime checks? @ties_ven shows how to model state transitions directly in the #Java type system—no @nullable, no ambiguity.

    A must-read for anyone building APIs or domain models. javapro.io/2025/09/24/state-ma

    #TypeSafety #APIDesign

  46. Modern Banking Microservices with Clean Architecture, DDD, TDD, .NET 9, and Angular (Monorepo): A Complete Engineering Guide to Building Production-Grade Banking Systems Using Microservices, Docker, CI/CD, Testing, and Angular Nx Monorepos leanpub.com/fullstack-banking- by Gustavo Felix is the featured book on the Leanpub homepage! leanpub.com #CSharp #ApiDesign #Devops #Angular #MessageDriven #Rabbitmq #Microservices #Git

    Find it on Leanpub!