Jenkins 2.0 as deployment pipeline is on hold – still the build pipeline generation is not a first-class-citizen since it is still based on plugins. Authors says that it could be done better. I suppose that it recommendation considers only the pipeline, not the CI itself

Apache Kafka is on trial – although quite widely used in industry. Authors have a pragmtic approach building the report

Languages & Frameworks

Spring Boot to adopt – seems to be obvious choice right now, so those who bet on it few years ago were right (lucky me!)

React.js to adopt – as a JS framework with one-way binding, providing the loose coupling on the front side

Platforms

Docker! Docker! Docker!

Techniques

GitFlow on hold! That’s right. Authors noted that feature branches tend to stand away from master / develop branch for too long. That causes the merge / integration problems. So the point is to use GitFlow wisely. Feature branch and merge request that have 2 days of coding in it are far too big.

It helps to assess if the novelty you’ve recently found is ready to adopt or was not tested enough yet. There you’ll find out that NoSQL are ready to go, however Node.js not really – still it is good for fast prototyping and mocks but not for production.

The report gathers data in a nice visual graphs and explains each item shortly. Here is the graph sample

TechRadar graph

Do you like my blog?
I manage this blog and share my knowledge for free sacrificing my time. If you appreciate it and find this information helpful, please consider making a donation in order to keep this page alive and improve quality