Welcome to another installment of This Week in Spring! I can't believe how quickly this year has gone! This week I'm in Melbourne, Australia for the YOW! conference and then week it's off to Brisbane and then Sydney for the next editions of the same show. Australia is the furthest I've ever been from my 'native' timezone - so even though I always post This Week in Spring every Tuesday, I appreciate that it's still Monday for anybody west of Europe right now! Tonight, I'll join my pal, Intellij's Trisha Gee, and we'll be speaking at the Melbourne JVM User Group. I'm super excited to be here…

Last weeks' Spring Data Kay M1 is the first release ever that comes with support for reactive data access. Its initial set of supported stores — MongoDB, Apache Cassandra and Redis — all ship reactive drivers already, which made them very natural candidates for such a prototype. Let’s take a more detailed look at the new programming model and the APIs that make up that support.

Reactive Repositories

The repositories programming model is the most high-level abstraction Spring Data users usually deal with. They’re usually comprised of a set of CRUD methods defined in a Spring Data provided…

Recorded at SpringOne Platform 2016. Speaker: Dr. David Syer Slides: http://www.slideshare.net/SpringCentral/leadership-election-with-spring-cloud-cluster

Leader election allows application to work together with other applications to coordinate a cluster leadership via a third party system. A leader can then be used to provide global state or global ordering, generally without sacrificing availability. In this presentation we show how Spring Cloud Cluster provides a simple abstraction for leader election and how it is implemented using zookeeper, hazelcast and etcd.

Note that 1.0.1 release…

On behalf of the team, I am pleased to announce the GA release of Spring Cloud Data Flow 1.1. Follow the links in the getting started guide to download the local server implementation and shell to create Stream and Tasks.

General highlights of the 1.1 GA Release include:

• Builds upon Spring Boot 1.4, Spring Cloud Camden SR2, Spring Integration 4.3 and Spring Cloud Task 1.1 release improvements.

• Adds LDAP, Basic and File based backend authentication

• Improvements to OAUTH backed authentication

• LDAP authentication is now supported with SSL

• Adds a form-based login page for non-OAUTH backend authentication methods such as the LDAP, Basic and File-based options

• Adds the ability to pass application specific properties via YAML file. This is particularly useful when deploying streams that require many deployment properties to be set.

• Portable deployment properties for memory, disk and cpu are in place for support across various runtime implementations.

  …

On behalf of the Spring Data team, I’d like to announce the first milestone of the Kay release train. This is a special release train as it's going to ship a new generation of Spring Data that will include a couple of breaking changes going forward.

Infrastructure upgrades

The first and most noticeable change is the upgrade to Java 8 as a minimum baseline (no JDK 6 compatibility anymore) and an upgrade to Spring 5 as framework foundation. In subsequent milestones we're going to ship some significant internal rewrites that will also affect user facing API to make use of the new language…

On behalf of the Spring Cloud Data Flow team, I am pleased to announce the 1.1.0.RC1 release of Spring Cloud Data Flow for Apache YARN.

Spring Cloud Data Flow for Apache YARN allows one to use all the goodness of Spring Cloud Data Flow (like the Shell and UI) while targeting Apache YARN as a backend. Stream components are deployed as individual apps in Apache YARN, leveraging the power of the platform to handle scaling and health monitoring.

This first release candicate

• Builds upon Spring Cloud Data Flow 1.1.0.RC1 and Spring Cloud Deployer 1.1.0.RC1.
• Support for keeping multiple deployer versions in hdfs.
• Preparation of supporting upgrades on Ambari when these become available with Ambari future versions.
…

On behalf of the community, I’m pleased to announce the release of Spring Session 1.3.0.RC1. This release release closes lots of community submitted Pull Requests. For a complete list of changes see the changelog.

What’s New in Spring Session 1.3.0 RC1

Highlights include:

• First class Spring Security’s RememberMe Support

• Updated guides to use Lettuce

• OrientDB Support

• Configuration Improvements

• Performance Optimizations

• Bug Fixes

Contributions

Without the community we couldn’t be the successful project we are today. I’d like to thank everyone that created issues & provided feedback…

Speaker: Josh Long https://www.twitter.com/starbuxman

Hi Spring fans! In this tip, we'll look at Cloud Foundry, a an open-source cloud platform that's optimized for managing applications. To those of you in the US, happy Thanksgiving tomorrow!

We are pleased to announce that Spring Cloud Task 1.1.0.RELEASE is now available via Github and the Pivotal download repository. Many thanks to all of those who contributed to this release.

Spring Cloud Task 1.1.0 offers the following features:

This is the generally available release (GA) for 1.1.0. This release addresses key enhancements to the project to allow for better coverage of operational concerns for tasks in a cloud environment. Features new to the 1.1.0 line include:

• Updated error handling - 1.0.x stored stack traces that were the result of task executions within the TaskExecution#exitMessage field, requiring that this field perform double duty. First it was available for orchestration of tasks (similar to StepExecution#exitStatus in Spring Batch) as well as the storage of stack traces for debugging. In the 1.1.0 release, error messages have been moved to a new field TaskExecution#errorMessage so that each field has it's own, dedicated use.

• Updated customization options for partitioned batch jobs - In the 1.0.x line for Spring Cloud Task, when launching workers as tasks, there was not a way to customize the command line arguments provided to them. This is an issue in environments like CloudFoundry where you can use command line args to customize configuration without the need to re-push your app. In the new 1.1.0 release, we provide the ability to customize command line arguments via the CommandLineArgsProvider which is similar in functionality to the EnvironmentVariablesProvider introduced in 1.0.2.

  …