Amazon EC2 Auto Scaling vs. .NET

[Amazon EC2 Auto Scaling] is simple to set up and pretty self-explanatory. Never had issues around scaling up or down. [Now] we won't need to guess the capacity for our apps or services. The both scaling, up and down is simply perfect, you can actually stop checking every time for resources because this tool takes care of everything

Incentivized

If you need to build anything from a quick-and-dirty GUI utility to a full-fledged desktop application, .NET is the way to go. It doesn't require extensive knowledge of the languages as Visual Studio is extremely helpful in its autocomplete, refactoring, and prompts, and lets you build out your solution easily without worrying about the details of [the] setup and boilerplate.

Incentivized

• Dynamic scaling can be configured to respond to a wide variety of metrics and alerts
• Predictive scaling allows one to get ahead of high traffic events rather than simply reacting to them
• Health checks are configurable based on the needs of your application and architecture

Incentivized

• Visual Studio is one of the best IDEs and .NET is the best framework to use with Visual Studio.
• There is a large network of support for the .NET framework.
• The .NET framework encompasses a very large area of the programming stack.
• The .NET framework is flexible and can be used for desktop applications or web development.

Incentivized

• Sometimes, Auto scaling takes time to spin up your instances if your traffic is so high in short span of time.
• And, Auto scaling can be more efficient if we have only Load balancer in our architecture.
• It has some limitations on setting up the Auto scaling infra.

Incentivized

• .NET is heavily Microsoft Windows oriented, and while .NET core tried to resolve that with MacOS and Linux support, .NET Core is still waiting for wider adoption.
• While free for small projects, additional features for big projects can be a little expensive.
• Can be resource-heavy upon deployment. We continuously have our more senior staff optimize the code of our junior developers for performance. Other languages are a little bit more forgiving in comparison.

Incentivized

Usability is good since we already know how AWS works. For those that are new it might be a little bit confusing at the beginning but they are improving it at a fast pace. Even though AWS keeps changing the user interface constantly, it is still powerful, understandable and easy to use. For technical people, they still offer the CLI.

Incentivized

.NET frameworks are fantastic overall. There are no limitations to what you can accomplish with it. The most important part is that you'll have access to developer community support and that .NET is always being improved every month. Be it in web applications, back-end servers, or integrations, .NET enables developers to do it all.

Incentivized

The platform works as is. The help and tutorials on the help page can help you to setup the entire platform without problems, and also provides help on a huge variety of problems. Amazon also provides support plans. We have the basic support plan, but Amazon offers three support tiers, and we know that it works perfect.

Incentivized

As Microsoft Gold Partners, we do have access to a lot of additional information and support from Microsoft. Still, the availability of "open and free" documentation, community, and enthusiasts of the platform is vast. Added to that, the quality of resources provided for all the Microsoft ecosystem is very impressive.

Incentivized

The operating system, CPU, RAM, and storage may be constructed in any configuration and readily altered after the build. The most important factor is the "sense of security."Problems may arise once every several years, but there is a significant difference when discussing how to cope with hardware problems in the local age.

If it was up to me, I'd rather use something like Node.js hands down. Things are simpler, there is no gigantic convoluted class hierarchy to learn like there is with .NET. Also Node is really fast and lightweight. I find .NET these days to be a totally solid product and it certainly has its place - but it seems a bit dated and boring to me now.

Incentivized

• We will devote more time to development than server administration, but we will require additional time if you migrate from another ecosystem.
• Fault detection and reporting are automated in the old server, and bandwidth is fixed per month, but everything is manageable automatically. We only pay for the resources we use.
• After some months, we met our return on investment (ROI).

• We are slowly switching from a dying programming language to .NET because it was too expensive to hire developers for the old programming language. There are way more .NET developers around and an amazing community which has allowed us to keep our costs low.
• Our development time has been greatly reduced because now we're not developing applications for each OS platform. We do it once and deploy accordingly.
• .NET Core has been a big mindshift in terms of how to program. The learning curve has been quite high for existing .NET developers.

Incentivized