VERY EXPERIENCED C# Programmer needed

Unfortunately, I'm working on similar goals on a very different timeline.

When you say a Unity3D game, I assume you mean something that is actually 3D and has some action, like a FPS or Third Person whatever/etc..? So that's the angle this response takes. If you are going for something turn based, or otherwise not "real-time", then some of these points probably shouldn't concern you much.

Some notes on your proposed setup:

SQL Server: (Unless you have some super killer hardware..)Great for storage, not the best for looking up/changing data repeatedly at high frequency, even when cached. Focus on using that to store information that is infrequently changed, like login details and high scores, player stats, etc.. mostly static information that won't be changing every frame of the game. Also, I wouldn't expose the SQL server directly to your clients at all. It's just too risky and it probably won't provide you any performance benefits. Any Database access should come via the Server Code directly, and the parts that the client needs to know should be relayed to the client by the server.

Windows Server is fine for hosting a game server, especially if it's written to run on Windows.

The usefulness of a web services/api layer for a game server database is mostly in the realm of public access to data, like public scoreboards on your games website and things like that. You probably won't get effective access to data at 3D game speeds from a web service, plus it's just more surface area to hack. If people like your game, it will happen.

Look at writing, or better yet, incorporating an existing UDP(faster) or TCP(slower but more reliable by nature) networking code solution into your client and server directly. This will give you the best performance when it comes to communicating data at high frequencies.

Anyhow, just some pointers, take what you want from them. Hope they help out.

Thank you, I appreciate your feedback. Unfortunately, my Killer hardware is the hardware that aws has allowed me to use on the free tier (until I can get a game that could bring in some income and afford the better/faster shit). However, I'm just looking for the experience... right now. There may be up to 10 people playing this to test it.

Also, just wanted to add a few things.
My client application doesn't have knowledge of the db. That's what the web services/api is for. The client sends a user login request to the api endpoint. The api handles the login and sends a response back to the client.

I was thinking about using SQL because I don't believe the db will be queried too often. Think of like a game of pong. The game server will handle the match between the two players, after the game is over, the server will send the result of the match to the api. Api stores the stats and updates player data.

I should have mentioned that I'm not trying to build a WoW clone. Just a little something to get some experience in building a game server.

However, now that you bring up the sql thing, what would you recommend if I needed something faster? Would a node sever and mongoDB suffice? If not, give me an idea of what you think would work for something like an mmorpg.

Again, Thanks for the tips.

You should be well taken care of with that setup then.

I'll message you some more info.