docs: update documentation after event system removal

- Remove event system configuration from .example.env
- Remove event system section from CONFIGURATION.md
- Update README.md to show WithJob instead of WithEvent
- Update ROADMAP.md to mark job system as implemented
- Update docs/index.md feature list with job system
- Remove 03-event-driven example directory
- Update examples/README.md learning path and patterns

Author: anxuanzi

.example.env

@@ -222,41 +222,6 @@ CACHE_STORE=memory
 # CACHE_S3_BUCKET=my-cache-bucket
 # CACHE_S3_REGION=us-east-1
 
-# -----------------------------------------------------------------------------
-# Event System (Redis Streams) - Enable with WithEvent: true
-# -----------------------------------------------------------------------------
-
-# --- Redis Connection ---
-
-# Option 1: Connection URL (recommended)
-# EVENT_REDIS_URL=redis://localhost:6379/0
-
-# Option 2: Individual settings
-# EVENT_REDIS_HOSTS=localhost:6379
-# EVENT_REDIS_USERNAME=default
-# EVENT_REDIS_PASSWORD=secret
-# EVENT_REDIS_DB=0
-
-# Legacy (deprecated)
-# EVENT_REDIS_ADDR=localhost:6379
-
-# --- Consumer Settings ---
-# EVENT_CONSUMER_TIMEOUT=30s
-# EVENT_MAX_RETRIES=3
-# EVENT_RETRY_BACKOFF=1s
-# EVENT_DLQ_TTL=24h
-# EVENT_STALE_CONSUMER_TIMEOUT=5m
-
-# --- Performance ---
-# EVENT_BATCH_SIZE=10
-# EVENT_MAX_PENDING_MESSAGES=1000
-# EVENT_CLAIM_MIN_IDLE_TIME=1m
-# EVENT_CLAIM_INTERVAL=30s
-
-# --- Delayed Queue ---
-# EVENT_DELAYED_QUEUE_ENABLED=true
-# EVENT_DELAYED_QUEUE_CHECK_INTERVAL=1s
-
 # -----------------------------------------------------------------------------
 # Lock System (Distributed Mutex) - Enable with WithLock: true
 # -----------------------------------------------------------------------------

CONFIGURATION.md

@@ -264,49 +264,6 @@ GOE supports multiple MongoDB connections. The default connection uses `MONGO_*`
 
 ---
 
-## Event System (Redis Streams)
-
-The event system uses Redis Streams for pub/sub messaging with support for consumer groups, dead letter queues, and delayed messages.
-
-### Redis Connection
-
-| Variable | Type | Default | Description |
-|----------|------|---------|-------------|
-| `EVENT_REDIS_URL` | string | - | Redis connection URL (priority over individual settings) |
-| `EVENT_REDIS_HOSTS` | []string | `localhost:6379` | Comma-separated Redis hosts |
-| `EVENT_REDIS_ADDR` | string | `localhost:6379` | Redis address (legacy, use `EVENT_REDIS_URL` or `EVENT_REDIS_HOSTS`) |
-| `EVENT_REDIS_USERNAME` | string | - | Redis username |
-| `EVENT_REDIS_PASSWORD` | string | - | Redis password |
-| `EVENT_REDIS_DB` | int | `0` | Redis database number |
-
-### Consumer Settings
-
-| Variable | Type | Default | Description |
-|----------|------|---------|-------------|
-| `EVENT_CONSUMER_TIMEOUT` | duration | `30s` | Consumer read timeout |
-| `EVENT_MAX_RETRIES` | int | `3` | Maximum retry attempts for failed messages |
-| `EVENT_RETRY_BACKOFF` | duration | `1s` | Delay between retries |
-| `EVENT_DLQ_TTL` | duration | `24h` | Dead letter queue message TTL |
-| `EVENT_STALE_CONSUMER_TIMEOUT` | duration | `5m` | Timeout for stale consumer detection |
-
-### Performance Settings
-
-| Variable | Type | Default | Description |
-|----------|------|---------|-------------|
-| `EVENT_BATCH_SIZE` | int | `10` | Number of messages to fetch per batch |
-| `EVENT_MAX_PENDING_MESSAGES` | int | `1000` | Maximum pending messages per consumer |
-| `EVENT_CLAIM_MIN_IDLE_TIME` | duration | `1m` | Minimum idle time before claiming messages |
-| `EVENT_CLAIM_INTERVAL` | duration | `30s` | Interval for checking claimable messages |
-
-### Delayed Queue
-
-| Variable | Type | Default | Description |
-|----------|------|---------|-------------|
-| `EVENT_DELAYED_QUEUE_ENABLED` | bool | `true` | Enable delayed message queue |
-| `EVENT_DELAYED_QUEUE_CHECK_INTERVAL` | duration | `1s` | Interval for processing delayed messages |
-
----
-
 ## Lock System (Distributed Mutex)
 
 The lock system provides distributed locking using Redis with support for single instance, Sentinel, Cluster, and Redlock algorithms.

README.md

@@ -120,7 +120,7 @@ WithHTTP:    true, // HTTP server (Fiber)
 WithCache:   true, // Caching system
 WithDB:      true, // SQL database (GORM)
 WithMongoDB: true, // MongoDB
-WithEvent:   true,  // Event system (Redis Streams)
+WithJob:     true, // Background job processing (Redis)
 WithLock:    true, // Distributed locking
 })
 ```

ROADMAP.md

@@ -16,7 +16,7 @@
 - GoFiber v3 - fastest Go HTTP framework
 - Uber Zap - production-grade structured logging
 - GORM - mature ORM with good ecosystem
-- Redis Streams - scalable, persistent event system
+- Redis - background job processing and distributed locking
 
 **Production Readiness**
 - Health checks with liveness/readiness probes (K8s-ready)
@@ -34,7 +34,7 @@
 | `db` | ✅ Stable | GORM SQL database (MySQL, PostgreSQL, SQLite, SQL Server) |
 | `mongodb` | ✅ Stable | MongoDB native driver |
 | `cache` | ✅ Stable | Multi-backend caching (Redis, Memory, etc.) |
-| `event` | ✅ Stable | Redis Streams pub/sub with consumer groups |
+| `job` | ✅ Stable | Background job processing with scheduling and retries |
 | `lock` | ✅ Stable | Distributed locking (Redlock) |
 | `health` | ✅ Stable | Health checks (liveness/readiness) |
 | `metrics` | ✅ Stable | Prometheus metrics |
@@ -62,20 +62,21 @@
 
 **Impact:** Very high - almost every app needs authentication
 
-#### 2. Background Jobs / Task Queue
-**Current State:** Event system exists but no job queue
+#### 2. Background Jobs / Task Queue ✅ IMPLEMENTED
+**Current State:** Fully implemented with Redis backend
 
-**What's Missing:**
-- Delayed job execution ("run this in 5 minutes")
-- Scheduled/cron jobs ("run every hour")
-- Persistent job queue (Redis/DB-backed)
-- Retry with exponential backoff
-- Dead letter queue for failed jobs
-- Job priorities and queues
-- Concurrency control
-- Job progress tracking
+**Features:**
+- ✅ Delayed job execution ("run this in 5 minutes")
+- ✅ Scheduled/cron jobs with human-friendly syntax
+- ✅ Persistent job queue (Redis-backed)
+- ✅ Retry with exponential backoff
+- ✅ Dead letter queue for failed jobs
+- ✅ Multiple named queues
+- ✅ Concurrency control
+- ✅ Job uniqueness/deduplication
+- ✅ Health checks and statistics
 
-**Impact:** High - async processing is fundamental to scalable apps
+**Impact:** Completed - enable with `WithJob: true`
 
 #### 3. Database Migrations
 **Current State:** Only GORM AutoMigrate (not suitable for production)
@@ -163,7 +164,6 @@
 - Rooms/channels abstraction
 - Broadcast helpers
 - Presence tracking
-- Integration with event system
 
 #### 11. GraphQL Support
 **What's Missing:**

docs/index.md

@@ -41,9 +41,9 @@ features:
     -   icon: 🗄️
         title: GORM Database Integration
         details: Seamless integration with GORM for database operations, supporting MySQL, PostgreSQL, SQLite, and SQL Server.
-    -   icon: 🔄
-        title: Event System
-        details: Built-in event system using Redis Streams for publish-subscribe patterns, consumer groups, dead letter queues, and delayed message processing.
+    -   icon: 📋
+        title: Job System
+        details: Production-ready background job processing with human-friendly scheduling, delayed execution, retries with exponential backoff, and dead letter queues.
     -   icon: 🍃
         title: MongoDB Support
         details: Native MongoDB integration with connection pooling, multiple database support, and helper utilities for indexes and transactions.