Freaks City

Nacos Overview Nacos, derived from Dynamic Naming and Configuration Service, is a platform designed to streamline service discovery, configuration management, and governance in cloud-native environments. It simplifies building, delivering, and managing microservice architectures by offering capabilities for dynamic registration, configuration, ...

Core Concepts of Microservices Architecture Microservices architecture represents a structural approach to software development where an application is composed of small, autonomous modules. Each module, or service, focuses on a specific business capability and operates independently within its own process. These services communicate through we ...

Core Annotations (Simulating Dubbo) 1. @SPI Annotation (Marking Extension Interfaces) import java.lang.annotation.*; @Target(ElementType.TYPE) @Retention(RetentionPolicy.RUNTIME) public @interface SPI { // Default extension name String value() default ""; } 2. @Adaptive Annotation (Simplified Adaptive Methods) import java.lang.annot ...

Distributed Transactions in Microservices In microservice architectures, a single business operation often spans multiple services and databases. Unlike local transactions that follow the ACID (Atomicity, Consistency, Isolation, Durability) principles within a single database, distributed transactions must ensure data consistency across network ...

Nacos functions not only as a service registry but also as a dynamic configuration management server. This capability allows for centralized configuration control, enabling updates to be pushed to multiple services simultaneously without requiring individual modifications or service restarts. When a service starts, it merges local configuration ...

Nacos clusters organize microservices into logical groups, defaulting to the DEFAULT cluster. Adjust this behavior via the clusterName property in your configuration file: spring: cloud: nacos: discovery: server-addr: 127.0.0.1:8848 username: nacos password: nacos clusterName: SH Services in the same ...

Design Approach Upon successful login, generate a token using the userId and have the frontend store it. When subsequent requests reach the gateway, create a filter to parse userId from the token and inject it into the request headers. Once the request arrives at the target service, create an interceptor to extract userId from the headers, fet ...