Hi Spring fans! In this installment Josh Long (@starbuxman) looks at the just-announced support for reactive transactions, now supported in both R2DBC and Spring Data MongoDB.

speaker: Josh Long twitter: @starbuxman

The Spring Cloud Data Flow team is pleased to announce the release of 2.1 of Data Flow.

We have a brand new website with great new content, which is where you can find our getting started guide for use on Cloud Foundry and Kubernetes and your Local Machine.

Here are the highlights:

New Dedicated Data Flow Website

The Data Flow team takes pride is openly communicating with the community in various forums including StackOverflow, Gitter, GitHub, Twitter, and at times in Email and Zoom calls even.

However, we realized that we could provide a much better experience to answer common questions and provide an easier on-ramp to using Data Flow if we focused on improving the online documentation. The reference guide was not the ideal format to achieve that goal, so we embarked on creating a new website - https://dataflow.spring.io…

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.

In spite of this, every six months or so developers would bundle up their code changes into a release, write the release notes, create a rollback plan, and wait around until midnight on a Saturday to deploy it. The deployment would be done manually, and not by developers, but by someone in operations. Developers were strictly passengers on this particular release-train (after all, we’re “the people who write all the bugs” as my friend Coté…

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…

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.

• Nicolas on Twitter (@nicolas_frankel)
• Nicolas' epic blog

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:

Does Spring Framework support Reactive @Transaction?

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.

Over time, MongoDB started to support multi-document transactions with MongoDB Server 4.0. R2DBC (the specification for reactive SQL database drivers) started to emerge, and we decided to pick up on R2DBC with Spring Data R2DBC. Both projects wanted to expose transactional behavior, so they eventually provided inTransaction(…)…

Spring Data R2DBC

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 insert/update/delete operations.
• Coroutine extensions.
• Support for custom conversions.
• Named parameters that are translated to native bind markers by using Dialect instances.
• Support for single-column projections for simple types.
• Refactored package structure.
…

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, …

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.

How can you help?

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…