Hi Spring fans! It’s been quite a crazy week! I was in Spring I/O last week in Barcelona, Spain and there was a deluge of interesting news to come out of the show! I loved the show - a sort of mini SpringOne - and am chomping at the bit to see what comes next. I’m now beginning a small tour starting in Zurich, Switzerland; then I’m off to the paradise-like Paris, France for the epic SpringOne Tour event there, then I’m off to Minsk, Belarus; then off to Barcelona, Spain for JBCN, and then - finally - home for the middle school graduation of my kid at the end of the month. So much exciting stuff culminating in an even more exciting event, I can hardly stand it!
The Spring Blog
Josh Long often says that “production is the best place on the Internet.” But where I used to work, developers needed to negotiate with operations, networks, and security before their code could go anywhere near this promised land.
Understandably, each of these disciplines seemed to have the same hidden agenda: change is bad. Experience had taught us that change was difficult and error-prone, so as a company we’d become risk-averse and cautious about our deployments. Releases were infrequent and large. There was plenty that could go wrong.
HI Spring fans! In this installment Josh Long (@starbuxman) talks to Nicolas Frankel (@nicolas_frankel) about integration testing, blogging, Kotlin, application security, living on the French/Swiss border, blogging consistently, and much more. It’s an interview with one of my favorite voices in the community.
Back in 2016, our reactive journey started with Spring Framework 5 accompanied by a couple of reactive integrations. Throughout our journey, other projects joined the reactive movement. With R2DBC, we now also provide a reactive integration for SQL databases. With the growth of transaction-capable integrations, we constantly got asked:
At the time our journey began, we had no reactive form of transactional integrations, so this question was simple to answer: There’s no need for reactive transaction management.
The 4th Generation of Reactor is arriving. On behalf of the team we want to thank all our community for the tremendous feedback. Over the last year we have grown our reactive line-up significantly including R2DBC and BlockHound. Our adoption in the java ecosystem looks phenomenal and we are collaborating with major corps including Microsoft and Google. We have more than doubled our regular Gitter audience with some awesome -you guessed it- reactive discussions happening every day. Finally, Sergei Egorov has joined the core team and we have no plans to stop expanding!
The 8th Service Release for Californium is out. Beyond fixing its share of issues, it is shipping with a turbo-charged
reactor-netty -thanks to changes backported- from our new Dysprosium-M1 release.
The release is available on your preferred maven central repository.
Note that the release overrides
Californium-SR7 which has shipped with an unwelcome regression in
Anticipating the coming
Dysprosium-RELEASE, our reactor-core 3.1.x and reactor-netty 0.7.x lines will not receive further patches. We encourage our users to update to
Californium releases trains, which match Spring Boot 2.1.x and Spring Framework 5.1.x.
On behalf of the community and everyone who contributed, I’m delighted to announce the availability of the second milestone of Spring Data R2DBC 1.0. It is based on the recently released Moore M4 release and R2DBC 0.8.0.M8 release. Please note that Spring Data R2DBC is released outside of the Moore release train and it will be part of the next release train Neumann.
Spring Data R2DBC ships with 32 tickets fixed. The most notable features are:
- Support for MySQL by using jasync-sql.
- Reactive transaction manager.
- Fluent API for
- Coroutine extensions.
- Support for custom conversions.
- Named parameters that are translated to native bind markers by using
- Support for single-column projections for simple types.
- Refactored package structure.
On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Boot 2.1.5 has been released and is now available from repo.spring.io and Maven Central.
This is a maintenance release that includes a number of important dependency updates and bug fixes.
A gentle reminder that Spring Boot 1.5 will be end of life in august, so all users should now be upgrading to Spring Boot 2.1.
If you’re interested in helping out, check out the “ideal for contribution” tag in the issue repository. If you have general questions, please ask on stackoverflow.com using the
spring-boot tag or chat with the community on Gitter.
On behalf of the team and everyone that contributed, I am pleased to announce that the third milestone of Spring Boot 2.2 has been released and is available from our milestone repository. This release closes over 100 issues and pull requests.
If you want to get started with 2.2 and try out the new features, you can bootstrap a new project on https://start.spring.io.
Hi Spring fans! Welcome to another installment of Spring Tips (@SpringTipsLive)! In this installment we look at the just-landed community contribution in Spring Batch adding support for Apache Kafka. This new support offers some tantalizing opportunities to bridge batch and streaming workloads. Stage large writes to backend warehouses with Kafka and drain the stream with Spring Batch. Load large amounts of data from existing datastores and funnel it into stream processing pipelines. And the possibilities become even more interesting when you consider Spring Integration, Spring Cloud Stream, Spring Cloud Stream Kafka Streams, and Spring Cloud Data Flow. If you want a quick primer on Spring Batch-basics you might like this Spring Tip installment on Spring Batch from - gasp! - two years ago!