From 2c8a6e47eebbc9d089b7b33ec356505a632fbcf2 Mon Sep 17 00:00:00 2001 From: maliming Date: Tue, 24 Mar 2026 21:13:16 +0800 Subject: [PATCH] Add ABP 10.3 availability note to dynamic features articles --- .../POST.md | 2 ++ .../Community-Articles/2026-03-23-Dynamic-Events-in-ABP/POST.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docs/en/Community-Articles/2026-03-21-Dynamic-Background-Jobs-and-Workers-in-ABP/POST.md b/docs/en/Community-Articles/2026-03-21-Dynamic-Background-Jobs-and-Workers-in-ABP/POST.md index 06e7e3bf10..ed02df79e6 100644 --- a/docs/en/Community-Articles/2026-03-21-Dynamic-Background-Jobs-and-Workers-in-ABP/POST.md +++ b/docs/en/Community-Articles/2026-03-21-Dynamic-Background-Jobs-and-Workers-in-ABP/POST.md @@ -1,5 +1,7 @@ # Dynamic Background Jobs and Workers in ABP +> This feature is available since ABP 10.3. + ABP's Background Jobs and Background Workers are two well-established infrastructure pieces. Background jobs handle fire-and-forget async tasks — sending emails, generating reports, processing orders. Background workers handle continuously running periodic tasks — syncing inventory, cleaning up expired data, pushing scheduled notifications. This works great, but it has one assumption: **you know all your job and worker types at compile time**. diff --git a/docs/en/Community-Articles/2026-03-23-Dynamic-Events-in-ABP/POST.md b/docs/en/Community-Articles/2026-03-23-Dynamic-Events-in-ABP/POST.md index 1195a6953c..cdc1a03f58 100644 --- a/docs/en/Community-Articles/2026-03-23-Dynamic-Events-in-ABP/POST.md +++ b/docs/en/Community-Articles/2026-03-23-Dynamic-Events-in-ABP/POST.md @@ -1,5 +1,7 @@ # Dynamic Events in ABP +> This feature is available since ABP 10.3. + ABP's Event Bus is a core infrastructure piece. The **Local Event Bus** handles in-process communication between services. The **Distributed Event Bus** handles cross-service communication over message brokers like RabbitMQ, Kafka, Azure Service Bus, and Rebus. Both are fully type-safe — you define event types at compile time, register handlers via DI, and everything is wired up automatically. This works great, but it has one assumption: **you know all your event types at compile time**.