It's almost impossible to keep up with the @SpringBoot and @java ecosystems. Here are five trends I find super exciting: @graalvm: build highly optimized, operating system and architecture-specific native images that run in small fractions of a similar JRE application. Use @SpringBoot 3 AOT to take your applications further than ever #iot #edge #Kubernetes

the proxy design pattern is a super useful one in @Java. The idea behind a proxy is to make it more transparent to work with remote resources. They're all over the place in @Java and enterprise Java, in particular. I'm going to look at some of my favorite examples in this thread

I spent the weekend working on my little side project which I hope will benefit others: it's a much-improved version of the publication pipeline I used to build @ReactiveSpring

bootiful-asciidoctor.github.io the ideal is that you point the pipeline to the Git repo with you @asciidoctor docs, and point it to the Git repos (zero or more) containing code you'd like to include, and it'll clone 'em all, then generate your book.
* screen PDF
* prepress PDF
* ePub
* Mobi
* HTML

Cryptography takes time on the CPU. It’s one of those things that blocks threads in a reactive application. You need to move that into an isolated thread pool (a Scheduler, in @ProjectReactor). 1/N Token-based security schemes like OAuth help here because they reduce the frequency of cryptography. You only need to do encryption when you exchange long term credentials (username, password) for short term credentials (token). 2/n

I love reactive programming. Reactive libraries offer me several tentpole benefits

1. Consistency
2. Smarter, safer concurrency
3. Robustness
4. Resource efficiency

I’ll expand on those points here: 1. : one API no matter what the application (SSE, WS, HTTP, Kafka, whatever) etc are all easily represented as Reactive Stream types. This greatly simplifies integration and composition of disparate services and data

I love the new @SpringBoot 2.3 release. It's hard to pick any single thing or theme, but I love the features that make my software even more relevant on @kubernetesio and in the cloud.

Here's a list of some of the features I love... Easy @Docker image generation with @buildpacks_io

docs.spring.io/spring-boot/do…

one of the frustrating things about public IaaS like AWS and evergreen SaaS (even on-prem) like @pivotalcf is that you can't constrain the 'version' of the dependency. that is, AWS is going to evolve and it MIGHT break assumptions into your code from yesteryear. 1/N This is fine when there's a robust CI/CD practice to continuously (daily, at worst?) confirm that things haven't broken and an on-call team able to respond to such changes. It gets complicated when you want to ramp down the team and reprioritize their efforts 2/N

the new @SpringCloud release is jam-packed with good stuff and represents a major milestone in the journey to reactive microservices.

spring.io/blog/2018/06/1… We released Spring @springframework 5 in September 2017. This was the first release to introduce new Reactive programming support to help build more robust, scalable services. It builds upon the @Pivotal @ProjectReactor project, our reactive streams compatible reactive runtime.