Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
MIT License
82
stars
11
forks
source link
Suggestions for local and production deployment including an Azure Web App #340
I have an ASP.NET Core web application and a couple of microservices, that communicate over HTTP and Azure Service Bus. Locally, I run everything using docker-compose, so they communicate over a bridge network.
In production, the web app gets deployed as an Azure Webapps for Containers application, and the microservices just run as containers on a VM and they all communicate over public IP's, which is what I want to get away from, and SF Mesh sounds like it could be a solution.
How would I translate my current setup into SF Mesh? I would still very much like to keep the public webapp as an Azure Webapp because of all the stuff you get for free like deployment slots and stuff.
Hi
I have an ASP.NET Core web application and a couple of microservices, that communicate over HTTP and Azure Service Bus. Locally, I run everything using docker-compose, so they communicate over a bridge network.
In production, the web app gets deployed as an Azure Webapps for Containers application, and the microservices just run as containers on a VM and they all communicate over public IP's, which is what I want to get away from, and SF Mesh sounds like it could be a solution.
How would I translate my current setup into SF Mesh? I would still very much like to keep the public webapp as an Azure Webapp because of all the stuff you get for free like deployment slots and stuff.
Thanks for any advice