System and method for processing messages in a service-oriented pipeline architecture

Abstract

A computer-implemented system and method for processing messages using a common interface platform supporting multiple pluggable data formats in a service-oriented pipeline architecture is disclosed. The method in an example embodiment includes deserializing or serializing a request/response message using a pluggable serializer/deserializer mechanism and a corresponding pluggable data format parser. An example embodiment uses a common model for serialization/deserialization regardless of the data format, resulting in a consistent and efficient mechanism.

1 . A method comprising:
 receiving a request, through a single API interface supporting multiple different data formats, to serialize or deserialize a message, the message having a specific data format representing one of the multiple different data formats;   selecting one of a plurality of pluggable formatters corresponding to the specific data format of the message; and   initiating, by a hardware processor, the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format of the message into a desired java object.   
     
     
         2 . The method of  claim 1 , wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message further comprises:
 serializing or deserializing the message in the specific data format of the request received.   
     
     
         3 . The method of  claim 1 , wherein receiving the request, through the single API interface supporting multiple different data formats, to serialize or deserialize the message further comprises:
 receiving the request to serialize or deserialize the message from one of a plurality of handlers from a pipeline in a service-oriented pipeline architecture.   
     
     
         4 . The method of  claim 3 , wherein receiving the request to serialize or deserialize the message from one of the plurality of handlers from the pipeline in the service-oriented pipeline architecture further comprises:
 invoking the request to serialize or deserialize the message by the one of the plurality of handlers.   
     
     
         5 . The method of  claim 1 , wherein receiving the request, through the single API interface supporting multiple different data formats, to serialize or deserialize the message further comprises:
 receiving the request to serialize or deserialize the message after a protocol-agnostic portion of the message is processed from a pipeline in a service-oriented pipeline architecture.   
     
     
         6 . The method of  claim 5 , wherein receiving the request after the protocol-agnostic portion of the message is processed from the pipeline in the service-oriented pipeline architecture further comprises:
 receiving the request to serialize or deserialize the message from a dispatcher in the service-oriented pipeline architecture.   
     
     
         7 . The method of  claim 1 , wherein the single API interface represents a common interface supporting the multiple different data formats during runtime with the plurality of pluggable formatters. 
     
     
         8 . The method of  claim 1 , wherein selecting one of the plurality of pluggable formatters corresponding to the specific data format of the message further comprises: selecting one of a plurality of pluggable serializers or deserializers corresponding to the specific data format of the message. 
     
     
         9 . The method of  claim 1 , wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format into the desired java objects further comprises:
 invoking, by the selected one of the plurality of pluggable serializers and deserializers, one of a plurality of data parsers corresponding to the specific data format of the message.   
     
     
         10 . The method of  claim 1 , wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format into the desired java objects further comprises:
 calling a server message processor to access serialization parameters; and   triggering serialization of an outgoing response message.   
     
     
         11 . The method of  claim 1 , wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format into the desired java objects further comprises:
 calling a client message processor to access serialization parameters; and   triggering serialization of an outgoing request message.   
     
     
         12 . The method of  claim 1 , wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format into the desired java objects further comprises:
 calling a server message processor to access deserialization parameters; and   triggering deserialization of an incoming request message.   
     
     
         13 . The method of  claim 1  wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format into the desired java objects further comprises:
 calling a client message processor to access deserialization parameters; and 
 triggering deserialization of an incoming response message. 
 
     
     
         14 . The method of  claim 3 , wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format into the desired java objects further comprises:
 triggering serialization or deserialization by calling a message processor in the pipeline in the service-oriented pipeline architecture by the one of the plurality of handlers from the pipeline in the service-oriented pipeline architecture.   
     
     
         15 . The method of  claim 6 , wherein initiating the selected one of the plurality of pluggable formatters to service the request and to convert the specific data format into the desired java objects further comprises:
 triggering serialization or deserialization by calling a message processor in the pipeline in the service-oriented pipeline architecture by the dispatcher in the service-oriented pipeline architecture.   
     
     
         16 . The method of  claim 1 , wherein receiving the request, through the single API interface supporting multiple different data formats, to serialize or deserialize the message further comprises:
 receiving the message representing a request for a service from a service consumer.   
     
     
         17 . The method of  claim 1 ,
 wherein selecting one of the plurality of pluggable formatters corresponding to the specific data format of the message comprising:
 obtaining, by a serialization/deserialization processor, the one of the plurality of pluggable formatters corresponding to the specific data format of the message from a serialization/deserialization factory; 
   wherein initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format of the message into the desired java object further comprising:
 serialization or deserialization of the message; 
 storing the serialized or deserialized message in a cache memory in the serialization/deserialization processor; and 
 providing a pointer to the cache memory indicating a location of the stored serialized or deserialized message in response to the request to serialize or deserialize the message. 
   
     
     
         18 . A machine readable medium not having transitory signals and storing instructions that, when executed by at least one processor of a machine, cause the machine to perform operations comprising:
 receiving a request, through a single API interface supporting multiple different data formats, to serialize or deserialize a message, the message having a specific data format representing one of the multiple different data formats;   selecting one of a plurality of pluggable formatters corresponding to the specific data format of the message; and   initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message and to convert the specific data format of the message into a desired java object.   
     
     
         19 . The machine readable medium of  claim 18 , wherein the initiating the selected one of the plurality of pluggable formatters to service the request to serialize or deserialize the message further comprises:
 serializing or deserializing the message in the specific data format of the request received.   
     
     
         20 . A system comprising:
 an single interface to receive a request to serialize or deserialize a message, the single interface supporting multiple different data formats, the message having a specific data format representing one of the multiple different data formats;   a message processor to select one of a plurality of pluggable formatters corresponding to the specific data format of the message; and   a message processing pipeline to initiate the selected one of the plurality of pluggable formatters to service the request to natively serialize or natively deserialize the message and to convert the specific data format of the message into a desired java object.