[ISSUE #5249]Refactor/unified runtime pipeline and protocol processors#5250
Open
qqeasonchen wants to merge 8 commits intoapache:masterfrom
Open
[ISSUE #5249]Refactor/unified runtime pipeline and protocol processors#5250qqeasonchen wants to merge 8 commits intoapache:masterfrom
qqeasonchen wants to merge 8 commits intoapache:masterfrom
Conversation
…ugin configuration
… EgressProcessor - Introduced IngressProcessor (Filter -> Transformer -> Router) and EgressProcessor (Filter -> Transformer) to centralize pipeline logic. - Refactored ClientGroupWrapper (TCP SDK) to use these processors. - Refactored EventMeshConnectorBootstrap (Connectors) to use these processors. - Updated SinkWorker to support embedded mode for unified runtime execution. - Updated Unified Runtime Design documentation to reflect architectural clarity.
…ine architecture
This commit completes the migration of all HTTP and gRPC protocol processors to use
the unified IngressProcessor and EgressProcessor pipeline architecture, ensuring
consistent Filter-Transformer-Router processing across all protocols.
Changes:
- HTTP Processors (5): Migrated SendAsyncMessageProcessor, SendSyncMessageProcessor,
BatchSendMessageProcessor, BatchSendMessageV2Processor, and refactored
SendAsyncEventProcessor to use IngressProcessor
- gRPC Processors (3): Migrated PublishCloudEventsProcessor,
BatchPublishCloudEventProcessor, and RequestCloudEventProcessor with bidirectional
pipeline support (Ingress for requests, Egress for responses)
- Added BatchProcessResult utility class to track success/filtered/failed counts for
batch processing with detailed statistics
- Added comprehensive unit tests: IngressProcessorTest, EgressProcessorTest,
BatchProcessResultTest, and enhanced SendAsyncEventProcessorTest
- Added IngressProcessor and EgressProcessor getters to EventMeshServer and
EventMeshGrpcServer for cross-module access
- Updated design documentation (unified-runtime-design.md) to reflect the new
architecture and migration status
- Updated configuration guide (core-engines-configuration.md) with pipeline key format
Architecture improvements:
- Unified pipeline key format: {producerGroup}-{topic}
- Consistent filter behavior: filtered messages return SUCCESS status
(except request-reply returns error)
- Router support: topic changes tracked with finalTopic variable
- Batch statistics: detailed success/filtered/failed counts with message IDs
- Bidirectional processing: RequestCloudEventProcessor applies Ingress to requests
and Egress to responses
All tests pass with no regressions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
#5249 This PR consolidates EventMesh's fragmented runtime architecture into a single unified runtime with standardized processing pipelines.
Commit 1: Unify Connector, Function, and Core Runtime into eventmesh-runtime
eventmesh-runtime-v2module entirely (33 files, ~1700 lines deleted), including its separate runtime lifecycle, connector/function managers, health/monitor/status services, meta storage, and configurationRouter,RouterBuilder,ConnectorEventPublisher,SourceWorker) intoeventmesh-runtimeandeventmesh-functionmodulesRouterEngine,FilterEngine,TransformerEngineas core processing engines ineventmesh-runtimeEventMeshConnectorBootstrapto manage connector lifecycle within the unified runtimeEventMeshServerto integrate engines and A2A service initializationClientGroupWrapper(TCP) to delegate to the new enginesCommit 2: Unified Ingress/Egress Pipelines
IngressProcessor— a centralized pipeline implementing Filter -> Transformer -> Router for incoming messagesEgressProcessor— a centralized pipeline implementing Filter -> Transformer for outgoing messagesClientGroupWrapper(TCP SDK) to useIngressProcessorandEgressProcessorEventMeshConnectorBootstrap(Connectors) to use the new processorsSinkWorkerto support embedded mode for unified runtime executionCommit 3: Complete HTTP and gRPC Processor Migration
SendAsyncMessageProcessor,SendSyncMessageProcessor,BatchSendMessageProcessor,BatchSendMessageV2Processor, andSendAsyncEventProcessorto useIngressProcessorPublishCloudEventsProcessor,BatchPublishCloudEventProcessor, andRequestCloudEventProcessorwith bidirectional pipeline supportBatchProcessResult— utility class for tracking success/filtered/failed countsIngressProcessorTest,EgressProcessorTest,BatchProcessResultTestKey Changes
eventmesh-runtime-v2/(entire module)eventmesh-runtime/.../core/protocol/IngressProcessor.javaeventmesh-runtime/.../core/protocol/EgressProcessor.javaeventmesh-runtime/.../core/protocol/BatchProcessResult.javaeventmesh-runtime/.../boot/RouterEngine.javaeventmesh-runtime/.../boot/EventMeshConnectorBootstrap.javaTest Plan
./gradlew :eventmesh-runtime:testpasses