smart_message 0.0.12 → 0.0.13

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2e7bd096698c7b656fc3800dcbbd88366dccb0ae36be0a9a1f50240c944a6de3
-  data.tar.gz: 13235c27c12c4f76bdae091b0a432b505f0cfe49cd571fde387358aba98cf7da
+  metadata.gz: 38b75aa70a9ab79b0fd9ac311d7e5634491789e5813161630ff7e04f17d61373
+  data.tar.gz: 8196665b3a660cfaad1c30753697f020c4a54b50c25d23be6f6c3c6ad9149e38
 SHA512:
-  metadata.gz: 2b9b74f2203c1c6cd95a981e4f7c89d9fb6e1aad112c99b61420521ce95e89b4f3c378936ba9f435f67ee548b88e2e2ea28d70216856eaf898c028f1058f5d04
-  data.tar.gz: f7a9636706cb07e2b8df17e0e25b13128a2aed8a4ddd3d80ab28fadee3e27fc1ac52fafa9593f9854ffa54fb5920fe93334fb7f361c3394929c1fe4ea9be2adb
+  metadata.gz: 876f94f732eb022c568a200747438ab6a0938602735f89601fc7c9e48f34bf21791c75608b2d877475d9190a9629974a63448f5ceb6eeb24bf073b0cc1e4ee19
+  data.tar.gz: 310150522f4d6561c40e7322072a75778867b643b5eb6b79364b750a39689e27cbfd7c7022ae0f0c8a44ae9a850549c02e94005930d4b878ba75cb1eb1192a58

data/CHANGELOG.md

@@ -7,10 +7,44 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.0.13] 2025-09-10
+
+### Changed
+- **BREAKING: Transport-Level Serialization Architecture**: Major architectural rework moving serializer responsibility from message classes to transport layer
+  - **Core Change**: Serializers now associated with transports instead of message classes, enabling different transports to use different serialization formats
+  - **Message Structure**: Eliminated wrapper objects in favor of flat message structure with `_sm_header` routing metadata
+  - **Serialization Format**: Messages now serialized as single JSON objects containing both header and payload data (e.g., `{"_sm_header": {...}, "content": "value", "property": "data"}`)
+  - **Transport Flexibility**: Each transport can now use its own serializer (JSON, MessagePack, etc.) independently
+  - **Backward Compatibility**: Added `_sm_payload` and `split` methods to maintain compatibility with existing proc handlers
+  - **Performance**: Simplified message processing pipeline with direct message instance passing instead of complex wrapper handling
+
+### Fixed
+- **Message Reconstruction**: Fixed critical bug in `SmartMessage::Base#initialize` where payload properties were not properly extracted from flat serialized structure
+  - **Root Cause**: Initialization logic looked for `props[:_sm_payload]` but flat structure stores properties directly in `props`
+  - **Solution**: Changed to `payload_props = props.except(:_sm_header)` to extract all non-header properties
+  - **Impact**: Proc handlers now receive correct message content, resolving nil property values in `_sm_payload`
+- **Circuit Breaker Test Compatibility**: Updated circuit breaker tests to use new transport method signatures
+  - **Issue**: Tests were calling `transport.publish(header, payload)` with two arguments
+  - **Fix**: Updated to `transport.publish(message_instance)` with single message parameter
+  - **Result**: All circuit breaker tests now pass with new architecture
+- **Deduplication Test Format**: Updated deduplication tests from old wrapper format to new flat structure
+  - **Changed**: `_sm_payload: { content: "value" }` → `content: "value"`
+  - **Maintained**: Full deduplication functionality with handler-scoped DDQ system
+
+### Enhanced
+- **Transport Serialization Control**: Each transport implementation can now specify its preferred serializer
+  - **Memory Transport**: Returns message objects directly without serialization for performance
+  - **STDOUT Transport**: Uses JSON serializer with pretty printing for human readability
+  - **Redis Transport**: Uses MessagePack with JSON fallback for efficient network transmission
+- **Message Processing Pipeline**: Streamlined architecture with direct message instance routing
+  - **Eliminated**: Complex wrapper object creation and management overhead
+  - **Simplified**: Transport `receive` method now directly reconstructs message instances from flat data
+  - **Improved**: Cleaner separation between transport concerns and message processing logic
+
 ### Added
 - **Emergency Services Multi-Program Demo**: Complete emergency dispatch simulation system
   - Added comprehensive emergency services message definitions with validation
-  - Emergency Dispatch Center (911) routing calls to appropriate departments 
+  - Emergency Dispatch Center (911) routing calls to appropriate departments
   - Fire Department, Police Department, and Health Department service implementations
   - AI-powered visitor generating realistic emergency scenarios with retry logic
   - Health monitoring system across all city services with status reporting

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    smart_message (0.0.12)
+    smart_message (0.0.13)
       activesupport
       async
       async-redis
@@ -30,7 +30,7 @@ GEM
       tzinfo (~> 2.0, >= 2.0.5)
       uri (>= 0.13.1)
     amazing_print (1.8.1)
-    async (2.29.0)
+    async (2.31.0)
       console (~> 1.29)
       fiber-annotation
       io-event (~> 1.11)
@@ -69,12 +69,12 @@ GEM
     i18n (1.14.7)
       concurrent-ruby (~> 1.0)
     io-endpoint (0.15.2)
-    io-event (1.13.0)
+    io-event (1.14.0)
     io-stream (0.10.0)
     json (2.13.2)
     logger (1.7.0)
     lumberjack (1.4.1)
-    metrics (0.14.0)
+    metrics (0.14.1)
     minitest (5.25.5)
     minitest-power_assert (0.3.1)
       minitest
@@ -95,7 +95,7 @@ GEM
     shoulda-matchers (4.5.1)
       activesupport (>= 4.2.0)
     state_machines (0.100.1)
-    traces (0.18.1)
+    traces (0.18.2)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
     uri (1.0.3)

data/docs/core-concepts/architecture.md

@@ -9,10 +9,10 @@ SmartMessage is designed around the principle that **messages should be independ
 ### Core Principles
 
 1. **Separation of Concerns**: Message content, transport, and serialization are independent
-2. **Plugin Architecture**: Pluggable transports and serializers
+2. **Plugin Architecture**: Pluggable transports
 3. **Dual Configuration**: Both class-level and instance-level configuration
 4. **Thread Safety**: Concurrent message processing with thread pools
-5. **Gateway Support**: Messages can flow between different transports/serializers
+5. **Gateway Support**: Messages can flow between different transports
 
 ## Architecture Overview
 
@@ -26,7 +26,7 @@ The foundation class that all messages inherit from, built on `Hashie::Dash`.
 
 **Key Responsibilities:**
 - Property management and validation
-- Plugin configuration (transport, serializer, logger)
+- Plugin configuration (transport, logger)
 - Message lifecycle management
 - Header generation and management
 
@@ -40,7 +40,6 @@ class MyMessage < SmartMessage::Base
   
   config do
     transport MyTransport.new
-    serializer MySerializer.new
   end
 end
 ```
@@ -163,7 +162,6 @@ puts header.from          # "payment-service"
 puts header.to            # "order-service"
 puts header.reply_to      # "payment-service" (defaults to from)
 puts header.version       # 1
-puts header.serializer    # "SmartMessage::Serializer::JSON"
 ```
 
 ## Message Lifecycle
@@ -176,7 +174,6 @@ class OrderMessage < SmartMessage::Base
   
   config do
     transport SmartMessage::Transport.create(:memory)
-    serializer SmartMessage::Serializer::Json.new
   end
 end
 ```
@@ -201,7 +198,7 @@ order = OrderMessage.new(order_id: "123", amount: 99.99)
 order.from("order-service").to("payment-service")
 order.publish
 # 1. Creates header with UUID, timestamp, addressing
-# 2. Encodes message via serializer  
+# 2. Encodes message via transport's serializer  
 # 3. Sends via transport
 # 4. Circuit breaker monitors for failures
 ```
@@ -210,7 +207,7 @@ order.publish
 ```ruby
 # Transport receives serialized message
 transport.receive(message_class, serialized_message)
-# 1. Decodes message using class's configured serializer
+# 1. Decodes message using transport's serializer
 # 2. Routes decoded message to dispatcher
 # 3. Dispatcher checks DDQ for duplicates per handler
 # 4. Applies message filters (from/to/broadcast)
@@ -271,7 +268,6 @@ SmartMessage supports configuration at both class and instance levels:
 class PaymentMessage < SmartMessage::Base
   config do
     transport ProductionTransport.new
-    serializer SecureSerializer.new
   end
 end
 
@@ -459,7 +455,6 @@ Configuration uses method-based DSL:
 ```ruby
 config do
   transport MyTransport.new(option1: value1)
-  serializer MySerializer.new(option2: value2)
   logger MyLogger.new(level: :debug)
 end
 ```

data/docs/getting-started/examples.md

@@ -20,7 +20,6 @@ class NotificationMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:stdout, loopback: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -87,7 +86,6 @@ class UserRegisteredEvent < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -152,7 +150,6 @@ class WelcomeEmailMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:stdout)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -171,7 +168,6 @@ class AnalyticsMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:stdout)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -209,7 +205,6 @@ class OrderCreatedMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -252,7 +247,6 @@ class InventoryReservationMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -289,7 +283,6 @@ class PaymentProcessingMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -362,7 +355,6 @@ class LogMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:stdout, output: "application.log")
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -412,7 +404,6 @@ class MetricMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -496,7 +487,6 @@ class MessageGateway < SmartMessage::Base
   # Receive from one transport
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -621,7 +611,6 @@ class ResilientMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -689,7 +678,6 @@ class DeadLetterMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:stdout, output: "dead_letter_queue.log")
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)

data/docs/getting-started/quick-start.md

@@ -92,7 +92,6 @@ class WelcomeMessage < SmartMessage::Base
   # Configure the transport (where messages go)
   config do
     transport SmartMessage::Transport.create(:stdout, loopback: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   # Define how to process received messages
@@ -213,12 +212,10 @@ transport SmartMessage::Transport.create(:memory, auto_process: true)
 ```
 
 ### Serializers
-Serializers handle message encoding/decoding:
-
-```ruby
-# JSON serialization (built-in)
-serializer SmartMessage::Serializer::Json.new
-```
+Transports handle their own serialization automatically:
+- **MemoryTransport**: No serialization (objects passed directly)
+- **StdoutTransport**: JSON serialization for readability
+- **RedisTransport**: MessagePack (with JSON fallback) for efficiency
 
 ### Message Handlers
 
@@ -321,7 +318,6 @@ class NotificationMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:memory, auto_process: true)
-    serializer SmartMessage::Serializer::Json.new
   end
 
   def self.process(decoded_message)
@@ -364,7 +360,6 @@ class EventMessage < SmartMessage::Base
 
   config do
     transport SmartMessage::Transport.create(:stdout, output: 'events.log')
-    serializer SmartMessage::Serializer::Json.new
   end
 end
 

data/docs/index.md

@@ -31,13 +31,13 @@ Think of SmartMessage as ActiveRecord for messaging - just as ActiveRecord frees
 
 ### Transports
 - [Transport Layer](reference/transports.md)
-- [Redis Queue Transport](transports/redis-queue-transport.md) ⭐ **Featured**
+- [Redis Transport](transports/redis-transport.md)
 - [Redis Transport Comparison](transports/redis-transport-comparison.md)
 
 ### Guides
-- [Redis Queue Getting Started](guides/redis-queue-getting-started.md)
-- [Advanced Routing Patterns](guides/redis-queue-patterns.md)
-- [Production Deployment](guides/redis-queue-production.md)
+- [Examples & Use Cases](getting-started/examples.md)
+- [Architecture Overview](core-concepts/architecture.md)
+- [Transport Configuration](reference/transports.md)
 
 ### Reference
 - [Serializers](reference/serializers.md)