microservice-infrastructure

Microservice Infrastructure

Applicable Scenarios

Configuring multiple environments, multiple profiles, and feature toggles
Implementing event-driven or MQ asynchronous processing
Handling inter-service communication, Feign calls, degradation, and timeout control
Handling internationalization copy and logging standards

Only cross-cutting practices such as AOP, distributed locks, retries, and parameter validation
Only using utility components such as JWT, expression parsing, and thread pools
Only the business logic of a certain module itself

This skill focuses on "microservice foundation capabilities", not single-module business rules.
If the question is more like "how do services communicate with each other, how is configuration split by environment, how are events decoupled", it usually falls here.
First enter the corresponding reference document by topic:
- Conditional configuration:reference/1-conditional-config.md
- Event-driven:reference/2-event-driven.md
- Inter-service communication:reference/3-service-communication.md
- Internationalization and logging:reference/4-i18n-logging.md
If what you want is framework-level cross-cutting practices, switch to common-technical-practices; if what you want is specific utility classes, switch to utility-components。

Multi-environment configuration, events, Feign, and logging/i18n all belong to platform-level infrastructure
The core of such capabilities is stability, maintainability, and cross-module consistency
Inter-service calls must consider timeouts, degradation, circular dependencies, and observability at the same time
Event-driven architecture must prioritize idempotency and asynchronous consistency

Mixing microservice infrastructure with cross-cutting practices
Only writing call logic without handling timeouts, degradation, and tracing
Only integrating MQ without handling idempotency, replay, and event ordering
Logging and i18n lack unified standards, causing fragmented cross-module behavior