0 views collected around this technical thread.
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 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 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.