Win a copy of TDD for a Shopping Website LiveProject this week in the Testing forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Spring Quickly: Building a new application

 
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Good day,

If a developer or a team is building a new application, what are the factors to be able to decide if Spring is the right framework to use? Or use another one, like Grails or Play?

Regards,
Joey
 
Author
Posts: 51
5
Spring Java
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Joey. Thanks for your question. A difficult question I can say. I'll try to put some points I learned from my experience that you need to take into consideration for choosing a framework.

1. Does the framework have a big community? Make sure you choose a framework with a big and active community to get easier over problems you may encounter. You need to make sure you have who to ask questions at some point.
2. Is the framework still developed or only maintained? You need to make sure you choose a framework that is both maintained and still developed. Our domain changes quickly and you want to make sure next year you'll be able to use new inventions
3. What does your team know? You need to take into consideration of course what the members of your team already know. Say you have two frameworks A and B. These two frameworks both have a big community and are developed and maintained. If most members of your team know how to use B, then of course in your project best will be to choose B and not A.
4. How easy is to find developers who know to use that framework? Is the framework still new? Sometimes we like to use new technologies but this comes with a risk. If in the future, it won't be that hot anymore, you'll end up with increased costs and difficulty of finding new devs for the team.

I honestly like the discussion on this aspect. There're probably more points but I've tried the most relevant that come now to my mind

Cheers!
 
I hired a bunch of ninjas. The fridge is empty, but I can't find them to tell them the mission.
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
https://coderanch.com/t/751654/free-earth-friendly-heat-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic