If you ever scale up, you might find it difficult for recruiting for that stack, ironically
> The main application uses React with Tailwind on the frontend, C# on the backend
I'm curious what about your experience gave you that stack? I'm sure it works fine, but the "not JS backend" people are usually stuck in older frontend frameworks, and the JS everything world has Next.js and various things to power both the frontend and backend together
Both C# (ASP.NET Core) and React consistently rank pretty high up in the Stack Overflow Developer Survey frameworks section, with both being in the top 5 for 2023 [0].
Have you ever heard of "making people learn tools"? Not every job has to be the cookie-cutter node/react stack... you can also train people to use your stack.
It was a mix of what I already knew (.NET) and what I wanted to learn (React). I love C# as a language and it works just fine with whatever frontend you throw at it (it's just an API after all). I wouldn't touch a Microsoft frontend framework with a ten-foot pole.
> The main application uses React with Tailwind on the frontend, C# on the backend
I'm curious what about your experience gave you that stack? I'm sure it works fine, but the "not JS backend" people are usually stuck in older frontend frameworks, and the JS everything world has Next.js and various things to power both the frontend and backend together