The Spring Blog
I’m pleased to announce the releases of Spring Security OAuth 2.3.7, 2.2.6, 2.1.6 and 2.0.19. These maintenance releases primarily deliver bug fixes and minor enhancements.
For a complete list of changes, please refer to:
In the previous post, I tried to provide justification for our shift to a functional programming model in Spring Cloud Stream (SCSt). It’s less code, less configuration. Most importantly, though, your code is completely decoupled and independent from the internals of SCSt.
In this post, I’ll dig a little deeper and summarize the core features of our functional support, specifically around its reactive features.
IMPORTANT: Anything you can do with
@StreamListener/@EnableBindingyou can also do without it. In other words, the functional support is now feature-compatible with the annotation-based support.
On behalf of the Spring Boot team and everyone that has contributed, I am delighted to announce that Spring Boot 2.2.0 has been released and is available now from repo.spring.io, Maven Central and Bintray. This release adds a significant number of new features and improvements. For full upgrade instructions and new and noteworthy features please see the release notes.
Spring Boot 2.2 moves to new versions of several Spring projects:
- Spring AMQP 2.2
- Spring Batch 4.2
- Spring Data Moore
- Spring Framework 5.2
- Spring HATEOAS 1.0
- Spring Integration 5.2
- Spring Kafka 2.3
- Spring Security 5.2
- Spring Session Corn
Event driven architecture is great. But without a framework, writing the scaffolding required to work with popular event messaging platforms can be messy. In this post we’ll take a look at how Spring Cloud Stream can be used to simplify your code.
You just want to write logic for your event driven application, but the boilerplate messaging code can get in the way. Connecting your apps to messaging services is tricky, and if you’re an enterprise developer, you probably need to work with multiple messaging technologies (either on-premises or in the cloud).
Hi, Spring fans! WHEW! What a week! Last week was the insane SpringOne Platform 2019 event, from which I am still recovering! Then I flew home, hosted Spring team member and Micrometer lead and friend Tommy Ludwig in San Francisco, and prepared to fly out for meetings and user group appearances on Monday (in Stuttgart, Germany) and Tuesday (in Amsterdam).
I prepared, and got into the Uber going to San Francisco airport when I got a call from my brother saying my 81-year-old dad wasn’t doing well (thanks to everyone for the well-wishes!) and was rushed to the hospital. I had to, regretfully, cancel my live appearances in those countries. I am SO sorry for those I disappointed. I was very happy to be able to do a few of those meetings remotely. Thanks to everyone who indulged me and supported me as I flew to Los Angeles to be with my father.
Recently, I had a discussion with a user and heard something that prompted me to begin a series of blog posts (starting with this one) with the goal of both demystifying the true goals of Spring Cloud Stream and Spring Cloud Function projects as well as demonstrating their new features.
The specific phrase that prompted all this was - "Spring Cloud Stream, being a light Spring Integration input/output router…”. That’s an interesting perception, but I have to disagree. While it may have been inspired by Enterprise Integration Patterns (EIP) and builds on top of Spring Integration (SI), that last part is really just an implementation detail. Spring Cloud Stream (SCSt) as a framework was never about “being a light Spring Integration input/output router”. In fact, this statement shows part of the problem, where SI (the framework of choice to support some of the internal requirements of SCSt) was somehow perceived to be the core of SCSt in such way that many perceive SCSt to be an extension or a wrapper to SI. It is not. It has always been about pure microservices and binding them to sources and targets of data (i.e., messaging systems) . Simple as that.
If you abstract yourself far enough from knowing the internals of SCSt, you quickly realize that it is really a binding and activation framework. It binds a piece of code (provided by the user) to source/target of data exposed by the binder and activates such code according to binder implementation (for example, message arrival and so on). That is pretty much it.
On behalf of the team and everyone who has contributed, I’m happy to announce that Spring Initializr 0.8.0 has been released and is now available from repo.spring.io. For the first time, the release is also available from Maven Central!
This release includes 90 fixes, improvements and dependency upgrades. Thanks to all those who have contributed with issue reports and pull requests.
Spring Initializr 0.8 brings a complete rewrite of the project generation API with dedicated abstractions for common assets of JVM-based projects:
Hi, Spring fans! In this SpringOne Platform 2019 episode, Josh Long (@starbuxman) interviews Spring mad scientist Andy Clement (@andy_clement) on AspectJ, SpEL, Eclipse, the new Graal native image feature, being an Iron-Man triathlete, and more.
It’s here it’s finally here! My favorite time of the year! Happy SpringOne Platform week! This week I’m in amazing Austin, TX talking to anybody who wants to about all things Spring. There have been a ton of amazing things announced at this show but one thing I’ve been excited to share with y’all is that we just announced the new Azure Spring Cloud runtime. (More on that in the links below)
I’ve been busy! I’m doing one talk with Microsoft on Azure Spring Cloud, and another with Okta / Google on simplifying the dev lifecycle. Also, I’m hosting the keynote tomorrow morning. So much to do, so little time!