| Sure! Because of my background in .NET, it made sense to stick with what I know. I don't believe the tech stack makes or breaks a product (unless you choose egregiously poorly). A product's success is primarily determined by how well you hit product market fit. That being said, a good stack that you know well can affect how quickly you build and how quickly you can adapt the product to changing market conditions. So here's what we use: - ASP.NET CORE( - Primarily ASP.NET Razor Pages for the web app. ASP.NET MVC Controllers for the internal and external APIs we support. - C# - We try to stay on the latest version. The recent pattern matching improvements alone make our code so much cleaner. - [HTMX](https://htmx.org/)\* - for front-end. We're not at the point where we feel we need a heavyweight front-end framework like React. We like the 37signals approach of shipping "HTML over the wire". We're also big on Web Components. That's a result of our [GitHub heritage](https://github.blog/2021-05-04-how-we-use-web-components-at-...). - TypeScript - for our front-end JS. This is a recent addition. Most of our JS is still ES6. - Azure Database for PostgreSql - PostgreSql is rock solid and great for storing all kinds of data. - Azure Functions - we support three types of custom code skills that customers can use to enhance and customize the bot : JavaScript, C#, and Python. We run these in Azure Functions. - App Insights - We use this for logging. - Azure Managed Grafana - We have a nice Grafana dashboard based off our App Insights logs that helps us get a birds-eye view of how everything is doing. - Azure App Configuration - For feature flags. As you can see, it's pretty heavily Microsoft based. Part of that is my background. The other part is we got a lot of Azure Credits when we joined the [Microsoft for Startups](https://www.microsoft.com/en-us/startups?rtc=1) program. So it made fiscal sense for us to stick with Azure. I do like that we can manage everything in a single portal. But some of these tools are not best-in-breed as we will be looking at other options down the road. |
Wow, Microsoft must have really drowned you with free credits to choose Azure. We also tried Azure 2.5 years ago when my small team (3 founding devs) started with our startup, but after 6 months of constant problems, broken services, outages, and completely out of the blue unexplained service failures we had to give up. We wasted a lot of engineering time on bending our app to Azure's needs and still had issues. We eventually migrated to Google Cloud and hadn't had any problems since then. I am not kidding, the first 6 months we must have spent at least 70% of our time on issues which we wouldn't have had on AWS or Google. Azure really under delivered on all fronts. Things looked extremely promising and then when we used a service we realised that most useful (often necessary) features were behind extremely expensive tiers and then it meant we had to either take huge hits on our hosting costs or build weird workarounds. We didn't want to go against Azure and often chose to pay, but even the higher tiered services then started to act up and often result in totally unexpected behaviour. Good luck to you though!