0 views collected around this technical thread.
This article explains the fundamentals of Remote Procedure Call (RPC), its role in distributed systems, the architecture and workflow of RPC frameworks, and compares popular implementations such as Thrift, Dubbo, and Spring Cloud with other communication styles like REST, SOAP, and SOA.
This article presents comprehensive guidelines for designing robust, secure, and maintainable enterprise services, covering API path conventions, request handling, input/output parameter design, business logic recommendations, exception handling, dependency management, monitoring, degradation strategies, encryption, and system admission practices.
This article explains how to design microservice architectures by applying domain‑driven design concepts such as bounded contexts and aggregates, using context mapping and event‑storming techniques to define clear service boundaries, handle communication, and balance consistency with availability.
This article presents comprehensive guidelines for designing flexible, secure, and maintainable API services, covering standardized paths, request handling, parameter design, business logic, exception management, dependency classification, monitoring, degradation strategies, handling legacy services, and encryption measures to ensure robust service architecture.
This article explores essential service design considerations beyond standard guidelines, covering API path structuring, request handling, parameter design, security measures, monitoring, degradation strategies, and code examples to help build flexible, secure, and maintainable backend services.
This article explains the fundamentals of Remote Procedure Call (RPC), its core components and workflow, compares it with other communication methods, lists popular RPC frameworks, and distinguishes RPC from SOA, SOAP, and REST, providing a comprehensive overview for backend developers.
This article explains the fundamentals of Remote Procedure Call (RPC) frameworks, their underlying architecture, communication steps, role of providers, consumers, and registries, and compares popular RPC solutions with other service paradigms such as SOA, SOAP, and REST.
The article analyzes high coupling problems caused by multiple controller calls and third‑party integrations in a Java settlement backend, and proposes a dedicated TPS microservice with unified Feign interfaces, enum‑based routing, and factory patterns to decouple frontend and backend logic while providing implementation examples and diagrams.
This article explains why remote procedure call (RPC) is essential for modern distributed services, describes the evolution from monolithic to service‑oriented architectures, and details the core components, communication steps, serialization, service discovery, and full call flow of an RPC framework.
The article describes how redesigning a TV streaming service from a single to a dual‑service architecture, leveraging Android Binder, optimized protocol startup, adaptive networking, and session‑based monitoring dramatically boosted stability above 99%, protocol success over 98.5%, and issue‑resolution efficiency via systematic batch analysis and A/B testing.
The team upgraded Taobao’s feed mixing by deploying an independent xhuffle service built on the xrec framework, which unifies ad and natural recommendation objectives, decouples strategy from business logic, and uses a serial integration to keep average latency under 30 ms while improving both natural and ad metrics, with plans to extend mixing to short video, live streams, and broader scenarios.
To cope with soaring traffic on Bilibili’s effect‑advertising engine, the team systematically measured latency, eliminated redundant Redis calls, switched JSON to Protobuf, applied branch‑prediction hints, loop‑unrolling and AVX256 SIMD, introduced object‑pooling and an inverted‑index request format, cutting CPU usage by 21 % and boosting peak throughput 13 %.
This article explains the OSI seven‑layer network model, compares RPC and HTTP services, describes RPC architecture, synchronous and asynchronous calls, and reviews popular RPC frameworks such as gRPC, Thrift, and Dubbo, helping developers choose the right approach for enterprise back‑end systems.
This article examines the challenges of a complex supply‑chain system built on Spring Cloud, proposes introducing an API layer to handle aggregation, distributed calls and decoration, and further adopts a Backend‑for‑Frontend (BFF) approach to reduce service coupling, improve client‑specific optimization, and streamline team responsibilities.
This article explains the fundamental differences between RPC and HTTP interfaces, their underlying protocols, component architectures, popular frameworks, performance characteristics, and provides guidance on when to use each approach in backend service development.
This article explains the fundamental differences between RPC and HTTP interfaces, describes their underlying client‑server architectures, compares performance, transport protocols, load balancing and service governance, and provides guidance on when to choose each approach in modern backend development.
This article analyzes the data‑dependency challenges in microservice‑based supply‑chain systems, critiques an initial IN‑query approach, proposes a data‑redundancy design, and ultimately presents a decoupled real‑time synchronization solution using the Bifrost middleware to improve performance and consistency.
This article analyzes data‑dependency issues in a micro‑service based supply‑chain system, compares an initial data‑redundancy approach with a message‑driven solution, and finally proposes a decoupled real‑time synchronization architecture using the Bifrost middleware to improve query performance and maintain consistency.
This article explains the fundamental differences between RPC and HTTP services, covering OSI model layers, RPC architecture components, synchronous vs asynchronous calls, popular RPC frameworks such as gRPC, Thrift, and Dubbo, and when to choose each approach for enterprise applications.
This article explains why Medium transitioned from a monolithic Node.js application to a microservice architecture, outlines the core design principles, shares practical strategies for building, deploying, and observing services, and warns about common pitfalls such as the microservice syndrome.