The article examines why a company might require every HTTP API to use POST, compares GET and POST characteristics, discusses RESTful principles, outlines the trade‑offs of a POST‑only policy, and offers practical guidance for choosing the right method based on business needs.
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.
The article examines why a company might mandate POST for every API, compares GET and POST characteristics, discusses RESTful principles, outlines the technical and business trade‑offs of such a policy, and shares practical guidance for choosing the right HTTP method.
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.
The article examines why a company might mandate POST for every API, compares GET and POST characteristics, discusses RESTful best‑practice expectations, highlights the hidden costs of over‑standardization, and presents a more nuanced approach to API design for dynamic and static services.
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.
The article examines why a company might mandate POST for every API, comparing GET and POST characteristics, discussing RESTful benefits, highlighting the hidden costs of uniform POST usage, and sharing a practical hybrid approach that balances security, payload size, caching, and developer productivity.
This article, based on the open‑source HiMarket project, systematically compares six mainstream API protocols—from classic RESTful and SOAP to modern GraphQL, microservice‑focused RPC frameworks, real‑time WebSocket, and streaming SSE—detailing their core concepts, technical traits, advantages, and ideal application scenarios.
The article examines why some companies mandate POST for every API, compares GET and POST characteristics, discusses RESTful principles, weighs the benefits and drawbacks, and offers practical guidance while showcasing an open‑source microservice project for deeper learning.
The article traces how an early AJAX API that used only HTTP 200 and a simple JSON wrapper devolved into a tangled mix of proper RESTful codes, custom three‑digit‑plus statuses, pseudo‑resources, PATCH work‑arounds, and finally a pragmatic scheme that keeps 200 for success, adds extended numeric categories, and adopts verb‑adjective‑resource method names for clarity.
The article narrates a top architect’s experience with early API error handling, the chaos caused by non‑standard HTTP status codes, the shift toward RESTful conventions, and later promotional offers for AI tools, illustrating both technical lessons and marketing pitches.
This article narrates the messy history of API design, illustrating early AJAX conventions, the misuse of HTTP status codes, the challenges of maintaining Restful standards, ad‑hoc extensions, and the eventual abandonment of Restful in favor of a simplified POST‑centric approach, while highlighting practical lessons for backend developers.
This article explains core microservice design principles—including the AKF scalability cube with its Y (functional), X (horizontal scaling), and Z (data partition) axes, front‑end/back‑end separation, stateless service architecture, and RESTful communication—providing practical guidance for building scalable, maintainable systems.
This article explains microservice architecture fundamentals, covering the AKF scalability cube split principle, front‑end/back‑end separation, stateless service design, and RESTful communication, illustrating Y, X, Z axes for functionality, horizontal scaling, and data partitioning with diagrams and practical examples.
This article explains why Spring Cloud uses HTTP instead of RPC for remote calls, compares HTTP and RPC protocols, describes how to implement a simple HTTP server in Java, outlines the principles of RESTful architecture, and discusses the advantages, disadvantages, and future trends of both approaches.
This article explains why Spring Cloud prefers HTTP over RPC for remote calls, covering the embedded Tomcat architecture, JSON data exchange, the fundamentals of RPC over TCP, and compares their advantages, disadvantages, and suitability for microservice development.
This article explains why Spring Cloud prefers HTTP over RPC for remote calls, detailing the underlying Tomcat-based web service, the differences between HTTP and RPC protocols, their advantages and disadvantages, and provides guidance on choosing the appropriate approach for microservice architectures.
This tutorial walks through creating a full‑stack project that uses json-server to expose a RESTful API, demonstrates CRUD operations via Postman, and shows how to interact with the API from a simple frontend using JavaScript fetch calls.
The article explains why Spring Cloud prefers HTTP over RPC for remote calls, detailing the advantages of embedded Tomcat and JSON over HTTP, the limitations of TCP‑based RPC, and provides a comparative analysis of their architectures, pros, cons, and suitability for microservices.
This ten‑day hands‑on course teaches the full lifecycle of building RESTful APIs with the Laravel framework, covering design, routing, request/response handling, authentication, data transmission, error handling, and practical exercises to boost development efficiency for beginners and experienced developers alike.
This article explains how Spring Cloud leverages HTTP via an embedded Tomcat container for flexible, cross‑platform microservice communication, contrasts it with TCP‑based RPC's serialization requirements, and outlines the advantages, disadvantages, and selection criteria for each approach.
This article explains the concepts, design principles, and key differences among RESTful, SOAP, RPC, SOA, and microservices, and outlines why microservices have emerged as an evolution of SOA, illustrated with typical framework examples and architectural evolution diagrams.
This article describes the motivation, design, and usage of Hasaki, a lightweight Go HTTP Restful client that supports custom status‑code handling, multiple data formats such as JSON, XML, YAML and protobuf, builder‑style chaining, and extensible middleware, providing code examples and a plugin architecture.
The article examines the reasons behind mandating POST for every API endpoint, compares GET and POST characteristics, discusses RESTful principles, highlights practical pros and cons, and offers guidance on choosing the most suitable HTTP method based on business and technical considerations.
The article examines why certain companies mandate POST for every API, compares GET and POST in terms of security, payload size, caching, and semantics, and discusses the trade‑offs and real‑world implications of such a blanket rule for backend development.
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 compares RPC and HTTP interfaces, detailing their architectures, popular frameworks, performance characteristics, load‑balancing, and service‑governance features, and provides practical guidance on selecting the right approach for internal high‑performance services or external cross‑platform APIs.
This article explains the core concepts, design principles, and key differences among RESTful, SOAP, RPC, SOA, and microservices, illustrating how they relate to each other and why modern architectures increasingly adopt microservices for scalability and business agility.
This article explains how RESTful API design reduces testing complexity by using unique URIs, standard HTTP methods, and JSON data exchange, and shows how test engineers can extend their frameworks with serialization support and added PUT/DELETE operations.
This article presents a full‑stack student management system built with Vue on the front end and SpringBoot + MyBatis on the back end, detailing project introduction, deployment steps, technology stacks, core functionalities, database design, and source code acquisition.
This article introduces a front‑back separated student management system built with Vue on the front end and SpringBoot + Mybatis on the back end, covering project introduction, deployment steps, UI showcases, technology stacks, system functions for admin, teacher, and student roles, as well as database design and acquisition methods.
This article explains how to build a highly extensible, modular backend service using Spring Cloud, demonstrates practical module composition and separation, discusses RESTful API design principles, presents concrete Java code examples for commands, controllers and pagination, and reviews popular API documentation tools such as Swagger, SpringDoc and Knife4j.
This article introduces Ginrest, a Go 1.18 generic‑based library that streamlines the conversion of gRPC or other microservice functions into RESTful endpoints by providing request/response wrappers, unified error handling, and context utilities, dramatically reducing repetitive boilerplate code.
This article provides PHP code snippets to determine the HTTP request method—such as GET, POST, PUT, DELETE, PATCH—and to check for AJAX requests, offering a quick reference for developers implementing RESTful APIs in a backend environment.
This article explains how to use the @PathVariable annotation in Spring MVC to handle required and optional parameters in RESTful URLs, illustrates the syntax with image-based examples, discusses the complexity of multiple parameters, and advises using POST for more intricate cases, while also offering promotional links and giveaways.
The article examines why certain companies mandate POST for every API, comparing GET and POST characteristics, discussing RESTful principles, ROI considerations, and the practical trade‑offs of such a uniform approach, while offering guidance on when each method is appropriate.
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.
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 the AKF scalability cube for microservice architecture, detailing the Y‑axis functional decomposition, X‑axis horizontal scaling, Z‑axis data partitioning, as well as front‑end/back‑end separation, stateless services, and RESTful communication, providing practical diagrams and guidance for building robust, scalable systems.
This article examines common RESTful API design mistakes—such as using verbs in URIs, embedding version numbers, and inconsistent case—provides corrected examples, discusses versioning strategies, and outlines best‑practice guidelines for building clean, resource‑oriented backend services.
This article presents a detailed case study of using TDengine as the core time‑series database for a private‑cloud energy‑management platform, covering project background, overall architecture, connector selection, Java RESTful implementation, performance testing, deployment strategy, and future technical expectations.
This guide explains RESTful concepts, compares Casbin keyMatch functions, demonstrates Postman testing of CRUD endpoints, and shows how to integrate authentication middleware in ThinkPHP5.1, providing complete code snippets and configuration details for secure API development.
This article explains why API version control is essential for software iteration, outlines major and minor version strategies, compares URI, host, and header versioning methods, and demonstrates routing techniques—including Nginx configuration—to support parallel API versions.
Effective API design in microservices requires platform independence, reliability, appropriate RESTful maturity, avoiding simple wrappers, ensuring separation of concerns, exhaustive and independent endpoints, proper versioning, consistent naming, and security measures, all of which are detailed alongside practical examples and a comprehensive review checklist.
This article outlines essential RESTful API design guidelines, covering clear URL conventions, precise HTTP status code usage, proper JSON responses, error handling without misleading 200 codes, and the inclusion of hypermedia links to improve client navigation.
This article outlines essential RESTful API design principles, covering clear URL structures, proper use of HTTP verbs, precise status codes, appropriate response formats, and the inclusion of hypermedia links to create intuitive, maintainable, and standards‑compliant web services.
This article explains essential RESTful API design details—including URL conventions, HTTP verb usage, status‑code precision, proper JSON responses, and HATEOAS linking—to help developers create clear, consistent, and user‑friendly web APIs.
This article outlines essential API design principles and best practices, covering simple, understandable, consistent, stable, and secure APIs, then delves into RPC mechanisms, Protobuf serialization, RESTful conventions, Swagger documentation, Spring Boot integration, HTTP/2 performance improvements, and the powerful combination of HTTP/2 with Protobuf in gRPC.
This article provides a comprehensive tutorial on building a full‑stack application by setting up front‑end tools like Node.js and Vue.js, creating Vue projects with CLI, using Vue directives, routing and Axios for API calls, and integrating a Spring Boot backend with RESTful services, Dubbo RPC, and Spring Cloud components for microservice architecture.
This article examines why robust API specifications are crucial for cloud services, outlines seven major challenges—from choosing design patterns and resource modeling to error handling, versioning, and ecosystem integration—and offers practical guidance for building consistent, reliable OpenAPI interfaces at scale.
This article shares a step‑by‑step experience of redesigning a project’s API by adopting front‑back separation, establishing unified interface conventions, standardizing database IDs, request/response formats, and implementing RESTful methods with Java Spring controllers, while also addressing tooling, documentation, and static resource strategies to dramatically reduce communication overhead and accelerate delivery.
The article examines the evolution of web development models, explains why naive front‑end/back‑end separation often leads to problems, and offers practical guidelines—including team roles, RESTful API design, collaboration patterns, and deployment strategies—to implement a successful separation architecture.
Although RESTful principles recommend using distinct HTTP verbs for CRUD operations, many developers still rely on GET and POST for creating, updating, and deleting resources, leading to non‑standard JSON APIs; this article explains the HTTP methods, their semantics, and why practical constraints often shape API design.
This article compares JSON Web Tokens and session cookies, highlighting JWT’s superior stability, security, RESTful compatibility, and performance, and explains the scenarios where JWT is the preferred choice for modern web applications.
This article explains the fundamentals of RESTful architecture—including resources, uniform interfaces, URIs, statelessness—and compares it with ROA, SOA, and RPC, while also covering authentication methods such as Basic, Token, and OAuth, offering practical guidance for building robust microservice APIs.
The article details the design and implementation of Albianj's core backend components—including distributed lock considerations, unique ID generators, logging, caching, dynamic configuration, and RESTful services—highlighting their architecture, operational principles, and the practical benefits observed in real-world deployments.
This article explains five stability patterns—retry, timeout, circuit breaker, handshaking, and bulkhead—used to keep distributed systems resilient, illustrates their implementation with JAX‑RS/RESTful services in Java, and shows how asynchronous Java 8 techniques further improve reliability.
