3 ms·

If you are looking for a new web framework and new database that will last you for 5 years, you're better off sticking with something mature. I'm a bit biased,

If you are looking for a new web framework and new database that will last you for 5 years, you're better off sticking with something mature. I'm a bit biased, since I went from .NET to Ruby on Rails, but I realize that RoR may not have the 5 year shelf life you are looking for. Honestly there are so many changes going in the web world, you are better off experimenting with a few and then deciding. Its impossible to say who will be on top in 2017. Its highly likely that the hot framework of 2017 doesn't exist today. I would look at RoR, Play 2.0 with Scala, Django, and ExpressJS with Node. For front end stuff look at Backbone. On the database side, stick with relational by default but experiment with NoSql solutions for non-critical data storage (logs, write once activity streams, etc). Get understanding of the persistence mechanisms and gotchas before fully committing. Good luck!

chrislomax 15y ago
Well another dev and myself just had this exact same conversation. There is a lot changing and I see a new technology on Hacker News every day. To be honest, the main reason to look around is because there is so much change happening. I don't believe .net is the best for us, we use it because we have so much written in it and our libraries are very large. I am currently looking at NoSQL, Mongo seems to be the one we are favouring at the minute. The one thing that really makes me want to experiment is knowing that sites like Facebook use multiple technologies to run the site and that's how I want to be. I currently feel stagnant and trying to make our projects fit into .net. I appreciate your comment
- hkarthik 15y ago
  I think a good strategy to insulate yourself from .NET is to slowly move your .NET code into RESTful services and isolate the dependencies there. The one big downside is that most of the alternatives are designed to work better with Unix based systems. That's usually a much bigger pill to swallow for an all Windows .NET shop so YMMV with pushing that. I know a shop trying to do Node.JS on IIS so that may be an option worth looking into to see if it works. YMMV here too, because it's really bleeding edge right now.
  - chrislomax 15y ago
    Well I was aware of the IIS node.js plug-in. I am really interested in node.js as well. It may be worth like you say putting it into a service that we could consume from many languages and taking it from there. Our main issue really is our admin as it relies quite heavy ContentPlaceholders as we populate them on runtime but I am more interested right now in trying new technologies

chrislomax 15y ago

Well another dev and myself just had this exact same conversation. There is a lot changing and I see a new technology on Hacker News every day. To be honest, the main reason to look around is because there is so much change happening. I don't believe .net is the best for us, we use it because we have so much written in it and our libraries are very large. I am currently looking at NoSQL, Mongo seems to be the one we are favouring at the minute. The one thing that really makes me want to experiment is knowing that sites like Facebook use multiple technologies to run the site and that's how I want to be. I currently feel stagnant and trying to make our projects fit into .net. I appreciate your comment

hkarthik 15y ago
I think a good strategy to insulate yourself from .NET is to slowly move your .NET code into RESTful services and isolate the dependencies there. The one big downside is that most of the alternatives are designed to work better with Unix based systems. That's usually a much bigger pill to swallow for an all Windows .NET shop so YMMV with pushing that. I know a shop trying to do Node.JS on IIS so that may be an option worth looking into to see if it works. YMMV here too, because it's really bleeding edge right now.
- chrislomax 15y ago
  Well I was aware of the IIS node.js plug-in. I am really interested in node.js as well. It may be worth like you say putting it into a service that we could consume from many languages and taking it from there. Our main issue really is our admin as it relies quite heavy ContentPlaceholders as we populate them on runtime but I am more interested right now in trying new technologies