Welcome to another installment of This Week in Spring! This week I’m in Budapest, Hungary, for the amazing Craft Conf. This show is a very special show indeed. Special, for me, first in that I’ll be joined by industry titans like Adrian Cochroft, Jez Humble, Sam Newman, and Kyle Kingsbury, and in that I’ll join two of my friends from Pivotal - Andrew Clay Shafer and Bridget Kromhout (also titans)! I’m so excited to be among these, and many more, that I can hardly contain it and I recommend you consider making the trip if it’s convenient, one day, yourself.
The Spring Blog
Following previous Reactive Spring and Reactor Core 3.0 blog posts, I would like to explain why Reactive types are useful and how they compare to other asynchronous types, based on what we have learned while working on the Spring Framework 5 upcoming Reactive support.
Reactive types are not intended to allow you to process your requests or data faster, in fact they will introduce a small overhead compared to regular blocking processing. Their strength lies in their capacity to serve more request concurrently, and to handle operations with latency, such as requesting data from a remote server, more efficiently. They allow you to provide a better quality of service and a predictable capacity planning by dealing natively with time and latency without consuming more resources. Unlike traditional processing that blocks the current thread while waiting a result, a Reactive API that waits costs nothing, requests only the amount of data it is able to process and bring new capabilities since it deals with stream of data, not only with individual elements one by one.
The latest milestone version of Spring Cloud is “Brixton.RC2” and it is available now from the usual repositories (details in the home page). This is a bugfix release building on the RC1, and there are no notable new features. If all goes well we’d like to get to a RELEASE in a week or two.
Welcome to another installment of This Week in Spring! This week I’m in Stuttgart and Mainz, Germany and Paris, France, speaking to customers and at the JAX conference, then it’s off to Paris, France, to speak at the Devoxx France edition. If you’re around in any of these places don’t hesitate to reach out I’d love to say hello.
Also, tonight, I’ll be joining my friends from industry (Daniel Bryant, Markus Eisele, and Simon Maple) for the ZeroTurnaround webinar, Microservices for the Enterprise. There are already more than 3,000 people registered and I hope to see you there, as well!
One of the nice things about working for Pivotal is that they have a great agile development division called Pivotal Labs. The teams within Labs are big proponents of Lean and XP software methodologies such as pair programming and test-driven development. Their love of testing has had a particular impact on Spring Boot 1.4 as we’ve started to get great feedback on things that could be improved. This blog post highlights some of the new testing features that have just landed in the latest M2 release.
Let’s talk about Pivotal. Our ambition is to make business more agile, to reduce the time around the innovation loop; speed is the single biggest advantage an organization can have. Pivotal’s main “product” is agility. This translates naturally into technology. Microservices are well-defined, small, easy-to-evolve, independently deployable batches of functionality. They lend themselves to rapid iteration because they’re small. Spring Boot and the Spring ecosystem make short work of standing up new microservices and applications, and Spring Cloud handles the complexity in distributed computing. Cloud Foundry automates the continuous deployment and management of applications. Distributed systems create valuable data which, when processed, can help drive direction. Pivotal Labs, our transformation arm, is a pioneer in agile development methodologies and continuous delivery, both essential when iterating in a dynamic market.
Spring Boot 1.4.0 MILESTONE 2 is out! This is a good time to tell you about the joint effort between Spring Boot team members and the Couchbase Java SDK team to offer a first class integration of Couchbase into Spring Boot :)
Spring Boot 1.4.0, Couchbase becomes a first class citizen of the Spring Boot ecosystem!
This article explains some of the dependency management tricks that
can be used to create libraries and apps that depend on newer versions
of a transitive dependency than that managed by a platform like
Spring Boot or the
Spring IO Platform. The
examples below uses Reactor as an example
of such a dependency because it is nearing a major new release (2.5.0)
but existing dependency management platforms (Spring Boot 1.3.xq)
declare a dependency on older versions (2.0.7). If you wanted to write
an app that depended on a new version of Reactor through a transitive
dependency on a library, this is the situation you would be faced
Welcome to another installment of This Week in Spring! This week I’m in wet and wonderful New York City. It’s already almost tax-day here in the US! Whew! time is sure flying. Other (markedly more pleasant) annual landmarks will soon be here, including our big SpringOne Platform event, so book your tickets now!
Also, I’ll be joining my friends Simon Maple, Daniel Bryant, and Markus Eisele for a webinar on microservices on April 19th - join us! It should be fun and - hopefully - interesting!
As usual, we’ve got a lot to cover so let’s get to it!
Greetings Spring community,
Spring WS has just released version 2.3.0.RELEASE. This is a major upgrade where we have updated several core dependencies such as Apache Wss4j 2 (from 1.6). I recommend upgrading to ensure you have the latest fixes. For a listing of completed issues see the report below:
The artifacts are staged on maven central, http://repo.spring.io/release, and bintray.