It depends heavily on the domain. For B2B operations tooling, the real question isn't which stack to build with — it's which ecosystem your customers are already locked into.
If your target users live in Microsoft 365 + Azure AD, the integration advantages of the MS stack are hard to ignore regardless of technical preference. Same goes for teams deep in the Google Workspace or Atlassian ecosystem.
For our greenfield project we went with Kotlin/Spring + Next.js on the basis that most of our target customers use Jira+Confluence, so Atlassian ecosystem familiarity mattered more than stack choice itself.
Comments
It depends heavily on the domain. For B2B operations tooling, the real question isn't which stack to build with — it's which ecosystem your customers are already locked into.
If your target users live in Microsoft 365 + Azure AD, the integration advantages of the MS stack are hard to ignore regardless of technical preference. Same goes for teams deep in the Google Workspace or Atlassian ecosystem.
For our greenfield project we went with Kotlin/Spring + Next.js on the basis that most of our target customers use Jira+Confluence, so Atlassian ecosystem familiarity mattered more than stack choice itself.