简体   繁体   English

带有ApplicationGateway的Azure服务结构

[英]Azure service fabric with ApplicationGateway

i have Service fabric Cluster Running on Azure ,i have deployed Application to Service Fabric. 我已在Azure上运行Service Fabric群集,已将应用程序部署到Service Fabric。

Now i want to use azure Application Gateway on this Scenario like Request First served to Application Gateway and then it migrated to Fabric Load Ba-lancer. 现在,我想在这种情况下使用azure应用程序网关,例如“请求首先服务到应用程序网关”,然后将其迁移到Fabric Load Ba-lancer。 I am Quite Confused on this.How to meet above Challenges with ApplicationGateway 我对此很困惑。如何使用ApplicationGateway应对上述挑战

I also able to configure ApplicationGateway but dont have IDea how to use it for service fabric 我也能够配置ApplicationGateway,但是没有IDea如何将其用于服务结构

Microsoft Azure Application Gateway offers layer 7 load balancing capabilities, SSL offloading, layer-7 routeing, cookie based session affinity, URL routeing and able to host multiple web application. Microsoft Azure应用程序网关提供第7层负载平衡功能,SSL卸载,第7层路由,基于cookie的会话亲和力,URL路由,并能够承载多个Web应用程序。 Azure Application Gateway requires its subnet; Azure应用程序网关需要其子网; sometimes it is confusing if you are not familiar with Azure VNet and Subnet segmentation. 如果您不熟悉Azure VNet和子网分段,有时会造成混淆。

First what you need to understand is the architecture pattern, how Microsoft Application Gateway would play a part in. 首先,您需要了解的是架构模式,Microsoft Application Gateway将如何参与其中。

I have written some detail series documenting my journey throughout Azure ServiceFabric. 我写了一些详细的系列文章,记录了我在整个Azure ServiceFabric中的经历。

I would suggest you go through these posts, and it will explain Architecture viewpoint for having Application Gateway in front of Service Fabric Cluster. 我建议您阅读这些文章,它将解释在Service Fabric群集前面使用Application Gateway的体系结构观点。

Irrespective of Application Gateway, you would need Internal Loadbalancer or External Loadbalancer (depends on your topology). 不管应用程序网关如何,您都需要内部负载均衡器或外部负载均衡器(取决于您的拓扑)。

  1. Cloud Architecture Pattern: Azure Service Fabric and Microservices - Part 1 (Physical Architecture) 云体系结构模式:Azure服务结构和微服务-第1部分(物理体系结构)

  2. Also try to understand how it is going to impact, security architecture of your implementation 还要尝试了解它会对实施的安全架构产生怎样的影响

Also, I would recommend you Reverse proxy in Azure Service Fabric . 另外,我建议您在Azure Service Fabric中使用反向代理

Not fully sure your meaning, but you could create sf cluster and related resources using ARM teplates. 不能完全确定您的意思,但是可以使用ARM teplate创建SF群集和相关资源。 Thats what I have done. 那就是我所做的。 I created appgw, cluster, vmss etc. In the virtualMachinesScalesets networkProfile you must configure the ApplicationGateway back endAddress pool instead of configuring loadBalancerBackendAddressPools. 我创建了appgw,cluster,vmss等。在virtualMachinesScalesets networkProfile中,您必须配置ApplicationGateway后端地址池,而不是配置loadBalancerBackendAddressPools。 The appgw must exist before vmss deployment. 在部署vmss之前,必须存在appgw。 You don't necessarily need lb at all. 您根本不需要磅。 Appgw can handle the load balancing for you. Appgw可以为您处理负载平衡。 Even though internal lb would bring in some nice additional features, which you could utilize later on... 即使内部lb会带来一些不错的附加功能,您以后也可以使用...

I have to admit that these things are quite poorly documented... 我不得不承认这些东西没有被很好地记载。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM