What are the actual downsides of using Aspire in prod, being aware it isn't supposed to be?
The company I'm working at has a product that is starting to grow and the project manager suggested making a small demo with Aspire to check out the benefits for us.
We finished up a demo (more like a lite version of the product, with very toned down features) and he asked me what the issues would be if we were to just use Aspire to orchestrate everything rather than deploying to something like kubernetes since everything was working well. I couldn't really answer that question since everything Aspire related is pretty new to me as well
So the main question is as stated in title, what are the downsides of doing it?
5 Replies
Are you deploying to azure?
As of right now no, we have a deal with a local provider and chances are that we aren't moving to azure either since it's cheaper
That's not a problem
How do you deploy today?
We have a CI/CD pipeline to build and publish the solution to our host provider via SSH
It consists of a monolithic ASP NET API with a Blazor frontend
We just publish the binaries and the server runs the services with nginx routing them to the API and frontend
sounds like you're good to go
perhaps the only thing to be aware of is the configuration required to make the client integrations work