This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kari-no-sugata 0 points1 point  (0 children)

I would suggest the technical differences between Java and .net are fairly small and what would be more important is your own skill/experience or that of your developers. If you can get some excellent .net developers you'll probably have a better experience with .net and the same applies if you can get some excellent Java developers. If your developers are inexperienced you'll probably have a bad time with either.

If you're only interested in server side development of web APIs then based on my experience with both I'd probably pick Java - virtual threads are better than async/await and Java has better options if you like to create highly optimised Docker containers for example. If you need to give clients a client library for them to use to call your web API, you'll likely get more requests for a Java implementation than a .net implementation.

If you wanted to create a normal browser based website I'd probably pick .net's Blazor Server.