0
ptaylor created
Dear Team,
Type - ASP.NET Core & Angular(Separate) Version - 13.3.0
We have been deploying the product in IIS and Azure App Services from a long time wherein Angular and API are deployed in two websites/azure app services and database is in a separate SQL server or Azure SQL Database. The team is planning to move to containerization deployment. We followed your document https://docs.aspnetzero.com/aspnet-core-angular/latest/Deployment-Angular-Docker to try out the deployment and were able to deploy the app in three containers, one for angular/web server, one for API/backend and one for SQL Server Database. There are few queries related to this before moving forward with staging and production.
- Can we have a single container with all three components(web server, API and Database)? If yes, what are pros and cons compared to three separate containers?
- We expected a better performance in containerization deployment but after testing we found its not better than IIS deployment. Both machines are of same configuration and in the same location with only difference being Operating System. Is this something due to the product architecture or in the way how containerization is deployed?
- What are other problems we would face in production if we have containerization deployment using Kubernetes? As per documentation moving to distributed cache Redis and using Hangfire for background jobs is mentioned. Are there any other changes we need to do in the application code?
Regards
1 Answer(s)
-
0
Hi @ptaylor,
- I think this is possible, see https://forums.docker.com/t/multiple-applications-in-a-single-container/54772. But I think this is not suggested.
- We don't have a special architecture about this. This might be because of the delay of communication between containers.
- You might face problems with SignalR if you run multiple pods of the web app. You can take a look at https://docs.aspnetzero.com/aspnet-core-angular/latest/Clustered-Environment for this one.
