@Ganesh Patil Thanks for reaching out.
It's a good practice to maintain separate repositories for your Azure Functions and your Azure Service Fabric services. This allows you to manage the code for each component separately and deploy them independently.
By maintaining separate repositories, you can also enforce different release cycles for your Azure Functions and your Azure Service Fabric services. For example, you can deploy your Azure Service Fabric services every week, while deploying your Azure Functions only when necessary.
As for best practices, Microsoft recommends using a separate repository for each Azure Function app. This allows you to manage the code for each function app separately and deploy them independently. You can also use a separate repository for each Azure Service Fabric application, which contains one or more services.
In addition, Microsoft recommends using a continuous integration and continuous deployment (CI/CD) pipeline to automate the deployment of your Azure Functions and Azure Service Fabric services. This allows you to test and deploy your code quickly and reliably.
You can find more information on best practices for Azure Functions and Azure Service Fabric on the Microsoft documentation website. Here are some links to get you started:
- Best practices for Azure Functions: https://docs.microsoft.com/en-us/azure/azure-functions/functions-best-practices
- Best practices for Azure Service Fabric: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-best-practices-overview