Java/Spring MVC vs C#/ASP.NET CORE: Which one should I learn as a Full Stack developer?

Both is very good technologies.It depend on you what is your background.If you are from Java then moved to Java/Spring MVC and also include Angular/React .Java resources is highly payable but only problem is that less market opening. But for c#/Asp.net core less payable as compared to java but opening in the market good as compared to java. read less

Hm. Interesting question! I, personally, would recommend C# and ASP.NET Core, (what the heck, why is that link there?) but I think it would be beneficial to lay out the pros and cons for both. Keep in mind that I have almost no experience with Spring and only minimal experience with .NET. In any case, here goes: Java/Spring MVC Pros: Respected in the business Widespread Constrained coding style might lead to easier to read code Cons: Verbose, both with the language and framework XML configuration is required Java is an ugly language, besides being verbose, especially its common coding style Does not have as good support for threading and asynchrony as C# has with async/await C#/ASP.NET Pros: Async-oriented Promises Faster to code in (more/better functional features, more well thought out) Better generics LINQ Better documentation Better IDE integration Quicker to get things up and running in Better configuration setup Able to be component oriented as well as MVC Nicer concept of MVC Nicer coding standards Availability of other programming styles than OOP, including functional. More low-level constructs allowing optimization Cons: Newer, slightly buggy Not as battle-tested as Java Heavy IDE (although you can use Visual Studio Code, too) What it all comes down too, I think, is what your using it for. If your company is already on the Microsoft stack, use ASP.NET. If they already use Java, go the Spring route. If your starting fresh, look around you: if the programmers appreciate functional concepts and won’t write Java in C#, then go the ASP.NET route. There isn’t any one-size-fits-all strategy read less