From d7639649c5b67d44763fb0ab938a94c6d737edf2 Mon Sep 17 00:00:00 2001 From: "Roland Edwards, AOE GmbH" <39269273+raedwards@users.noreply.github.com> Date: Wed, 23 May 2018 09:22:02 +0200 Subject: [PATCH] Update protobuf.md --- radar/2017-03-01/protobuf.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/radar/2017-03-01/protobuf.md b/radar/2017-03-01/protobuf.md index d95db18..b151263 100644 --- a/radar/2017-03-01/protobuf.md +++ b/radar/2017-03-01/protobuf.md @@ -7,8 +7,8 @@ quadrant: languages-and-frameworks In an increasingly microservice-oriented environment, it is crucial that all parties agree on a common language and wire format for data exchange. -JSON and XML are two very well-known formats for serialization of data, however they come with a few drawbacks. JSON is completely dynamic without any validation (though there is json-schema) and XML uses an extremely heavyweight syntax, which carries a huge overhead, so parsing and transport becomes quite slow. +JSON and XML are two well-known formats for serialization of data; however, they come with a few drawbacks. JSON is completely dynamic without any validation (though there is json-schema) and XML uses an extremely heavyweight syntax, which carries a huge overhead, so parsing and transport becomes quite slow. -Protobuf, amongst others, is an approach to solving this problem by using well-defined schemas to create language-specific code, which serializes/marshals and deserializes/unmarshals data. One of the key features is the built-in support for evolving schemas, it is easily possible to incrementally extend the definition while staying backwards-compatible and compose messages out of several sub-messages. +Protobuf, amongst others, is an approach to solving this problem by using well-defined schemas to create language-specific code, which serializes/marshals and deserializes/unmarshals data. One of the key features is the built-in support for evolving schemas; it is easily possible to incrementally extend the definition while staying backwards-compatible and compose messages consisting of several sub-messages. -If you are looking for a way to have different systems agree on a common protocol on top of a transport layer (such as AMQP or HTTP), Protobuf is definitely worth taking a look at and should be assessed. +If you are looking for a way to have different systems agree on a common protocol on top of a transport layer (such as AMQP or HTTP), Protobuf is definitely worth examining more closely and should be assessed.