Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

Azure Service Fabric Mesh preview

Sign in to queue

The Discussion

  • User profile image
    csinger

    Can you speak more about the CPU and RAM numbers in the template?  One of the nice things about the original Service Fabric is that you had nodes with sized to the VM that you picked and you could fill it with as many services as you wanted until the resources were used up at which point you could spin up another node and the services would level themselves out across nodes.

    If I don't know how much Memory or CPU a service might use how does one go about selecting the right size.  For example, say I pick 1GB as shown in the example but the service only uses 10MB, am I charged for the 10MB per second or the 1GB?  Same for the CPU's...

    When you said you didn't have to think about infrastructure, I figured I wouldn't have to think about it at all.  

    Perhaps these are upper limits so a leaking service doesn't bankrupt the owner of the service?

  • User profile image
    richard004

    SF Mesh sounds really exciting.

    On minute 5:18 you both guys are referring to some older video about how the bouncing pyramid application was done, if I got it right.

    Can you please provide a link to the original video?

    I struggle to find it in the AF history.

  • User profile image
    robcaron
  • User profile image
    chackod

    @csinger: The CPU and Mem indicate to the system the size of the container that the code package needs to run. SF mesh allows you partial cores, so if need only .5 Cores and .5 GB of memory, then you request only for that. The customer gets charged for what they request. After deploying, if you observe that your service needs more cores or memory you can scale up or down, by adjusting that the values or if you need more service (container) instances your scale out or in by adjusting the replica count for that service. What you do not need to worry about is the provisioning the azure capacity to scale up or out, system does that for you.

    Later in the year, you can also specify custom autoscale rules for your services, so that you can scale in or out as the load decreases or increases upto a limit that you set. 

     

     

     

  • User profile image
    ed123456

    Can you please discuss migrating applications between Service Fabric Mesh and Service Fabric?

    Can an existing Service Fabric application be wrapped in a container and deployed straight into Mesh? Also if an application is built on Mesh, but we decide we would rather manage the cluster ourselves, how challenging is it to move from Mesh to regular Service Fabric?

  • User profile image
    chackod

    @ed123456: SF Mesh in azure , being a multitenant offering  , the services are not allowed direct access to the Nodes and also in general cannot query the system services directly.  So if your services were making any such calls, then containerizing them and pushing them into Mesh would most likely break them.

    To provide the capability to move your existing SF apps to SF Mesh is something we plan to support in the future, closer to GA timeframe. This is an important capability for us and is in the near term backlog.

    All mesh applications can be deployed to a SF cluster. The main challenge for anyone moving a mesh application running in Mesh to a SF cluster, would be to move the state, it will have to be backed up and restored to the cluster.. If the state is external, then movement would be trivial. The resource model is understood by both mesh and SF cluster. So porting the applications back and forth would not be an issue.

Add Your 2 Cents