SLA for Service Fabric
SLA for Service Fabric reads thus:
The product documentation for most Azure services is clearly listed but the cost calculation for Service Fabric is not straight-forward. There is no charge for the Service Fabric service itself but the cost of creating the Service Fabric clusters has to be calculated on your own by finding out the resources required which typically include Virtual Machines, Storage, IP Addresses that you're going to use.
Questioning the production readiness of Service Fabric, a concerned SF explorer asked on the MSDN forum when SF will be ready for serious deployments.
Matt Snider, #AzureServiceFabric PM's reply in October 2016 -
Service Fabric is a free service, therefore, it does not have a financially backed SLA itself. The availability of your Service Fabric cluster is based on the SLA of the underlying virtual machines and storage resources used. Please see the Virtual Machine SLA and Storage SLA for more details.
The product documentation for most Azure services is clearly listed but the cost calculation for Service Fabric is not straight-forward. There is no charge for the Service Fabric service itself but the cost of creating the Service Fabric clusters has to be calculated on your own by finding out the resources required which typically include Virtual Machines, Storage, IP Addresses that you're going to use.
Questioning the production readiness of Service Fabric, a concerned SF explorer asked on the MSDN forum when SF will be ready for serious deployments.
Matt Snider, #AzureServiceFabric PM's reply in October 2016 -
SF is GAd both for our hosted offering in Azure as well as on premises for Windows Server. Regarding the SLA, we still do not have a specific SLA of our own because we can't do better than the general SLA of the environment/hardware that the cluster is running on top of.
Comments
Post a Comment