spring.io Reviews & Product Details - Page 28

We can write code more clean, without xml files configuration, only with annotations tag, also this framework is very flexibility to work with micro services Review collected by and hosted on G2.com.

Currently, I do not have any dislike. I am completely to liked with this framework Review collected by and hosted on G2.com.

Spring framework comes with Plug & Play feature and it actually abide by this tag line. I started using Spring framework since its 2.5 version had launched. The best part of spring is that we can use its any component without impacting other architecture of a product already in production. Its really very light weight comes with highly optimum solution, its every product lighten most of the task of developer and allow them to focus on business logic implementation, one the main benefits I personally like is that spring ate very large level help to avoid any memory leakage.. Some of the component which I personally used and liked are SpringMVC, SpringBoot,Spring Security,Spring IOC, Spring Tsak, Spring AOP Review collected by and hosted on G2.com.

Spring most worst part was it configuration which has already been sorted out by its team in their recent release of 4.x, still if I have to say any one point I would say hard to learn & use it optimally. But above all its really a very good framework all its component are awesome. Review collected by and hosted on G2.com.

Constantly being updated with new functionality and extremely easy to use. They are definitely a a great tool if you want to divert a little bit from other products. Review collected by and hosted on G2.com.

Steep learning curve, but once you work with the product a couple of times, it is quite easy to adapt and improve. Review collected by and hosted on G2.com.

It really helps me focus on my business features instead of worrying about configuration, boilerplate code and thinks like those.

It can be integrated with almost any technology I usually use: relational database, mongoDB, redis, JMS, etc...

Moreover it has a great system of metrics, that show you what is going on in your application. In addition you can extend that mechanism to provide your own metrics.

It's perfect to build a microservices architecture because it has everything it needs embedded. You don't need a servlet container or an application server. The only thing you need in your environment is a Java Virtual Machine Review collected by and hosted on G2.com.

Its startup process is a bit slow, and the result jar is heavy (more than twenty MB). Review collected by and hosted on G2.com.

Hello world path is trivial. Getting started with Java projects can be frustrating. Boot has done a good job of addressing that issue.

Automagically binding DBs and other beans is also awesome for kicking the tires.

This results in gradual intro to the complexity rather than having to deal with everything on day 1.

Also, the ability to create a runnable jar is awesome and portable. Review collected by and hosted on G2.com.

The residual mem requirements are quite beefy compared to Boot alternatives. Review collected by and hosted on G2.com.

I like the AOP feature of Spring best. Under AOP's help, we are very convenient to use transaction in our service side. We don't need to write lots of boilerplate code in our api. Review collected by and hosted on G2.com.

Lots of xml configuration. This framework is becoming bigger and bigger. I don't need most of the new functions but I still need to import them. Review collected by and hosted on G2.com.

It has everything! Everything you need to build your perfect app is available in the Spring Framework. From Mobile to Security to Data. Spring 4 provides you with "less writing, more doing". I see it as a convention over configuration. You no longer need those nasty XML configuration file, everything can be customized with java code.

Let's not forget Spring-Boot, to easily configure your application and you're ready to go.

The community is huge! You need help with something, you have it! Review collected by and hosted on G2.com.

Spring have its limits... If you're picky enough to have a need for a certain feature, you'll need to dig into the source code of Spring to see how it's internally done to understand some concepts.

It's a big framework, so for some situations, big = slow, but it's not that bad. Depends on your needs and how you code. Review collected by and hosted on G2.com.

Good ability to help developer maintain decent code structure.

Comprehensive support for different components, such as IOC, AOP, Security, ORM, No-SQL, RESTful and Web.

Decent abstraction in security and data accessing.

Active community and flexible extension framework. Review collected by and hosted on G2.com.

Tedious work on the Dependency Injection part.

Incapable of field injection of a certain bean.

Lack of tools that can visualize the Dependencies. Review collected by and hosted on G2.com.

A full fledged framework for building web apps with enormous stability, broad reach and used by lots of people so finding a solution to a problem is usually as easy as searching it on Google and thousands of solutions will appear.

Also there are lots of tutorials, blogs and courses on how to use it.

You could even say (as one of my seniors told me) that you can't build a Java app without Spring. Review collected by and hosted on G2.com.

I can't really say that there is anything I dislike about Spring. You could say that it is too big, but that can also be one of its strong points. Review collected by and hosted on G2.com.

Great idea, separation of generated code from a custom written code using aspects. Very useful once you get past initial, undocumented struggles. Roo is completely customizable but it takes time to learn how to use it. It keeps track of schema changes and custom code that overrides what Roo would generate. Easy to remove Roo from the project and push all the AJ code into Java classes to end up with a regular Spring Java project. Scripting and automation of code generation. If you can stick to the architecture Roo prefers, it is possible to generate entire application from DB tables with one command, executing a Roo script. Review collected by and hosted on G2.com.

Steep learning curve. I wouldn't recommend Roo for someone that does not have to repeatedly create new projects/applications. For one-offs, it's better to do everything by hand as it will take much longer to learn some tricks to make it behave the way you need it. There are several issues with IDE version so I end up always using the console version. There are some undocumented requirements for SQL table and column naming that become a serious pain when generating Data Access Layer for complex schemas. When something goes wrong, it's very difficult to troubleshoot what was the issue and how to fix it. I often end up starting from scratch as it's almost impossible to go back and repeat a sequence of steps cleanly. It makes things much easier that roo.log keeps track of all actions and the very same log can be used as a script to automate when starting from scratch and repeat sequence of steps without typing everything out again. Review collected by and hosted on G2.com.