Does this skill provide actual code for message buses?

This skill acts as a decision guide; for specific implementation details and code patterns, it should be used in conjunction with the backend-message-bus skill.

How does the skill handle initial data population?

It recommends the Full Sync Job pattern for initial data migration or population, often utilized via the backend-background-job skill.

When should I use an Entity Event Bus instead of a direct API call?

Use an Entity Event Bus when the source service owns the data, target services require local copies for performance, and eventual consistency is acceptable for your business logic.

Why does this skill forbid shared database access?

Shared databases create tight coupling between services, making them difficult to scale, deploy, and maintain independently. It violates the core principles of microservices.

What is the primary goal of this integration guide?

The primary goal is to ensure high decoupling between services while maintaining data integrity through ownership and idempotent message consumption.

Cross-Service Integration Architect

Name: Cross-Service Integration Architect
Author: CongDon1207

byCongDon1207

•

API Development

Guides the selection and implementation of communication patterns between backend services to ensure data consistency and architectural integrity.

About

This skill provides a strategic decision framework for handling cross-service communication in distributed systems. It helps developers choose between entity event buses, direct API calls, or background sync jobs while enforcing critical architectural principles such as strict data ownership and the 'No Shared Database' rule. By acting as a high-level architectural guide, it ensures that microservices remain decoupled and idempotent, streamlining the path from design to implementation by integrating with specialized message bus and background job skills.

Key Features

Prevents architectural anti-patterns like direct cross-service database access
Provides a quick decision matrix for selecting optimal communication patterns
1 GitHub stars
Guides the implementation of entity event buses for eventual consistency
Standardizes idempotency and message handling for service consumers
Enforces strict data ownership principles across distributed services

Use Cases

Establishing architectural guardrails for junior developers building microservices
Designing a data synchronization strategy for local entity copies in downstream services
Deciding whether to use a synchronous REST API or an asynchronous Message Bus for a new feature

About

Key Features

Prevents architectural anti-patterns like direct cross-service database access
Provides a quick decision matrix for selecting optimal communication patterns
1 GitHub stars
Guides the implementation of entity event buses for eventual consistency
Standardizes idempotency and message handling for service consumers
Enforces strict data ownership principles across distributed services

Use Cases

Establishing architectural guardrails for junior developers building microservices
Designing a data synchronization strategy for local entity copies in downstream services
Deciding whether to use a synchronous REST API or an asynchronous Message Bus for a new feature