Not only the weather outside brought Spring to us. In the first round of the first conference day, Stéphane Nicoll as one of the main contributors presented the news around the next major Spring Framework Release.
Whereas the support for Java 9 will only come with the 5.1 Release he announced the support of Kotlin. This statically typed language will surely accommodate fans of functional programming. Almost a marginal note was the implementation of an @Index-Annotation in order to reduce the effort of the component-scan from the Build-time and shift it towards the Compile-time. Consequently, the startup time in Spring 5 will be further accelerated.
Undoubted the main new feature is the support for reactive programming. The target consists in opening up new possibilities. Looking at not-reactive components also in future they will be available and will be further developed.
In the next session from Kai Tödter, a webservice including frontend and backend was developed and automatically deployed into the AWS within only one hour. For a kickstart the Spring Boot Initializer and AngularJS Seed was used. After a few smaller adjustments it only had to be tied up to Docker and was ready for upload. In the end the deployment into the AWS could be easily controlled and automized by using Terraform. The really remarkable point was the speed of development. This clearly shows that the used frameworks allow focussing on the development of business logic.
Besides the question, how microservices can be developed and deployed, Industry 4.0 with continuous data streams brings new challenges. Spring Cloud Data can offer answers. This was subject to the session of Nicolas Byl who also used a demo to present the features. The first part of the session focussed on showing how sources, processors and sinks can be easily generated through a DSL in order to process data streams. Every type of the mentioned three components is connected by queues of a messaging service such as Kafka.
For many use cases there are already components available. In addition, each of them is a Spring Boot Application. So, it is quite easy to create and use your own implementation. As a second aspect, the usage of Batch-Pipelines was demonstrated by triggering the next batch-job with the end-signal of its predecessor it’s easily possible to assure dependencies between the single processes. The most remarkable point was the fact how easily those pipelines can be created without restrict the developer.
Thus we can resume that Spring is the best enabler for cloud or industry 4.0 projects and will thus increasingly play a bigger role in the future.