Protocol buffers are a language-neutral, platform-neutral extensible mechanism for serializing structured data. You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages. 

Protocol Buffers - Google's data interchange format

In gRPC a client application can directly call methods on a server application on a different machine as if it was a local object, making it easier for you to create distributed applications and services. As in many RPC systems, gRPC is based around the idea of defining a service, specifying the methods that can be called remotely with their parameters and return types. 

gRPC-Java - The Java gRPC implementation. HTTP/2 based RPC

Schemas describe and document data models. If you have data, you should have a schema. Google's Protocol Buffers are built around a great schema language. It's cross platform and language independent. Whatever programming language you use, you'll be able to use proto schemas with your application. Proto schemas are backwards-compatible and future-proof. You can evolve your schema as your application loses old features and gains new ones.
 
Why Wire? 
The Protocol Buffers schema language and binary encoding are both defined by Google. Wire is an independent implementation from Square that's specifically designed for Android and Java. For each message type defined in the schema, Wire generates an immutable model class and its builder. The generated code looks like code you'd write by hand: it's documented, formatted, and simple. Wire's APIs should feel at home to programmers who like Effective Java.

Schemas describe and document data models. If you have data, you should have a schema. Google's Protocol Buffers are built around a great schema language. It's cross platform and language independent. Whatever programming language you use, you'll be able to use proto schemas with your application. Proto schemas are backwards-compatible and future-proof. You can evolve your schema as your application loses old features and gains new ones.

Wire - Clean, lightweight protocol buffers for Android and Java.

Protocol buffers  (a.k.a., protobuf)  are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages. 

protobuf-net is a contract based serializer for .NET code, that happens to write data in the "protocol buffers" serialization format engineered by Google. The API, however, is very different to Google's, and follows typical .NET patterns (it is broadly comparable, in usage, to XmlSerializer, DataContractSerializer, etc). It should work for most .NET languages that write standard types and can use attributes. 

Protobuf-net - Fast, portable, binary serialization for .NET

Discover open source projects across all platforms

Projects

Protocol Buffers - Google's data interchange format

gRPC-Java - The Java gRPC implementation. HTTP/2 based RPC

Wire - Clean, lightweight protocol buffers for Android and Java.

Protocol Buffers - Google's data interchange format

Protobuf-net - Fast, portable, binary serialization for .NET

TechStack

Tagcloud

License

Suggested keywords:

Projects

Protocol Buffers - Google's data interchange format

gRPC-Java - The Java gRPC implementation. HTTP/2 based RPC

Wire - Clean, lightweight protocol buffers for Android and Java.

Protocol Buffers - Google's data interchange format

Protobuf-net - Fast, portable, binary serialization for .NET

TechStack

Tagcloud

License