DEV Community

# apidesign

Best practices for designing, versioning, and managing robust REST and gRPC APIs.

Posts

đź‘‹ Sign in for the ability to sort posts by relevant, latest, or top.
NASA’s $125M Unit Error: Why Your API Needs Explicit Naming
doogal profile

NASA’s $125M Unit Error: Why Your API Needs Explicit Naming

#softwareengineering #apidesign #backenddevelopment
Comments
3 min read
API Rate Limits: What They Mean and Why You Hit Them
apiverve profile

API Rate Limits: What They Mean and Why You Hit Them

#ratelimiting #apidesign #performance #errors
Comments
4 min read
Architecting Scalable AI Chatbot Integrations for Enhanced Customer Experience
lifeisverygood profile

Architecting Scalable AI Chatbot Integrations for Enhanced Customer Experience

#ai #chatbots #architecture #apidesign
Comments
4 min read
Rate Limiting 101: How to Protect Your APIs at Scale
akshatjme profile

Rate Limiting 101: How to Protect Your APIs at Scale

#backenddevelopment #systemdesignconcepts #softwareengineering #apidesign
3
Comments
5 min read
API Design Interview Questions: REST and Beyond
matt_frank_usa profile

API Design Interview Questions: REST and Beyond

#apidesign #interviewquestion #restapi
1
Comments
7 min read
API Versioning Strategies: Incidents and Fixes
saber-amani profile

API Versioning Strategies: Incidents and Fixes

#backend #apidesign #dotnet
3
Comments
3 min read
REST vs GraphQL in Practice, Trade-offs for Backend and Frontend Teams
saber-amani profile

REST vs GraphQL in Practice, Trade-offs for Backend and Frontend Teams

#softwareengineering #apidesign #dotnet #python
4
Comments
4 min read
Surviving Breaking Changes in Evolving C# APIs, Hard Lessons and Practical Strategies for .NET Devs
saber-amani profile

Surviving Breaking Changes in Evolving C# APIs, Hard Lessons and Practical Strategies for .NET Devs

#softwareengineering #dotnet #systemdesign #apidesign
3
Comments
3 min read
đź‘‹ Sign in for the ability to sort posts by relevant, latest, or top.