The Spring Blog

On the heels of the previous blog in which we introduced the basic functional programming model for writing streaming applications with Spring Cloud Stream and Kafka Streams, in this part, we are going to further explore that programming model.

Let’s look at a few scenarios.

Scenario 1: Single input and output binding

If your application consumes data from a single input binding and produces data into an output binding, you can use Java’s Function interface to do that. Keep in mind that binding in this sense is not necessarily mapped to a single input Kafka topic, because topics could be multiplexed and attached to a single input binding (with comma-separated multiple topics configured on a single binding - see below for an example). On the outbound case, the binding maps to a single topic here.

Dear Spring community,

With Spring Framework 5.2.2 and 5.1.12 being available now, let me take the opportunity to provide an update on the maintenance roadmap in 2020.

Most importantly, Spring Framework 4.3.x and therefore Spring Framework 4 overall will reach its end-of-life next year: Our EOL cut-off is December 31st, 2020, with no further support on 4.3.x beyond that point. At the same time, we are also phasing out 5.0.x and 5.1.x for good.

As for planned releases, first up is a full round in mid January: with 5.2.3 and 5.1.13 accompanied by 5.0.16 and 4.3.26. The latter are the last maintenance releases in the 5.0.x and 4.3.x lines. We may do critical patches in case of vulnerabilities but otherwise no further releases are planned in those lines until the final cut-off at the end of 2020.

On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Framework 5.2.2 and 5.1.12 are available now.

The second maintenance release of the 5.2 line includes over 100 fixes and improvements. Spring Framework 5.1.12 includes 25 selected fixes and improvements.

As usual, we’ll follow up shortly with corresponding Spring Boot releases (2.2.2 and 2.1.11).

See you early 2020 for a full round of Spring Framework releases, from 4.3.x up to the 5.2.x generation. More on that in a future blog post, stay tuned!

Hi, Spring fans! Can you believe - and I can’t, by the way - that we’re already in December 2019? The last month before the new year? The last month of this decade? It defies belief! I can’t even imagine how we got this far so quickly, but it’s great that we did. I started writing This Week in Spring in the first week of January 2011, so we’re fast approaching 9 years of This Week in Spring!

As I write this I am in Toronto, Canada, for the last stop on the SpringOne Tour train for 2019. I enjoyed giving a two-hour talk introducing all sorts of stuff in the wide world of Reactive Spring yesterday. Now, I am just biding my time, preparing for my departure to Australia later today. I am off to Australia for two stops on the YOW! conference circuit. I wholely look forward to seeing everyone there!

This is the first in a series of blog posts in which we will look at how stream processing applications are written using Spring Cloud Stream and Kafka Streams.

The Spring Cloud Stream Horsham release (3.0.0) introduces several changes to the way applications can leverage Apache Kafka using the binders for Kafka and Kafka Streams.
One of the major enhancements that this release brings to the table is first class support for writing apps by using a fully functional programming paradigm. This blog post gives an introduction to how this functional programming model can be used to develop stream processing applications with Spring Cloud Stream and Kafka Streams. In the subsequent blog posts in this series, we will look into more details.

Hi, Spring fans! In today’s episode Josh Long (@starbuxman) talks to Spring Tools lead Martin Lippert (@martinlippert) about his time at Pivotal, and on the Spring team, his work on Spring Tools, and his work on language servers that now serve as the foundational integration for Spring users using Microsoft’s Visual Studio Code, emacs and Atom, among other things.

Thanks, dear listener, and Happy Thanksgiving!

• Spring Tools
• Martin Lippert’s profile page
• the Wikipedia description for Thanksgiving

On behalf of the community, I am pleased to announce that the General Availability (RELEASE) of the Spring Cloud Hoxton Release Train is available today. The release can be found in Maven Central. You can check out the Hoxton release notes for more information.

Notable Changes in the Hoxton Release Train

Spring Cloud Hoxton.RELEASE is based on Spring Boot 2.2.1.RELEASE.

Documentation Changes

The Hoxton.RELEASE docs have a new landing page, new theme and a single-page, multi-page and a pdf version.The landing page will link you to the documentation for the specific project you are interested in. We hope you find that the new documentation structure easier to consume.

We are pleased to announce the general availability of Spring Cloud Open Service Broker 3.1.0.RELEASE. Support for Open Service Broker API v2.15 is now feature complete. Thanks to the community for your feedback and contributions! This release includes all of the fixes and enhancements from the pre-release milestones:

• Upgrade to Spring Boot 2.2.1.RELEASE
• Add ServiceBrokerMaintenanceInfoConflictException to handle MaintenanceInfoConflict error scenarios
• ServiceBrokerInvalidParametersException now returns an HTTP 400 when a create or update request is malformed or includes invalid parameters. Previously it was, incorrectly, returning an HTTP 422.
• CreateServiceInstanceBindingRequest now extends AsyncParameterizedServiceInstanceRequest in order to utilize a common request object and reduce redundancy.
• Update reference documentation
• Support updating a Service Instance context
• Add list of endpoints to create Service Binding response body
• Support X-Broker-API-Request-Identity request identity header
• Restrict Operation strings to 10,000 characters in the response body
• Fix an issue where ServiceInstanceBindingDoesNotExistException was incorrectly extended from RuntimeException, instead of ServiceBrokerException
• Add maintenance_info field to Service Plan object
• Add maximum_polling_duration field to Service Plan object
• Add plan_updateable field to Service Plan object
• Return HTTP 400 when the required service_id and/or plan_id are missing or incorrect
• Return HTTP 202 when a service broker operation is in progress and an identical request is sent before the previous request completes
• Return JSON arrays instead of JSON objects for certain Service definition metadata
• Add support for custom base path of service broker controllers
• Improve support for service metadata in configuration properties
• Add support for configuring Base64 metadata.imageUrl data from a class path image file
• Improve configuration of event hooks via additional bean and auto-configuration support

Hi, Spring fans! Welcome to yet another installment of This Week in Spring! This week, I’m in Tokyo, Japan, for the Pivotal Summit Japan event. I’ve regretfully had to miss the China and Korea events because of a famly emergency, so it’s nice to be able to make this, the last stop on the tour, before returning to California to celebrate Thanksgiving with the family.

And, on that note… it’s almost Thanksgiving in the US. Thanksgiving is a time for us in the US to reflect on that for which we’re thankful. I think I speak for the entire Spring team when I say that we are very grateful for you all, dear (worldwide) community! Happy Thanksgiving, all!