Add, change, or debug external API integrations, vendor SDK adapters, and bridges to legacy business workflows. Use when an Action or domain service needs an outer technical dependency.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Put concrete external adapters in App\Infrastructure\Integrations, grouped by provider when useful. Legacy workflow bridges may live in App\Infrastructure\Legacy. Keep HTTP clients, SDK objects, transport failures, and provider-specific payloads at this boundary; translate them into consumer concepts.
A consumer in Domain or Application cannot depend on a concrete Infrastructure class. This boundary is a concrete reason for a contract:
App\Application\<Capability>\Contracts.App\Domain\<Capability>\Contracts.// App\Application\Orders\Contracts\PaymentGateway
interface PaymentGateway
{
public function refund(string $paymentReference, string $idempotencyKey): void;
}
// In a service provider's register() method:
$this->app->bind(
\App\Application\Orders\Contracts\PaymentGateway::class,
\App\Infrastructure\Integrations\Payments\ProviderPaymentGateway::class,
);
After OrderCancelled commits, a queued listener can invoke a refund Action that receives PaymentGateway. The adapter implements that interface and translates the provider response. Derive a stable idempotency key for a refund operation and use the provider's supported mechanism or an application deduplication strategy.
Do not inject SDK types into the contract or resolve concrete adapters from Actions through app(), strings, or custom facades. Do not create an interface for every helper inside Infrastructure.
Keep external calls outside database transactions where possible. A local rollback cannot reverse a remote refund; design retries and failure handling for the actual use case rather than treating the database transaction as distributed atomicity.
For migrated code using legacy business workflows, the same contract/adapter pattern applies. Direct Eloquent persistence is still allowed; it must not become a shortcut into legacy workflow orchestration.
Use events by default for asynchronous reactions. A scheduling contract is warranted only for a real infrastructure capability, not merely because a Job exists.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Create, modify, or refactor application use cases into Laravel-native DDD Actions. Use for business operations such as placing or cancelling orders, extracting controller orchestration, and fixing use-case behavior.
中文简介正在准备中。当前显示原文说明。
Create or change structured input for application use cases, including extracting HTTP request data for Actions invoked from controllers, jobs, or commands. Avoid DTOs for trivial scalar input.
中文简介正在准备中。当前显示原文说明。
Create, modify, or debug business events and their follow-up reactions, including order cancellation events, queued listeners, transaction timing, and rollback behavior.
中文简介正在准备中。当前显示原文说明。
Create, extend, or fix Eloquent business models and their state transitions. Use when moving business rules out of controllers or Actions, or explicitly migrating a model into a DDD capability.
中文简介正在准备中。当前显示原文说明。
Create or refactor business calculations and rules spanning multiple domain objects when no single entity or value object naturally owns the behavior. Use when assessing a growing service class.
中文简介正在准备中。当前显示原文说明。
Create or change immutable business values with meaningful invariants, equality, or behavior, such as order numbers and money. Use when primitive values obscure domain rules; avoid wrapping every scalar.
中文简介正在准备中。当前显示原文说明。