在服务结构应用程序中动态创建服务

问题描述

这有点描述性，请耐心等待. :)

在我要构建的应用程序中，产品具有独特的功能.用户可以选择加入功能A，B，D，但不能选择加入C.我构建此功能的方式是，每个独特的功能都是服务(无状态，我正在考虑将数据存储在Azure SQL中数据库，并从每个服务公开REST API).将所有服务捆绑在一起是一个ApplicationType.对于正在创建的每个客户租户(将其视为一组用户的共享帐户)，我正在考虑使用TenantManagementService创建一个新的已注册ApplicationType的具体实例，并在FabricClient实例上调用client.ApplicationManager.CreateApplicationAsync()我可以在该租户的节点上运行一个专用的应用程序实例.但是，正如我所提到的，租户可以选择仅选择加入映射到服务子集的特定功能.如果租户仅选择我的应用程序的服务A，则对应于功能B，C，D的其余服务实例不应在节点上空闲运行.

我曾考虑为每个服务创建参与者，但是我正在创建的服务是无状态的，我想让它们的多个实例主动在多个节点上运行以实现负载平衡，而不是拥有状态服务的空闲副本./p>

类似于我对应用程序类型所做的操作，即将应用程序类型作为新的租户注册生成，当租户希望选择加入/退出产品功能时，我可以生成/删除服务吗?

这是我尝试过的:打包我的应用程序时，我尝试将服务的InstanceCount设置为0.在我的ApplicationParameters XML文件中:

<Parameters>
    <Parameter Name="FeatureAService_InstanceCount" Value="0" />
    <Parameter Name="FeatureBService_InstanceCount" Value="0" />
</Parameters>

但是，从此类应用程序类型实例化应用程序时，Service Fabric资源管理器会启动.错误是这样的:

但是，另一方面，当在结构上部署服务时，它为我提供了一个删除它的选项，因此这种情况应该是有效的.

欢迎提出任何建议！

我的要求类似于在这里的anderso提到的方法- https://stackoverflow.com/a/35248349/1842699 ，但是，我要特别解决的问题是，使用一个或多个实例计数为零的打包服务上载创建应用程序实例！

解决方案

@uplnCloud

我希望我没事.

您的情况如下:

• 每个客户应该有一个单独的应用程序(从相同的ApplicationType创建).
• 每个客户应仅拥有服务的子集(在ApplicationType中定义).

如果我做对了，那么开箱即用即可.

首先，您应该从ApplicationManifest.xml中删除<DefaultServices />部分.这将指示Service Fabric不要使用该应用程序自动创建服务.

现在，算法如下:

1. 使用FabricClient.ApplicationManager.CreateApplicationAsync()
创建应用
2. 使用FabricClient.ServiceManager.CreateServiceAsync()为每个必需功能创建一个新的对应服务(您需要指定新创建的应用程序的应用程序名称)

还请注意，CreateServiceAsync()接受 ServiceDescriptor ，您可以配置所有与服务相关的参数-从分区模式开始，以实例数结束.

This is a bit descriptive so please bear with me. :)

In the application that I'm trying to build, there are distinct functionalities of product. Users can choose to opt-in for functionality A, B, D but not C. The way I'm building this, is that each of the distinct functionality is a Service (stateless, I'm thinking of storing the data in Azure SQL DBs and exposing REST APIs from each service). Bundled all services together is an ApplicationType. For each customer tenant (consider this as an shared account of a group of users) that is created, I'm thinking of creating a new concrete instance of registered ApplicationType using a TenantManagementService and calling client.ApplicationManager.CreateApplicationAsync() on a FabricClient instance so that I can have a dedicated application instance running on my nodes for that tenant. However, as I mentioned, a tenant can choose to opt-in only for specific functionality which is mapped to a subset of services. If a tenant chooses only service A of my Application, rest of the service instances corresponding to features B, C, D shouldn't be idly running on the nodes.

I thought of creating actors for each service, but the services I'm creating are stateless and I'd like to have multiple instances of them actively running on multiple nodes to load balance rather than having idle replicas of stateful services.

Similar to what I'm doing with application types, i.e., spawning application types as a new tenant registers, can I spawn/delete services as and when a tenant wants to opt-in/out of product features?

Here's what I've tried:I tried setting InstanceCount 0 for the services at when packaging my application. In my ApplicationParameters XML files:

<Parameters>
    <Parameter Name="FeatureAService_InstanceCount" Value="0" />
    <Parameter Name="FeatureBService_InstanceCount" Value="0" />
</Parameters>

However, Service Fabric Explorer cribs when instantiating the application out of such application type. The error is this:

But on the other hand, when a service is deployed on the fabric, it gives me an option to delete it specifically, so this scenario should be valid.

Any suggestions are welcome!

EDIT: My requirement is similar to the approach mentioned by anderso in here - https://stackoverflow.com/a/35248349/1842699, However, the problem that I'm specifically trying to solve is to upload create an application instance with one or more packaged services having zero instance count!

解决方案

@uplnCloud

I hope I understand everything right.

Your situation is the following:

• Each customer should have separate Application (created from the same ApplicationType).
• Each customer should have only subset of Services (defined in ApplicationType).

If I get it right then this is supported out of the box.

First of all you should remove <DefaultServices /> section from the ApplicationManifest.xml. This will instruct Service Fabric to don't create services automatically with the application.

Now the algorithm is the following:

1. Create application using FabricClient.ApplicationManager.CreateApplicationAsync()
2. For each required feature create a new corresponding Service using FabricClient.ServiceManager.CreateServiceAsync() (you need to specify the Application name of newly created Application)

Also note that CreateServiceAsync() accepts ServiceDescriptor that you can configure all service related parameters - starting from partitioning schema and ending up with instance count.

这篇关于在服务结构应用程序中动态创建服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！