Wintellect, a Microsoft-focused consultancy, blogs on JavaScript frameworks, Azure, .NET, F#, and enterprise development.
HN commenters link it mainly for its Azure-to-AWS service name comparison; no wider opinion is given in the comments.
The big clouds have similar enough products, just the names are changed, so at a high level, GP's list of AWS products can be swapped with eg, Azure's product names. https://www.wintellect.com/the-rosetta-stone-of-cloud-services-windows-azure-and-amazon-web-services/
Sadly, anything more in-depth than that, you'll need to sign an NDA with AWS to learn anything about the performance limits of their services (eg Redshift), and you won't get that unless you're already a big customer there. Azure's not going to be falling over themselves to let you know where they fall short, either. This is vendor lock-in, and is why there are so many free cloud credits to be had to startups.
This is also a reason I believe SaaS companies will find it is harder than they realized to arbitrage between clouds, and business models based on that may not be able to get that right.
You catch a good spot, thanks ! In future i will create multiple controllers, sure depends with the logical concern.
I will read read style guide and ng-annotate.
Unit testing is crucial you are right. I need to add to seed project.
By the way what do you think about this article ?
http://www.wintellect.com/blogs/jlane/five-reasons-asp.net-developers-shouldn%E2%80%99t-worry-about-node