Last post Jan 17, 2017 04:33 PM by bruce (sqlwork.com)
Jan 15, 2017 02:12 PM|victorTheHammer|LINK
Hello, i am a student, i am working in another domain then programming, i would like to hear your thoughts about this.
I need to build a highly scalable website, actually i need it to be as cheap as possible since my cash reserves are rather limited.
Apart from various caching strategies and so forth, here is one strategy i want to implement.
I will have 2 separate sites.
One will be a NodeJs powered website, that will serve static content (scripts, css, angular 2, have webpack running on it).I want to have it NodeJS because i want to learn a bit about Node in the process, and it is really hard to work with Angular 2/typescript
enviromnent in visual studio for me.( some will disagree and thats fine ).
The other will be a ASP.NET WEB API 2 powered website, which will only expose some endpoints for the nodejs application to consume data.
Both will be hosted in Microsoft Azure's Web Apps.
Is this a good idea? are there any drawbacks, what do you guys think?
Jan 17, 2017 04:33 PM|bruce (sqlwork.com)|LINK
your architecture is pretty classic 3 tier. node is very popular for the UI frontend. the middle tier is usually java, .net or node.
while main event loop is single threaded in node, the async i/o system is multi-threaded and will make use of the second cpu. node is highly scalable and generally has higher performance than asp.net (the new asp.net core is built on the same async lib as
node and can out perform node).
the main drawback is the frontend and backend are different languages and can not share code. an all node solution would be simpler, but your setup is not uncommon.