we plan to use Spring Batch for mission critical production batching system. And I am wondering which version we should choose now?
From the version history in github(https://github.com/spring-projects/spring-batch/tags): version 4.2.7 is marked with .RELEASE, while 4.3.3 is not.
So the questions are:
1、what's the difference regarding the versions with or without .RELEASE ending, is the ".RELEASE" ending verison more stable?
2、which version is recommended for production now ?
Thanks a lot!
Both are production ready releases, one for the 4.2 line and the other for the 4.3 line. I recommend using the latest 4.3 as it has an extended support lifetime. Spring Batch follows the same support terms as Spring Boot, and each version will be supported as long as the latest Spring Boot version that brings it is supported, see https://github.com/spring-projects/spring-boot/wiki/Supported-Versions.
For example:
the latest Spring Boot version that brings Spring Batch 4.2 is 2.3 which will be OSS supported until May 2021.
The latest Spring Boot version that brings Spring Batch 4.3 is 2.5 which will be OSS supported until May 2022.
etc
Spring Boot 2.6 is expected on November 2021 and will likely bring Spring Batch 4.3 as well, which extends the OSS support for Spring Batch 4.3 for another year. So I recommend using the latest version from 4.3 to benefit from a longer support period since you are planning to use it in production. FTR, there is an ongoing effort to update the website/wiki with all these support details across the portfolio, so keep tuned.
In regard to the version name scheme, we (the Spring engineering team) have decided to switch from the old naming scheme (.BUILD-SNAPSHOT, .RELEASE, etc) to a new naming scheme. This has been announced on our blog here: Updates to Spring Versions.
Related
My project is currently working with an elder spring boot version 1.5.7 and we wanna use a mongodb 4.0
Due to the gap between spring boot versions 1.5 to 2.X, i would like to upgrade for now the mongodb driver only by using a 3.8.2
My need is only some records and fetchs, any ACID specifics needs sure as update a doc with several processes
I tried locally and i got any errors,
My question is although it's not the best way, is there any fallback by doing that?
(Notes: I will upgrade my spring boot version later)
Thank by advance
Spring Boot is an opinionated framework and also has opinions about the used dependency versions.
So it's never a good idea to upgrade the dependency versions without upgrading Spring Boot itself.
I would not recommend to upgrade just the Mongo DB driver.
Currently I am using Rundeck 3.0.23-20190619.
Whether Rundeck 3.0.23-20190619 is stable version?
From the https://bintray.com/rundeck/rundeck-rpm/rundeck able to see the Rundeck 3.0.23-20190619 is not yet published as GA.
2.11.14-1.70.GA is the latest GA version with build date 2019-09-13T03:37:04.000Z.
Will the application developed with 3.0.23-20190619 compatible with 2.11.14-1.70.GA?
Right now the latest stable release is 3.1.2, you can check the latest version in the changelog here. The "GA" notation is not used anymore. In some cases, you can see some updates of 2.11 / 3.0 branches focused on backports, not for new features, etc.
Your projects and jobs are compatible using 2.11, 3.0 and 3.1 branches.
I am seeing 2 versions (9.0.1 vs 8.2.1) of wildfly which were released on the same day. What is the difference between two versions and why there are 2 versions exist in parallel? I couldn't find it over the internet.
Wildfly ships on a very fast development cycle. Each major release 8.x, 9.x, 10.x contains major changes from the previous version. All current major work is being done on the 10.x beta versions.
The minor versions are for bugfixes related to that particular release. Since there are now people in production with both 8.x and 9.x, any critical bugs or security patches go into one of these releases. It is very possible a security issue could exist and be fixed in both 8.x.1 and 9.x.1.
JBoss EAP, which is based on WildFly, deliberately has a slower release schedule. For each major version they release they offer paid support for 4 years, so they change major versions much slower.
There is a good slide of the lifecycle of WildFly/JBoss on page 9 of this slide-deck from the RedHat Summit in June:
http://videos.cdn.redhat.com/summit2015/presentations/12186_red-hat-jboss-enterprise-application-platform-7-roadmap-new-features.pdf
Here is the official announcement for the pair of releases: -
http://wildfly.org/news/2015/07/23/WildFly-901-and-821/
Seems the MongoDB release is a significant performance upgrade - ay idea when Spring Data MongoDB will support this version?
Strictly speaking, the MongoDB 3.0 server can even be used with the latest 2.13 Java driver and thus the currently released Spring Data MongoDB 1.6.2. For a full compatibility overview of the driver and server versions, see this wiki page.
The recently released first release candidate of Spring Data MongoDB 1.7 ships support for the MongoDB 3.0 Java driver. This is mostly a compatibility release, we don't target special 3.0 features yet (although you should be able to benefit from an upgrade nonetheless).
Find more information about this in the release train wiki, the JIRA ticket as well as the corresponding section of the reference documentation.
The GA release of Spring Data MongoDB 1.7 is scheduled to be part of the Fowler release train GA end of March.
Spring Data Mongo has 1.7RC1 -> http://docs.spring.io/spring-data/data-mongo/docs/1.7.0.RC1/ Hopefully that one will be released soon.
As Java Driver github repo says, they released a 2.13.0 version on January 29th and it is stable -> https://github.com/mongodb/mongo-java-driver/releases/tag/r2.13.0 It includes all the features for mongo 3.0, but you need to go through the compatibility to upgrade to this version.
Also, they are working on v. 3.0.0. for Java Driver, you can find it here -> https://github.com/mongodb/mongo-java-driver/releases/tag/r3.0.0-beta3 (its still in beta though)
We are using JBoss 4.2 GA, and need use a newest version in some new project.
I heard that JBoss 5.0 encounter such bugs... is this correct?
If not, which exact version of 5.0 to use?? and what about 6.0??
Thanks.
JBoss AS 5.1 is perfectly fine. Every app server has bugs, they're big, complex applications in themselves, but 5.1 is solid.
JBoss AS 6 hasn't been released yet, it's still in beta.
Jboss Application Server 7 is released, and up to a beta version of 7.1.0. You can download a copy here, and find the Getting Started Guides here.
As with any major revision of an application server, there are significant changes that might impact upon your business and will need to be considered in the context of your use case. Being an open source project, the early praise and early bugs are in the public arena, so it is easy to research for yourself.
Working on a documentation project involving AS7 I have seen some of the great work that the team has undertaken, and I couldn't imagine going back to a previous version now I've enjoyed the fast boot-up times, the ease of application deployment, custom configuration and the powerful Management CLI.
These kinds of improvements and features, not just constrained to JBoss Application Server or JBoss Enterprize Application Platform, speak volumes about the speed, stability and usability that will be increasing exponentially in this field for all competitors over the coming years. I'd urge you to check out the current generation of application servers if your experience is largely with JBoss AS 4.2.