Why not a spring framework?

Question

Are there any flaws to link my application with the Spring framework?
I am not talking about errors or problems, if any. I am talking about strategic architectural things that will influence my lifestyle. Should I prefer Spring over the basic Java EE features supported by the EE container? What are the benefits?

Thanks.

Answer 1

standard flaw for any technological solution: If you chose Spring, and then want to return to pure Java EE, then the transition will do some work (or a lot depending on how you use spring).

Note that Spring is a battle-tested platform used by probably 10 thousand Java applications (possibly more). This is not like his fringe technology, which may not be supported in the future.

Any of them are a great choice.

Answer 2

First of all, you can consider a list of all the components of your application in different boxes. Identify each box with the correct technology that you want to accept for delivery.

Then see if any of these technologies that are planned have the ability to work with Springframework. The current springframework supports a lot of third-party integration from ORM login.

From here you will see the benefits or justification for whether you should accept Springframework or not.

The key here is to look at CBA (Cost-Benefit Analysis), but rather, building your application architecture fits into any choice of structure that you encounter. The layman’s simplest question is to answer: “Do I need it to work?”