Having played a bit I'm now adding #OpenAPI docs with #Swagger UI to #Autonomi dweb using #utoipa and #utoipauto.

I'm neither a user nor, until now a builder of HTTP APIs so stumbling around, but these crates do a decent job of being usable even to a novice.

I really shouldn't be let loose with all this

Code on Demand is REST’s wildcard—optional but powerful. It lets servers send executable code to clients for enhanced functionality when needed. Want to know when, why, and how to use it effectively? Check out the latest post!

htmx up next!

#REST #API #WebAPI #htmx

https://woodruff.dev/rest-constraint-6-code-on-demand-when-why-and-how-to-use-it/

REST’s layered system is all about flexibility and scale. You can improve performance, security, and scalability by stacking components like gateways and load balancers without messing with the core API. Curious how this works? Check out my latest post!

https://woodruff.dev/rest-constraint-5-embracing-layers-for-flexibility-and-scale/

Going stateless is one of REST’s secret weapons. Treating each request as independent makes APIs more scalable, reliable, and easier to cache. Want to know why statelessness is such a big deal? Read the post!

https://woodruff.dev/rest-constraint-3-going-stateless-for-scalability/

Client-server separation is the secret sauce behind REST’s scalability. By keeping the UI and data storage separate, each can evolve independently. Want to know why this design choice is such a game-changer? The blog post will explain a lot.

https://woodruff.dev/rest-constraint-2-why-client-server-separation-is-a-game-changer/

Great #RESTful APIs aren’t about cramming in features—they’re about keeping things simple. Clear URLs, predictable responses, and a clean structure make all the difference. Want to know why simplicity wins in #API design? Check out my latest post!

https://woodruff.dev/restful-api-design-why-simplicity-wins/

Who here knows enough #webplatfrom and #webapi to know if relative links exists with the Origin Private File System (#OPFS)?

thanks much for RT and dig to find people knowing...

Learn how to close down and wind up an API without making a mess of it all in this post by me. Avoid surprising your customers with these simple communication and monitoring methods. #APIDevelopment #WebAPI https://blog.treblle.com/best-practices-deprecating-api/

Question for the .Net developers. When working with a service layer and WebAPI where do you put the user input *format* validation? controller/endpoint, service, or both?

I'm currently using fluentvalidation for format validation, validated at the WebAPI endpoint(s), and business logic validation within the service layer. Any serious formatting issues would cause a model exception, which seems fair as if invalid user data reaches the service layer I consider it exceptional

Does anyone has experience in writing REST APIs in #rust ?

Which framework did you use?

I am currently trying actix. But I found many others like rocket and axum