3 ms·
Seeing as you're more experienced on the Windows stack (saw your C# posts), I'd suggest not dealing with NodeJS at all if your aim is to push out and maintain t
by acesubido 14y ago
Seeing as you're more experienced on the Windows stack (saw your C# posts), I'd suggest not dealing with NodeJS at all if your aim is to push out and maintain this project with less friction.
If you're thinking it'll scale, it's much better to deal with scaling problems in a stack you're familiar with. So for your server stack I'd suggest these:
- PaaS: AppHarbor or Azure Cloud Services. You can easily scale up with them by a few clicks.
- Server-side: Seeing as you chose NodeJS, I assume you're going to use the stack's asynchronous nature, might I suggest looking up SignalR (http://www.hanselman.com/blog/AsynchronousScalableWebApplicationsWithRealtimePersistentLongrunningConnectionsWithSignalR.aspx http://www.hanselman.com/blog/AsynchronousScalableWebApplica...)
- ORM Layer: NHibernate
- DB: MySQL
Again, I'm not saying not to use NodeJS because I'm some sort of Microsoft Fanboy, I'm just giving suggestions based on how much "better" you can push out your project "quicker", and maintain/support it with lesser friction.
- JeremyMorgan 14y agoI'm more experienced on the Windows Stack, but one problem I have is this is going to be a "for fun" project that's likely not going to turn a profit in any way. I would gladly throw it on an Azure instance, but I'm afraid of paying a few hundred bucks or more a month for something when I could just do it for free. If I could find a way to monetize it without pushing away fans it may be an option. SignalR is one of the options I forgot to mention, I don't have any experience with that but it may serve my purpose well so I'll be looking into that. Thanks for the suggestion!