We performed a comparison between npm and Spring MVC based on real PeerSpot user reviews.
Find out in this report how the two Java Frameworks solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The solution is scalable."
"The product's most valuable feature is dependency installation."
"The most valuable feature of NPM is to trigger APMs."
"It's an open-source setting that's very scalable and easily approachable. I like that you can plug in many features to my product."
"The reversal build, gendered build, migrated PCA, and CT features are excellent."
"Dependency Injection is one of the major features which makes our life easier using Spring. It is well documented and has active communities, which provide us enormous help."
"The best feature of Spring MVC is its auto-configuration capabilities."
"The most valuable feature is simplicity."
"The interface is the solution's most valuable aspect."
"The most valuable features of Spring MVC are the modules, such as Spring Admin. All the Spring solutions work well together and are simple to maintain, such as the load balancing on the client side."
"We have found Spring is easy to use and learn."
"Spring MVC is fast and reliable."
"When we shifted from our legacy frameworks to the Spring framework, we discovered that Spring definitely made our development easier. One good example is that there is a lot of boiler plate code available that you don't have to write from scratch, making the development of web applications a much simpler process."
"I would like to see compatible versions, and what new features they will be providing. If it is a useful feature I can merge it. If it is not a usable feature, then I can ignore the newer version."
"Some of the libraries that we try to use in npm have issues with security. Also, because it's an open-source solution, I think there are lots of challenges with security. So, the security layer could be improved."
"The library could be updated."
"The product should be compatible with various programming languages, including both native and upcoming languages."
"NPM can improve the package manager. For the packages we download for our APM studio to trigger our APM driver, it would benefit if we could have the latest version of NuGet Package Manager within the package manager control. For example, Visual Studio would be good. Then it would be easy for us to get the package manager from there instead of Googling it out and matching it with the current version. It would be less time-consuming for us."
"It could provide faster performance."
"Adding more modules takes about 10 to 15 minutes each. It would be nice if they could reduce that part. The deployment time is a little high."
"The solution could be simplified quite a bit. It's unnecessarily complicated in some areas."
"We would like the deployment of this solution to be easier as, at present, it is quite complicated."
"I expect the solution to offer and include a lot of packages so that it can be configured more easily or the speed level increases, thereby helping it overcome its shortcomings."
"I saw some error messages coming up when they were getting problems actually viewing all the reports."
"Spring MVC could improve the integration with DevOps and other applications."
"I have recently had problems with the changes that were made using Spring Security."
npm is ranked 5th in Java Frameworks with 5 reviews while Spring MVC is ranked 3rd in Java Frameworks with 16 reviews. npm is rated 8.8, while Spring MVC is rated 8.4. The top reviewer of npm writes "User friendly, easy work flow, with fast deployment after compatibility check". On the other hand, the top reviewer of Spring MVC writes "Straightforward setup, highly stable, and useful online support". npm is most compared with Amazon Corretto, whereas Spring MVC is most compared with Jakarta EE, Spring Boot, Apache Spark, Open Liberty and Oracle Application Development Framework. See our Spring MVC vs. npm report.
See our list of best Java Frameworks vendors.
We monitor all Java Frameworks reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
