Spring IO 25–27
Last week, I had the pleasure to participate in the Spring IO in Barcelona, which took place from the 25th to the 27th of May.
After 2 years of virtual meetings, one could feel the enthusiasm and see the joy in each of the 1200 attendees’ faces. It was more than a pleasant experience. We had the opportunity to learn, discover and share knowledge about the Spring ecosystem with almost — 60 conferences, keynotes, and workshops. Allow me to share three main points I picked up from the event.
Before going further, a big thanks to Sergi Almar and the entire team behind the planning. The event was amazing: the venue, sessions, show, meals, and even the weather: Massive thanks! 🙏🏿🙏🏿🙏🏿
“Spring 6.0 will be the new beginning of the next decade of Spring”
The welcoming of Spring 6 was the main point. It’s planned for October in GA, with a release candidate in July, and you can already start playing with Milestone 5.
This will also come with a new version of Spring-boot 3 since Spring 6.0 will be the new beginning of the next decade of Spring. All Ecosystem is building the tools to leverage the developer experience:
- works on native image to speed up the start, and lightening artifacts, and resources needed to run applications ( spring aot, reactive Programmation, building native image…)
- Take full advantage of the cloud env and especially the now well-established Kubernetes ( spring cloud Kubernetes, going serverless with spring, knative…)
And so much more, all of this sounds like a sprint to catch Micronauts and Quarkus, in the race for subatomic framework.
My second takeaway is about Open rewrite.
In a world where change is the only constant, we need to adapt fast and sometimes — very often.
Thanks to Tim Te beek , I discovered the openrewrite; a tool that allows you to perform major migrations easily, by applying existing recipes. You can also combine them and even better make your own recipes.
After struggling with log4J, spring4j vulnerabilities, as well as migration of spring in these last months, I appreciate how useful this tool could be to major organizations — especially when you have a lot of code spread around several microservices…
If you care about keeping your codebase up to date in a distributed system, you should definitely consider it.
Problems are the favorite costumes of opportunity.
The last one blew my mind — mostly because we are currently trying to trigger distributed jobs at my workplace and are facing many challenges: retrying failing jobs, monitoring of jobs, scalability when needed, administration, etc
Existing tools which cover these sometimes come with a lot of complexity or lack some of the desired features, and not all of them have a built-in dashboard. We were also looking for a solution that would not be too invasive for our existing business code.
Jobrunr solved most of these challenges, it was really what we were looking for:
- Simple to use and implement.
- Offer a dashboard for administration and monitoring, user and non-tech friendly.
- Scalable and cloud-friendly.
- And also with a 🌱 green approach behind it.
Ronald Dehuysse perfectly describes the origin of the product and a global overview of JOBRUNR and also a little bit of all the magic behind the tool. I’m looking forward to implementing it and seeing how to go further with this.
So much more
As you might have already figured, these takeaways are fairly subjective and linked to my own context, but you can find other interesting topics from the event agenda here. As usual, the sessions will be available on the youtube channel — just subscribe, and if you need one more reason to watch them, did I mention how Josh Long was outstanding (like always) at live coding?
Feel free to share your own take aways, and make sure to save the date for next year, 25th–26th May, for the 10th anniversary.
I, can’t wait to be there!
Hasta el próximo año!
