AJR/TechRadarAJR
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/pr/16' into next

Browse Source 
# Conflicts:
#	radar/2017-10-01/adr.md
#	radar/2017-10-01/angular.md
#	radar/2017-10-01/asciidoc.md
#	radar/2017-10-01/axure.md
#	radar/2017-10-01/babel.md
#	radar/2017-10-01/blameless-post-mortems.md
#	radar/2017-10-01/crc.md
#	radar/2017-10-01/elasticsearch.md
#	radar/2017-10-01/gitlab-ci.md
#	radar/2017-10-01/gitlab.md
#	radar/2017-10-01/go-lang.md
#	radar/2017-10-01/grpc.md
#	radar/2017-10-01/keycloak.md
#	radar/2017-10-01/kubernetes.md
#	radar/2017-10-01/micro-frontends.md
#	radar/2017-10-01/microservices.md
#	radar/2017-10-01/pipeline-as-code.md
#	radar/2017-10-01/ports-and-adapters.md
#	radar/2017-10-01/react.md
#	radar/2017-10-01/reactive-programming.md
#	radar/2017-10-01/scala-lang.md
#	radar/2017-10-01/self-service-infrastructure.md
#	radar/2017-10-01/sonarqube.md
#	radar/2017-10-01/spring-boot.md
#	radar/2017-10-01/svn.md
#	radar/2017-10-01/webpack.md
#	radar/2017-10-01/yarn.md
This commit is contained in:
Bernhard Behrendt
2018-05-23 10:04:37 +02:00
parent 58984efdc3 a2dff28301
commit f3836fa7f9
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
radar/2017-03-01/protobuf.md
View File

@@ -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.

2
radar/2017-03-01/typescript.md
View File

@@ -13,7 +13,7 @@ JavaScript scoping, which led into recurring workarounds such as **var self = th
In TypeScript **this** stays **this**, which leads to more readable and understandable code from an OOP perspective.
TypeScript continues to be actively developed by Microsoft and is also well-Integrated in today's IDEs.
TypeScript continues to be actively developed by Microsoft and is well-Integrated in today's IDEs.
The excellent structure and the possibilities for extension make it a good choice to consider for larger JavaScript projects.