Java Weekly, Issue 283

Here we go…

1. Spring and Java

>> Feature toggles in a microservice environment – Part 2: Implementation [blog.codecentric.de]

A quick look at Unleash, a Node.js service for managing feature toggles across a collection of microservices, with a simple Java-based configuration example.

>> MBD-to-MDB Messaging: Harness the Power of the River Delta [tomitribe.com]

A good write-up showing how messaging between Message-Driven Beans can lead to powerful, asynchronous architectures.

>> A boost for Java on the Client [gluonhq.com]

And Gluon announces their client plugin for Maven and Gradle, which will compile a Java app and its dependencies to native code.

Also worth reading:

• >> 5 Minutes or Less: Message-Driven Beans with ActiveMQ and TomEE [tomitribe.com]

• >> Writing Web Applications in Java – a Study of Alternatives [infoq.com]

• >> Consumer-Driven Contracts with Spring Cloud Contract [rieckpil.de]

• >> Reactive Relational Database Transactions [paluch.biz]

Webinars and presentations:

• >> A Bootiful Podcast: Twitter's Chris Thalinger on Java, Graal, JVMs, JITs, and more [spring.io]

• >> Spring Tips: Debugging Reactor Applications [spring.io]

• >> Video course — Effective keyboard usage for developers [blog.sebastian-daschner.com]

• >> Life of a Distributed Graph Database Query [infoq.com]

• >> Massive Scale Anomaly Detection Framework [infoq.com]

• >> Quality Engineering in DevOps [infoq.com]

• >> The Future of Transportation [infoq.com]

Time to upgrade:

• >> Spring Tools 4.2.2 released [spring.io]

• >> CVE-2019-11269: Spring Security OAuth 2.3.6, 2.2.5, 2.1.5, 2.0.18 Released [spring.io]

• >> Spring Cloud Open Service Broker 3.0.1 Released [spring.io]

• >> Spring Cloud Edgware.SR6 Released [spring.io]

2. Technical and Musings

>> Using Intel Analytics Zoo to Inject AI into Customer Service Platform (Part II) [infoq.com]

An exercise in developing a Question Answering (QA) solution using Analytics Zoo on Azure's Big Data platform.

>> Why AWS access and secret keys should not be in the codebase [advancedweb.hu]

And a few good reasons why secret keys should come from environment variables and should never be hard-coded.

Also worth reading:

• >> Microsoft Launches Several New Machine Learning Services and Extends Its Cognitive Services [infoq.com]

• >> Exercises in Programming Style, Kwisatz Haderach-style [blog.frankel.ch]

• >> Being an Ethical Software Engineer [infoq.com]

• >> Checking your clean architecture [sourced-bvba.be]

3. Comics

And my favorite Dilberts of the week:

>> If You Can Dream [dilbert.com]

>> Wally and His Priorities [dilbert.com]

>> Counting Morons [dilbert.com]

4. Pick of the Week

Last week, I wrote about Codota – a really interesting coding assistant I found and have been using.

The response to the video was overwhelmingly positive, which is always super cool to see.

Here's Codota directly, in case you missed it. My suggestion is to simply install it and have it running in the background, as you're coding normally:

>> Codota – an AI Assistant that Actually Works [codota.com]

res – REST with Spring (eBook) (everywhere)

Learning to build your API
with Spring?

Download the E-book