The article examines the reasons behind a company's rule to use POST for every API, compares GET and POST characteristics, shares community opinions, discusses the trade‑offs of strict RESTful enforcement, and suggests when such a convention is appropriate.
An experienced developer reflects on a Zhihu question about mandating POST for all interfaces, compares GET and POST characteristics, shares personal practices, presents community opinions on RESTful benefits and drawbacks, and describes his company's concrete API rule using a single POST/action endpoint with protobuf and gRPC integration.
This guide presents 22 practical best‑practice rules for designing consistent, resource‑oriented RESTful APIs, covering naming conventions, URL structure, parameter casing, versioning, monitoring endpoints, security measures, pagination, field selection, CORS, error handling, and more, with concrete code examples.
The article examines the reasons behind a company's rule that all HTTP interfaces must use POST, compares POST and GET characteristics, discusses RESTful benefits and drawbacks, and offers practical guidance on choosing the right method for different API scenarios.
This comprehensive tutorial explains how to design and implement RESTful APIs with Spring Boot 3.2.5, covering all major HTTP methods (GET, HEAD, POST, PUT, DELETE, PATCH), best‑practice endpoint design, response handling, status‑code usage, pagination, filtering, versioning, caching, and security considerations.
This comprehensive guide explains what APIs are, outlines essential design principles, and presents best‑practice techniques—including RESTful patterns, resource‑oriented design, proper HTTP methods, status codes, versioning, pagination, caching, error handling, authentication, and documentation—to help developers build scalable, secure, and maintainable interfaces.
The article examines common misconceptions in RESTful API design, explaining why developers often limit interfaces to GET and POST, why some APIs return only HTTP 200 status codes, and how to decide the proper use of other methods and status codes for empty results.
The article examines the reasons behind mandating POST for all HTTP interfaces, compares GET and POST characteristics, discusses RESTful principles, highlights practical drawbacks, and shares a real‑world backend implementation that balances security, performance, and operational efficiency.
This article explains what RESTful APIs are, outlines their architectural constraints, shares practical design guidelines such as using nouns in URIs, proper HTTP methods, status codes, versioning strategies, and demonstrates how Apache APISIX can enforce these practices and modernize legacy APIs without changing existing code.
This guide presents a concise set of best‑practice rules for designing consistent, resource‑oriented RESTful APIs, covering naming conventions, URL structures, HTTP methods, versioning, pagination, security, monitoring, and documentation to improve developer experience and system reliability.
This article examines the reasons behind mandating POST for all API endpoints, compares GET and POST characteristics, discusses the practical implications of such a policy, and offers guidance on when each HTTP method is appropriate for backend development.
This guide presents 22 practical rules for designing clean, consistent RESTful APIs—including resource-oriented URLs, kebab‑case paths, camelCase parameters, proper use of HTTP verbs, versioning, pagination, field selection, CORS, security, and monitoring—to help developers avoid common pitfalls and improve API usability.
This article presents a concise set of best‑practice guidelines for designing consistent, resource‑oriented RESTful APIs, covering naming conventions, URL structures, HTTP methods, parameter handling, versioning, monitoring, security, error handling, and documentation tools.
This guide presents a concise set of best‑practice rules for designing consistent, RESTful backend APIs—including naming conventions, URL structures, HTTP methods, versioning, pagination, security, and documentation tools—to help developers create clear, maintainable, and user‑friendly services.
This guide presents a concise set of best‑practice rules for designing consistent, RESTful backend APIs—including naming conventions, versioning, pagination, security, monitoring, and error handling—to improve developer experience and maintainability across microservice architectures.
This article presents a concise, step‑by‑step guide to designing clean, consistent RESTful APIs, covering resource naming, URL conventions, HTTP methods, versioning, pagination, field selection, security, monitoring, error handling, and documentation tools, with concrete code examples for each rule.
The article explains the origins of REST, breaks down its core concepts of resources, representations, and state transfer, details HTTP methods, URL versioning, status codes, and provides practical RESTful API design examples while contrasting REST with traditional Web Services.
This article examines why some companies force every API to use POST, compares GET and POST advantages and drawbacks, shares practical guidelines, and invites readers to consider the best approach for their own API design.
The article examines why certain companies mandate POST for every API, comparing GET and POST across security, payload size, data types, performance, and proper usage, and offers practical guidelines for designing sensible HTTP method conventions.
This guide walks through Postman's core features, covering GET, POST, PUT, and DELETE request testing, body options, custom headers, console usage, and the four variable types with their priority hierarchy, providing practical examples and official resource links.
This comprehensive guide explains why clear API specifications are essential, compares RESTful and RPC styles, outlines OpenAPI and Google design principles, and provides practical rules for versioning, URL design, HTTP methods, status codes, authentication, rate limiting, error handling, naming conventions, and documentation to help developers build robust, maintainable services.
This article explains how to create Laravel routes for GET and POST forms, handle CSRF protection, disable it when necessary, configure CSRF whitelist, and use form method spoofing to send PUT requests via HTML forms.
This article explains how to design highly available, flexible, and durable APIs by identifying consumers, defining resources and operations, choosing the right API style, and following best practices such as proper HTTP methods, clear error messages, and hypermedia (HATEOAS) support.
This guide explains the nine HTTP methods, highlights the five most common ones for RESTful APIs, outlines essential API design principles, and details proper usage of HTTP status codes and error responses to build robust, maintainable backend services.
This article explains the background of RESTful APIs, outlines recommended URL and parameter formats, details HTTP methods, response structures, filtering, pagination, status codes, hypermedia links, and extension considerations to help developers design robust, standardized backend services.
This article presents ten concise best‑practice guidelines for designing clean, efficient REST APIs, covering proper use of HTTP methods, status codes, headers, framework selection, black‑box testing, and five additional crucial recommendations to help developers create elegant and maintainable web services.
This guide demystifies RESTful API design by explaining the role of each HTTP method, resource types, URL conventions, and best‑practice principles, using clear diagrams so beginners can grasp how to build scalable, maintainable backend services.
