Spring Cloud Task 1.1.0.M2 is now available

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

What’s new in Spring Cloud Task 1.1.0.M2

This release continues to progress on 1.1.0’s main theme of improving overall task functionality as well as migrating features that existed within Spring XD to Spring Cloud Task. The main updates for this release are the following:

  • Support for Generated Task Id - A common use case for a Spring Cloud Task application is to launch it within a PaaS, like Cloud Foundry or other cloud infrastructure. Because of this, there may be a delay between the launch request and the actual application beginning. Worse, the system responsible for launching the application may not actually launch the task for reasons outside of Spring Cloud Task’s control (lack of resources, network issues, etc). This feature allows the caller to register that a task has been requested to run. This way, no request of a task is lost between the request and the actual start of the Boot application.
  • Support for External Execution Id - When executing a task on a PaaS or other cloud infrastructure, there is typically a mapping that needs to occur between the task’s execution id and the id provided by the underlying system. This feature provides the ability to correlate those two for things like log management, audit, etc.

Webinar: Consumer Driven Contracts and Your Microservice Architecture

TDD introduced many improvements into the development process, but in our opinion the biggest impact relates to code design. Looking at the code from the usage perspective (by first writing an acceptance test) allows us to focus on usability rather than concrete implementation. Unfortunately, we usually rest on our laurels not trying to uplift this practice to the architecture level.

This presentation will show you how you can use the Spring Cloud Contract Verifier functionality in order to have a fully automated solution to stub your HTTP / Messaging collaborators. Just by adding proper configuration, you’ll surround the microservices you are testing with faked stubs that are tested against their producer, making much more realistic tests.