java-weekly-232
Java Weekly, Issue 232
Here we go…
1. Spring and Java
===== >> Truth First, or Why You Should Mostly Implement Database First Designs [blog.jooq.org]
Some solid points to consider when thinking about where the source of truth in your system is, and how to make sure your architecture reflects that.
>> Java Collections Are Evolving [dzone.com]
The highly useful new functionality the last couple of JDK releases have brought to the Java Collection Framework. Really good stuff.
>> Zip Slip Directory Traversal Vulnerability Impacts Multiple Java Projects [infoq.com]
A quick but interesting write-up, all about the new “Zip Slip” vulnerability – along with a few practical examples, if you’re curious.
Also worth reading:
-
===== >> The rise of Java Microframeworks [e4developer.com]
-
===== >> Write BDD Unit Tests with BDDMockito and AssertJ [thepracticaldeveloper.com]
-
===== >> JEP 181, JEP 315, and JEP 333 Proposed to Target JDK 11 [marxsoftware.blogspot.com]
-
===== >> The best way to write a Hibernate ORM issue test case [in.relation.to]
-
===== >> WireMock Tutorial: Request Matching, Part One [petrikainulainen.net]
-
===== >> How to improve statement caching efficiency with IN clause parameter padding [vladmihalcea.com]
-
===== >> Webapps desktop integration [blog.frankel.ch]
Webinars and presentations:
-
===== >> Simplifying Apache Geode with Spring Data [infoq.com]
-
===== >> Spring Driven Industrial IoT Utilizing Edge, Fog, and Cloud Computing [infoq.com]
-
===== >> Spring Tips: JPA [spring.io]
-
===== >> The Spring IO 2018 Playlist [youtube.com]
Time to upgrade:
-
===== >> WildFly 13 released, featuring all latest Hibernate versions! [in.relation.to]
-
===== >> Joda-Time assertions 2.1.0 release [joel-costigliola.github.io]
-
===== >> Gradle Releases Version 4.7 with Support for Java 10 [infoq.com] and >> Gradle 4.8 Release Notes [docs.gradle.org]
*2. Technical* and Musings
===== >> Storing Encrypted Credentials in GIT [techblog.bozho.net]
Storing credentials correctly isn’t necessarily easy, but it’s highly important that you understand how to do that well.
>> “Should that be a Microservice?” Part 4: Independent Scalability [content.pivotal.io]
Microservices can be a useful architectural choice… but don’t always. Better think twice.
Also worth reading:
-
===== >> Karate framework: REST API testing made easy! [aboullaite.me]
-
===== >> Software Jobs for Social Anxiety Sufferers [daedtech.com]
-
===== >> How to Measure the Reliability of Your Software Throughout the CI/CD Workflow [blog.takipi.com]
-
===== >> When to use Let’s Encrypt’s webroot and standalone authorization [advancedweb.hu]
-
===== >> shell-scripting-recipes [alexecollins.com]
-
===== >> Hack the Box Writeup – Crimestoppers [codemonkeyism.co.uk]
-
===== >> On choosing both/and, not either/or [ontestautomation.com]
3. Comics
>> Motivational Speaker [dilbert.com]
>> Decentralization Changes Everything [dilbert.com]
>> Boiling an Ocean [dilbert.com]
4. Pick of the Week
===== >> Why the best things in life are all backwards [markmanson.net]
