Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
We have a pretty large codebase developed on Spring Boot and over the course of time, we have kept adding starters as required. I am going through a bit of housekeeping and have noticed that there are quite a bit of overlap in the dependencies provided by the starters. For eg. for creating a REST API, we started out with the spring-boot-starter-web and later added spring-boot-starter-data-rest. But I just noticed that spring-boot-starter-web is a direct dependency of spring-boot-starter-data-rest.
Now I know that as a best practice, if my code is using a library directly, that library should always be a direct dependency instead of relying on another library depending on it. But Spring Boot starters are just a BOM so I am wondering if there is a better practice here.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 11 months ago.
Improve this question
I need to use Kafka in my spring-boot application and I see spring-boot has its own spring-kafka library. I am new to spring and java and confused if I should be using spring-kafka or any other application's spring-based lib rather than using the core libraries and what are the benefits of either one of them.
Spring boot with Kafka comes with various autoconfiguration out-of-the-box to save you from the trouble of configuring each and everything (though you can definitely override spring-boot opinionated autoconfiguration).
So, if you want a ready-made application to work quickly, you can take the help of spring-boot and its utilities.
If your preference is configuring each and everything to gain fine control, use core libraries.
I'd say it's just a matter of choice or preference.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I'm learnig Spring framework. I want ask about configuration style.
If XML configuration is not deprecated. When better option is using annotation config and xml config?
I read for bigger beans better is xml, but it was five years ago.
XML configuration is still officially supported by Spring. However, in practice, you can see it here and there, but in general its considered outdated by the community (ok this can be an arguable statement, so I'll state that its solely my opinion to be "on the safe side").
One example where XML configuration is still in use is large old projects (usually enterprises) that were started long time ago in the XML configuration era.
In a nutshell, for the learning purposes annotation based configurations is the way to go.
The good news are that spring is way more than the configuration, so if you'll understand how it works and what can be done with this framework, you'll be able to quickly switch from XML based configurations to Java config or annotations and the other way around
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I am a fresh Spring Boot developer coming from a Django background. I like what i see so far but I've been searching for a way to auto-generate CRUD UI from my Entities similar to how Django admin does it out of the box. I'm not averse to solutions that require a little tinkering.
Spring Boot does not provide you that kind of feature but there are some additional tools that can easily do it for you - the most popular is jHipster
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am new bee to spring. I am trying to build an application using JSP and Hibernate with Spring. Is it a good practice to use jsp, servlets and use spring to declare the database connectivity and beans in xml or should i use spring mvc please guide me.
You can use whatever part you need from spring. That is one of the best thing about springframework. If you need to use spring just for data access layer then that is fine use it just for that. If you will use it dependency injection frawework for your project then you can use it that way.
Spring MVC is just a presentation layer part of spring. I have been using springframework for last 12 years and I haven't used SpringMVC until last year. So I recommend you to use what you know best for presentation layer but I also strongly recommend using spring for back-end layer.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Jersey and RESTEasy are popular JAX-RS implementations. There are other Rest Webservice implemenations such as Restlet.
I want to know which one to use when? what is the most used implementation nowadays in web application developments.
I'd go for Spring MVC version of REST, it suppports Dependancy Inversion(DI), Also spring supports many pluggable features like support for freemarker template, jaxb, xmlbeans etc., you will have plenty of options on return data.
Also, i wouldn't disagree on using jersey or resteasy, they are very lightweight compared to spring. If you don't want to use spring, then either one of the above mentioned should work as well, there are no major pros and cons.