smart_message 0.0.6 → 0.0.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eac068dc19706e57d2c66a1dfe36981fbac33e6d7b180fe0429f81d874727cd4
-  data.tar.gz: 91585bc79637c4feab1256716519c0c3c7aa36c2b313ed09ebee7788b11d3f1a
+  metadata.gz: 118cf15fea99493c202bd383a547358a44a3873284cfe656665701213b40b51e
+  data.tar.gz: 7e542557b5b88f2963291232a875ba4dab44c682673251d7e976ac913ff41c14
 SHA512:
-  metadata.gz: a0c0ead05e3cb104873e5cfa53cfc182ee06c6fd2f2e56fe02c0d64a4313dc4356b84d3b5be251e5438e6e381812848f6f587b005a315282204d8160f785f87b
-  data.tar.gz: 3a84537cca151b3b8f3efa16b9ad8591811be19ab5547013fe9f33d7df58474e5db2a74e85e669fb95c17e5b375dd2d889b3a3051b6ded765120dd208246c26a
+  metadata.gz: 637591235fcdf1feb8708f244d1f2f6b416d7330bca7f06c597581ea9ffcb3eb55e74610bcc045c7839e50304f978fd24092c870528a7f3277cd0d8be2620ae4
+  data.tar.gz: 35773299f97565981fc778bd76358c2560eef1d6c4885367ddb66d81448136c8a8a9f402d26477d2c7ac29c885f07906a7e3f0396fb827fdf15e5bbe3e5a43bc

data/CHANGELOG.md

@@ -6,6 +6,61 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
+## [0.0.7] 2025-08-19
+### Added
+- **Production-Grade Circuit Breaker Integration**: Comprehensive reliability patterns using BreakerMachines gem
+  - Circuit breaker protection for message processing operations with configurable failure thresholds
+  - Transport-level circuit breakers for publish/subscribe operations with automatic fallback
+  - Integrated circuit breaker DSL throughout SmartMessage components for production reliability
+  - Memory and Redis storage backends for circuit breaker state persistence
+  - Built-in fallback mechanisms including dead letter queue, retry with exponential backoff, and graceful degradation
+  - Circuit breaker statistics and introspection capabilities for monitoring and debugging
+
+### Fixed
+- **Critical: Redis Transport Header Preservation**: Fixed message header information loss during Redis pub/sub transport
+  - **Root Cause**: Redis transport was only sending message payload through channels, reconstructing generic headers on receive
+  - **Impact**: Message addressing information (`from`, `to`, `reply_to`) was lost, breaking entity-aware filtering and routing
+  - **Solution**: Modified Redis transport to combine header and payload into JSON structure during publish/subscribe
+  - **Result**: Full header information now preserved across Redis transport with backward compatibility fallback
+  - Redis IoT example now displays all expected sensor data, alerts, and real-time device monitoring output
+- **Performance: Dispatcher Shutdown Optimization**: Dramatically improved dispatcher shutdown speed
+  - **Previous Issue**: Slow 1-second polling with no timeout mechanism caused delays up to several minutes
+  - **Optimization**: Replaced with native `wait_for_termination(3)` using Concurrent::ThreadPool built-in timeout
+  - **Performance Gain**: Shutdown now completes in milliseconds instead of seconds
+  - Removed unnecessary circuit breaker wrapper - thread pool handles timeout and fallback natively
+- **Code Quality: Transport Method Signature Consistency**: Ensured all transport `do_publish` methods use consistent parameters
+  - Standardized `do_publish(message_header, message_payload)` signature across all transport implementations
+  - Updated Redis, STDOUT, and Memory transports for consistent interface
+
+### Changed
+- **Dispatcher Architecture**: Simplified shutdown mechanism leveraging Concurrent::ThreadPool native capabilities
+  - Removed custom timeout polling logic in favor of built-in `wait_for_termination` method
+  - Eliminated redundant circuit breaker for shutdown operations - thread pool provides timeout and fallback
+  - **BREAKING**: Removed `router_pool_shutdown` circuit breaker configuration (no longer needed)
+- **Redis Transport Protocol**: Enhanced message format to preserve complete header information
+  - Redis messages now contain both header and payload: `{header: {...}, payload: "..."}`
+  - Automatic fallback to legacy behavior for malformed or old-format messages
+  - Maintains full backward compatibility with existing Redis deployments
+
+### Enhanced
+- **Circuit Breaker Integration**: Strategic application of reliability patterns where most beneficial
+  - Message processing operations protected with configurable failure thresholds and fallback behavior
+  - Transport publish/subscribe operations wrapped with circuit breakers for external service protection
+  - Clean separation between internal operations (thread pools) and external dependencies (Redis, etc.)
+- **Redis Transport Reliability**: Production-ready Redis pub/sub with complete message fidelity
+  - Full message header preservation enables proper entity-aware filtering and routing
+  - IoT examples now demonstrate complete real-time messaging with sensor data, alerts, and device commands
+  - Enhanced error handling with JSON parsing fallbacks for malformed messages
+- **Developer Experience**: Cleaner, more maintainable codebase with proper separation of concerns
+  - Circuit breakers applied strategically for external dependencies, not internal thread management
+  - Simplified shutdown logic leverages proven Concurrent::ThreadPool patterns
+  - Clear distinction between reliability mechanisms and business logic
+
+### Documentation
+- **Circuit Breaker Patterns**: Examples of proper BreakerMachines DSL usage throughout codebase
+  - Strategic application for external service protection vs internal thread management
+  - Configuration examples for different failure scenarios and recovery patterns
+  - Best practices for production-grade messaging reliability
 
 ## [0.0.6] 2025-08-19
 

data/Gemfile.lock

@@ -1,8 +1,9 @@
 PATH
   remote: .
   specs:
-    smart_message (0.0.6)
+    smart_message (0.0.7)
       activesupport
+      breaker_machines
       concurrent-ruby
       hashie
       redis
@@ -27,6 +28,11 @@ GEM
     base64 (0.3.0)
     benchmark (0.4.1)
     bigdecimal (3.2.2)
+    breaker_machines (0.4.0)
+      activesupport (>= 7.2)
+      concurrent-ruby (~> 1.3)
+      state_machines (>= 0.50.0)
+      zeitwerk (~> 2.7)
     concurrent-ruby (1.3.5)
     connection_pool (2.5.3)
     debug_me (1.1.1)
@@ -53,9 +59,11 @@ GEM
     shoulda-context (2.0.0)
     shoulda-matchers (4.5.1)
       activesupport (>= 4.2.0)
+    state_machines (0.100.1)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
     uri (1.0.3)
+    zeitwerk (2.7.3)
 
 PLATFORMS
   arm64-darwin-24

data/examples/01_point_to_point_orders.rb

@@ -92,7 +92,8 @@ class OrderService
       customer_id: customer_id,
       amount: amount,
       payment_method: payment_method,
-      items: items
+      items: items,
+      from: 'OrderService'
     )
     
     puts "🏪 OrderService: Sending order to payment processing..."
@@ -132,7 +133,8 @@ class PaymentService
       payment_id: payment_id,
       status: success ? 'success' : 'failed',
       message: success ? 'Payment processed successfully' : 'Insufficient funds',
-      processed_at: Time.now.iso8601
+      processed_at: Time.now.iso8601,
+      from: 'PaymentService'
     )
     
     puts "💳 PaymentService: Sending payment response..."

data/examples/02_publish_subscribe_events.rb

@@ -270,7 +270,8 @@ class UserManager
       user_email: user_email,
       user_name: user_name,
       timestamp: Time.now.iso8601,
-      metadata: metadata
+      metadata: metadata,
+      from: 'UserManager'
     )
     
     puts "👤 UserManager: Publishing #{event_type} event..."

data/examples/03_many_to_many_chat.rb

@@ -164,7 +164,8 @@ class HumanChatAgent
         message_type: 'user',
         timestamp: Time.now.iso8601,
         mentions: mentions,
-        metadata: { client: 'human_agent' }
+        metadata: { client: 'human_agent' },
+        from: @user_id
       )
       
       message.publish
@@ -228,7 +229,8 @@ class HumanChatAgent
       user_id: @user_id,
       command: command,
       parameters: parameters,
-      timestamp: Time.now.iso8601
+      timestamp: Time.now.iso8601,
+      from: @user_id
     )
     
     bot_command.publish
@@ -259,7 +261,8 @@ class HumanChatAgent
       notification_type: notification_type,
       content: content,
       timestamp: Time.now.iso8601,
-      metadata: { triggered_by: @user_id }
+      metadata: { triggered_by: @user_id },
+      from: @user_id
     )
     
     notification.publish
@@ -444,7 +447,8 @@ class BotAgent
       message_type: 'bot',
       timestamp: Time.now.iso8601,
       mentions: [],
-      metadata: { bot_type: 'service_bot' }
+      metadata: { bot_type: 'service_bot' },
+      from: @bot_id
     )
     
     message.publish
@@ -480,7 +484,8 @@ class RoomManager
       notification_type: 'room_created',
       content: "Room '#{name}' was created",
       timestamp: Time.now.iso8601,
-      metadata: { description: description }
+      metadata: { description: description },
+      from: 'RoomManager'
     )
     
     notification.publish

data/examples/04_redis_smart_home_iot.rb

@@ -234,7 +234,7 @@ class SmartThermostat
         @battery_level -= 0.1 if rand < 0.1   # Occasional battery drain
         
         # Publish sensor data
-        SensorDataMessage.new(
+        sensor_msg = SensorDataMessage.new(
           device_id: @device_id,
           device_type: 'thermostat',
           location: @location,
@@ -242,8 +242,11 @@ class SmartThermostat
           value: @current_temp.round(1),
           unit: 'celsius',
           timestamp: Time.now.iso8601,
-          battery_level: @battery_level.round(1)
-        ).publish
+          battery_level: @battery_level.round(1),
+          from: @device_id
+        )
+        puts "🌡️  #{@device_id}: Publishing temperature #{@current_temp.round(1)}°C"
+        sensor_msg.publish
 
         # Check for alerts
         if @current_temp > 28.0
@@ -255,7 +258,8 @@ class SmartThermostat
             location: @location,
             message: "Temperature too high: #{@current_temp.round(1)}°C",
             timestamp: Time.now.iso8601,
-            requires_action: true
+            requires_action: true,
+            from: @device_id
           ).publish
         end
 
@@ -325,7 +329,8 @@ class SecurityCamera
             value: true,
             unit: 'boolean',
             timestamp: Time.now.iso8601,
-            battery_level: @battery_level.round(1)
+            battery_level: @battery_level.round(1),
+            from: @device_id
           ).publish
 
           # Send security alert
@@ -337,7 +342,8 @@ class SecurityCamera
             location: @location,
             message: "Motion detected in #{@location}",
             timestamp: Time.now.iso8601,
-            requires_action: false
+            requires_action: false,
+            from: @device_id
           ).publish
           
           # Auto-start recording
@@ -346,7 +352,8 @@ class SecurityCamera
             command: 'start_recording',
             parameters: { duration: 30 },
             requested_by: 'motion_detector',
-            timestamp: Time.now.iso8601
+            timestamp: Time.now.iso8601,
+            from: @device_id
           ).publish
           
         elsif !motion_detected && @motion_detected
@@ -361,7 +368,8 @@ class SecurityCamera
             value: false,
             unit: 'boolean',
             timestamp: Time.now.iso8601,
-            battery_level: @battery_level.round(1)
+            battery_level: @battery_level.round(1),
+            from: @device_id
           ).publish
         end
 
@@ -424,7 +432,8 @@ class SmartDoorLock
           value: @locked ? 'locked' : 'unlocked',
           unit: 'string',
           timestamp: Time.now.iso8601,
-          battery_level: @battery_level.round(1)
+          battery_level: @battery_level.round(1),
+          from: @device_id
         ).publish
 
         # Check for low battery
@@ -437,7 +446,8 @@ class SmartDoorLock
             location: @location,
             message: "Door lock battery low: #{@battery_level.round(1)}%",
             timestamp: Time.now.iso8601,
-            requires_action: true
+            requires_action: true,
+            from: @device_id
           ).publish
         end
 
@@ -528,7 +538,8 @@ class IoTDashboard
           summary_stats: {
             total_devices: @@devices.size,
             avg_battery: @@devices.values.map { |d| d[:battery_level] || 100 }.sum / [@@devices.size, 1].max
-          }
+          },
+          from: 'IoTDashboard'
         ).publish
       end
     end
@@ -592,13 +603,16 @@ class SmartHomeDemo
     puts "\n🎛️  Sending some manual commands..."
     sleep(2)
     
-    DeviceCommandMessage.new(
+    cmd_msg = DeviceCommandMessage.new(
       device_id: "THERM-001",
       command: "set_temperature",
       parameters: { target: 24.0 },
       requested_by: "mobile_app",
-      timestamp: Time.now.iso8601
-    ).publish
+      timestamp: Time.now.iso8601,
+      from: 'SmartHomeDemo'
+    )
+    puts "🎛️  Publishing command: set_temperature for THERM-001"
+    cmd_msg.publish
     
     sleep(3)
     
@@ -607,7 +621,8 @@ class SmartHomeDemo
       command: "start_recording",
       parameters: { duration: 60 },
       requested_by: "security_schedule",
-      timestamp: Time.now.iso8601
+      timestamp: Time.now.iso8601,
+      from: 'SmartHomeDemo'
     ).publish
     
     sleep(2)
@@ -617,7 +632,8 @@ class SmartHomeDemo
       command: "get_status",
       parameters: {},
       requested_by: "mobile_app",
-      timestamp: Time.now.iso8601
+      timestamp: Time.now.iso8601,
+      from: 'SmartHomeDemo'
     ).publish
     
     puts "\n⏳ Monitoring for 30 seconds (watch the Redis channels!)..."

data/examples/05_proc_handlers.rb

@@ -137,7 +137,7 @@ notifications = [
 notifications.each_with_index do |notification_data, index|
   puts "\n📤 Publishing notification #{index + 1}: #{notification_data[:title]}"
 
-  notification = NotificationMessage.new(**notification_data)
+  notification = NotificationMessage.new(**notification_data, from: 'ProcHandlerDemo')
   notification.publish
 
   # Give time for all handlers to process
@@ -161,7 +161,8 @@ error_notification = NotificationMessage.new(
   title: 'Another Error',
   message: 'This error won\'t trigger the block handler',
   user_id: 'test_user',
-  timestamp: Time.now.iso8601
+  timestamp: Time.now.iso8601,
+  from: 'ProcHandlerDemo'
 )
 
 error_notification.publish

data/examples/06_custom_logger_example.rb

@@ -470,7 +470,7 @@ class PriorityOrderService
   
   def process_priority_order(order_data)
     # Create message with instance-level logger override
-    message = OrderProcessingMessage.new(**order_data)
+    message = OrderProcessingMessage.new(**order_data, from: 'PriorityOrderService')
     
     # Override the logger at instance level
     message.logger(@priority_logger)
@@ -506,7 +506,8 @@ class LoggerDemo
     DefaultLoggerMessage.subscribe
     default_msg = DefaultLoggerMessage.new(
       message: "Testing the built-in default logger",
-      level: "info"
+      level: "info",
+      from: 'LoggerDemo'
     )
     default_msg.publish
     sleep(0.5)
@@ -518,7 +519,8 @@ class LoggerDemo
       customer_id: "CUST-123",
       amount: 99.99,
       status: "pending",
-      items: ["Widget A", "Widget B"]
+      items: ["Widget A", "Widget B"],
+      from: 'LoggerDemo'
     )
     order1.publish
     sleep(0.5)
@@ -529,7 +531,8 @@ class LoggerDemo
       recipient: "customer@example.com",
       subject: "Order Confirmation",
       body: "Your order has been received",
-      priority: "normal"
+      priority: "normal",
+      from: 'LoggerDemo'
     )
     notification.publish
     sleep(0.5)
@@ -542,7 +545,8 @@ class LoggerDemo
       customer_id: "VIP-456",
       amount: 299.99,
       status: "urgent",
-      items: ["Premium Widget", "Express Shipping"]
+      items: ["Premium Widget", "Express Shipping"],
+      from: 'PriorityOrderService'
     )
     sleep(0.5)
     
@@ -555,7 +559,8 @@ class LoggerDemo
     # Create and send a message - watch for the Ruby logger output
     msg = StandardLoggerMessage.new(
       content: "Testing with Ruby's standard logger",
-      level: "info"
+      level: "info",
+      from: 'LoggerDemo'
     )
     
     # The logger will output to STDOUT using Ruby's standard format
@@ -573,7 +578,8 @@ class LoggerDemo
         order_id: nil,  # This might cause issues
         customer_id: "ERROR-TEST",
         amount: "invalid_amount",
-        status: "error_demo"
+        status: "error_demo",
+        from: 'LoggerDemo'
       )
       
       # Simulate an error during processing

data/examples/07_error_handling_scenarios.rb

@@ -167,7 +167,8 @@ class ErrorDemonstrator
       missing_user_id = UserRegistrationMessage.new(
         email: "john@example.com",
         age: 25,
-        username: "johndoe"
+        username: "johndoe",
+        from: 'ErrorDemonstrator'
       )
       puts "❌ ERROR: Should have failed but didn't!"
     rescue => e
@@ -181,7 +182,8 @@ class ErrorDemonstrator
     begin
       missing_multiple = UserRegistrationMessage.new(
         user_id: "USER-123",
-        username: "johndoe"
+        username: "johndoe",
+        from: 'ErrorDemonstrator'
       )
       puts "❌ ERROR: Should have failed but didn't!"
     rescue => e
@@ -197,7 +199,8 @@ class ErrorDemonstrator
         user_id: "USER-123",
         email: "john@example.com", 
         age: 25,
-        username: "johndoe"
+        username: "johndoe",
+        from: 'ErrorDemonstrator'
       )
       puts "✅ Message created successfully"
       puts "   User: #{valid_user.username} (#{valid_user.email})"
@@ -227,7 +230,8 @@ class ErrorDemonstrator
         user_id: "USER-124",
         email: "not-an-email",  # Invalid format
         age: 25,
-        username: "janedoe"
+        username: "janedoe",
+        from: 'ErrorDemonstrator'
       )
       puts "   Message created, now validating..."
       invalid_email.validate!  # Explicitly trigger validation
@@ -245,7 +249,8 @@ class ErrorDemonstrator
         user_id: "USER-125",
         email: "kid@example.com",
         age: 10,  # Too young (< 13)
-        username: "kiduser"
+        username: "kiduser",
+        from: 'ErrorDemonstrator'
       )
       puts "   Message created, now validating..."
       invalid_age.validate!  # Explicitly trigger validation
@@ -263,7 +268,8 @@ class ErrorDemonstrator
         user_id: "USER-126",
         email: "user@example.com",
         age: 30,
-        username: "user@123!"  # Contains invalid characters
+        username: "user@123!",  # Contains invalid characters
+        from: 'ErrorDemonstrator'
       )
       puts "   Message created, now validating..."
       invalid_username.validate!  # Explicitly trigger validation
@@ -282,7 +288,8 @@ class ErrorDemonstrator
         email: "user@example.com",
         age: 30,
         username: "validuser",
-        subscription_type: "platinum"  # Not in allowed list
+        subscription_type: "platinum",  # Not in allowed list
+        from: 'ErrorDemonstrator'
       )
       puts "   Message created, now validating..."
       invalid_subscription.validate!  # Explicitly trigger validation
@@ -301,7 +308,8 @@ class ErrorDemonstrator
         email: "valid@example.com",
         age: 25,
         username: "validuser123",
-        subscription_type: "premium"
+        subscription_type: "premium",
+        from: 'ErrorDemonstrator'
       )
       puts "   Message created, now validating..."
       valid_user.validate!  # Explicitly trigger validation
@@ -339,7 +347,8 @@ class ErrorDemonstrator
         user_id: "USER-V1-001",
         email: "v1user@example.com",
         age: 28,
-        username: "v1user"
+        username: "v1user",
+        from: 'ErrorDemonstrator'
       )
       puts "✅ V1 Message created (version #{v1_message._sm_header.version})"
       v1_message.publish
@@ -356,7 +365,8 @@ class ErrorDemonstrator
         email: "v2user@example.com",
         age: 32,
         username: "v2user",
-        phone_number: "+1234567890"
+        phone_number: "+1234567890",
+        from: 'ErrorDemonstrator'
       )
       puts "✅ V2 Message created (version #{v2_message._sm_header.version})"
       v2_message.publish
@@ -374,7 +384,8 @@ class ErrorDemonstrator
         user_id: "USER-MISMATCH-001",
         email: "mismatch@example.com",
         age: 35,
-        username: "mismatchuser"
+        username: "mismatchuser",
+        from: 'ErrorDemonstrator'
       )
       
       puts "✅ Original message created with version #{version_mismatch_message._sm_header.version}"
@@ -396,8 +407,8 @@ class ErrorDemonstrator
 
     # Test Case 4: Show version information
     puts "📊 Test Case 3D: Version information display"
-    v1_msg = UserRegistrationMessage.new(user_id: "INFO-V1", email: "info@example.com", age: 25, username: "infouser")
-    v2_msg = UserRegistrationMessageV2.new(user_id: "INFO-V2", email: "info@example.com", age: 25, username: "infouser", phone_number: "+1234567890")
+    v1_msg = UserRegistrationMessage.new(user_id: "INFO-V1", email: "info@example.com", age: 25, username: "infouser", from: 'ErrorDemonstrator')
+    v2_msg = UserRegistrationMessageV2.new(user_id: "INFO-V2", email: "info@example.com", age: 25, username: "infouser", phone_number: "+1234567890", from: 'ErrorDemonstrator')
     
     puts "📋 Version Information:"
     puts "   UserRegistrationMessage (V1):"
@@ -424,7 +435,7 @@ class ErrorDemonstrator
     puts "Expected: Ideally should report all missing fields"
     puts "Actual Hashie::Dash behavior:"
     begin
-      message = MultiRequiredMessage.new(optional_field: "present")
+      message = MultiRequiredMessage.new(optional_field: "present", from: 'ErrorDemonstrator')
       puts "❌ ERROR: Should have failed but didn't!"
     rescue => e
       puts "✅ Error caught: #{e.class.name}"
@@ -443,7 +454,7 @@ class ErrorDemonstrator
     test_data.each_with_index do |test_case, index|
       puts "   #{index + 1}. #{test_case[:name]}:"
       begin
-        message = MultiRequiredMessage.new(test_case[:data])
+        message = MultiRequiredMessage.new(test_case[:data].merge(from: 'ErrorDemonstrator'))
         puts "      ✅ Success: Message created"
       rescue => e
         field_name = e.message.match(/property '([^']+)'/)[1] rescue 'unknown'

data/examples/08_entity_addressing_basic.rb

@@ -62,7 +62,8 @@ order = OrderMessage.new(
   order_id: "ORD-2024-001",
   customer_id: "CUST-12345",
   items: ["Widget A", "Widget B", "Gadget C"],
-  total_amount: 299.99
+  total_amount: 299.99,
+  from: 'order-service'
 )
 
 puts "\n📤 Publishing point-to-point order message..."
@@ -111,7 +112,8 @@ SystemAnnouncementMessage.subscribe
 announcement = SystemAnnouncementMessage.new(
   message: "System maintenance scheduled for tonight at 2:00 AM EST",
   priority: 'high',
-  effective_time: '2024-12-20 02:00:00 EST'
+  effective_time: '2024-12-20 02:00:00 EST',
+  from: 'admin-service'
 )
 
 puts "\n📤 Publishing broadcast announcement..."
@@ -192,7 +194,8 @@ UserLookupResponse.subscribe
 request = UserLookupRequest.new(
   user_id: "USER-789",
   request_id: SecureRandom.uuid,
-  requested_fields: ['name', 'email', 'last_login']
+  requested_fields: ['name', 'email', 'last_login'],
+  from: 'web-service'
 )
 
 puts "\n📤 Publishing user lookup request..."
@@ -208,7 +211,8 @@ response = UserLookupResponse.new(
     email: "alice@example.com",
     last_login: "2024-12-19 14:30:00"
   },
-  success: true
+  success: true,
+  from: 'user-service'
 )
 response.to('web-service')  # Set reply destination
 
@@ -261,7 +265,8 @@ normal_payment = PaymentMessage.new(
   payment_id: "PAY-001",
   amount: 150.00,
   account_id: "ACCT-12345",
-  payment_method: 'credit_card'
+  payment_method: 'credit_card',
+  from: 'payment-service'
 )
 
 puts "\n📤 Publishing normal payment (using class defaults)..."
@@ -275,7 +280,8 @@ backup_payment = PaymentMessage.new(
   payment_id: "PAY-002",
   amount: 75.50,
   account_id: "ACCT-67890",
-  payment_method: 'debit_card'
+  payment_method: 'debit_card',
+  from: 'payment-service'
 )
 
 # Override instance addressing
@@ -338,7 +344,8 @@ external_message = ExternalAPIMessage.new(
   api_call: "PUT /api/v1/users/USER-123",
   payload_data: internal_data,
   authentication_token: "Bearer abc123xyz789",
-  partner_id: "PARTNER-ALPHA"
+  partner_id: "PARTNER-ALPHA",
+  from: 'api-gateway'
 )
 
 # Gateway can override destination based on routing rules