GemFire’s Portable Data eXchange (PDX) is a cross-language data format that can reduce the cost of distributing and serializing your objects.
GemFire .NET Framework PDX serialization:
Is interoperable with other languages by GemFire – no need to program a Java-side implementation
Reduces deserialization overhead by providing direct field access on servers of serialized data, without full deserialization. Stores data in named fields that you can access individually, to avoid the cost of deserializing the entire data object
The simplest option is to use automatic serialization by registering the GemFire .NET Framework PDX reflection-based autoserializer in your application. When you have an autoserializer, GemFire uses it for all domain objects that are not separately treated under the IPDXSerializable interface.
For greater control, you can specify individual treatment for domain objects using the
IPdxSerializable interface. Objects derived from the
IPdxSerializable interface are not subject to autoserialization.
When you create an
IPdxSerializable object, GemFire stores the object’s type information in a central registry. The information is passed between peers, between clients and servers, and between distributed systems.
This offers a notable advantage to the .NET Framework client, which shares data with Java cache servers. When using PDX serialization, clients automatically pass registry information to servers when they store an
IPdxSerializable object. Clients can run queries and functions against the data in the servers without the servers needing to know anything about the stored objects. One client can store data on the server to be retrieved by another client, with the server never needing to know the object type. This means you can code your .NET Framework clients to manage data using Java servers without having to create Java implementations of your .NET Framework domain objects.
The access methods for
IPdxSerializable objects allow you to examine specific fields of your domain object without deserializing the entire object. This can reduce deserialization costs significantly. Client .NET Framework apps can run queries and execute functions against the objects in the server caches without deserializing the entire object on the server side. The query engine automatically recognizes PDX objects and uses only the fields it needs.
Clients can execute Java functions on server data that only access parts of the domain objects by using
Likewise, peers can access just the fields needed from the serialized object, keeping the object stored in the cache in serialized form.
You can use GemFire delta propagation with PDX serialization.
See the following sections for details on implementing PDX serialization and autoserialization: