<commit_before># HTTP Gateway for Azure Service Fabric services
This project contains an ASP.NET 5 middleware which can be used 
as a public gateway to your internal HTTP based Service Fabric services.

## Introduction

[Azure Service Fabric](https://azure.microsoft.com/en-us/services/service-fabric/)
is a cluster platform for hosting service-oriented applications.
It contains a feature-rich orchestration platform which allows you to configure
on how many nodes your services should run. If a node goes down or if 
Service Fabric has to reconfigure the service placements, your services are 
moved to other nodes automatically. Due to this dynamic nature, the cluster 
also contains a "naming service" which gives you an actual address for a service. 

Calling this naming service is fine if your code runs inside the cluster
as well. If you are using the default communication stacks or WCF for your
services then you can even use the built-in classes from the SDK 
(e.g. `ServiceProxy`) which makes this process transparent.

However if you want to access your services from a computer which is 
not part of the cluster you usually communicate with the cluster through 
a load balancer. If you set up a Service Fabric cluster in Microsoft Azure
this is automatically configured for you.<commit_msg>image to AppVeyor build status<commit_after># HTTP Gateway for Azure Service Fabric services

This project contains an ASP.NET 5 middleware which can be used 
as a public gateway to your internal HTTP based Service Fabric services.

https://ci.appveyor.com/api/projects/status/github/gruntjs/grunt?branch=master&svg=true

[![Build status](https://ci.appveyor.com/api/projects/status/glormo3hm3wsdwm4/branch/master?svg=true)](https://ci.appveyor.com/project/cwe1ss/servicefabric-httpservicegateway/branch/master)

## Introduction

[Azure Service Fabric](https://azure.microsoft.com/en-us/services/service-fabric/)
is a cluster platform for hosting service-oriented applications.
It contains a feature-rich orchestration platform which allows you to configure
on how many nodes your services should run. If a node goes down or if 
Service Fabric has to reconfigure the service placements, your services are 
moved to other nodes automatically. Due to this dynamic nature, the cluster 
also contains a "naming service" which gives you an actual address for a service. 

Calling this naming service is fine if your code runs inside the cluster
as well. If you are using the default communication stacks or WCF for your
services then you can even use the built-in classes from the SDK 
(e.g. `ServiceProxy`) which makes this process transparent.

However if you want to access your services from a computer which is 
not part of the cluster you usually communicate with the cluster through 
a load balancer. If you set up a Service Fabric cluster in Microsoft Azure
this is automatically configured for you.
{'fraction_non_alphanumeric': 0.04679972470750172, 'fraction_numerical': 0.0020646937370956643, 'mean_word_length': 4.711198428290766, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 5, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4950481', 'n_tokens_mistral': 731, 'n_tokens_neox': 706, 'n_words': 400}