Company.ServiceFabric | minimalist template for building microservice architectures | Continuous Deployment library

by countincognito C# Version: Current License: BSD-2-Clause

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Company.ServiceFabric Summary

Company.ServiceFabric is a C# library typically used in Devops, Continuous Deployment, Docker applications. Company.ServiceFabric has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This a minimalist template for building microservice architectures, using the IDesign Method, in Service Fabric using .NET Core 2.0, a HTTPS RESTful public API, Stateless Services, Service Fabric Remoting V2, and Swagger. It is heavily influenced by code samples that can be downloaded from the IDesign website. It requires a local installation of Seq for logging, and a minimum of version 3.0.456 of the Service Fabric SDK and version 6.1.456 of the Service Fabric Runtime (Visual Studio 15.5.6). For further details see the Service Fabric 6.1 release notes. The Company.ServiceFabric.sln solution includes all component, framework and configuration projects. The Company.InProc.sln solution includes only the component interfaces and implementations - this is to demonstrate just one possible way of separating business code from plumbing in order to make development and testing easier. Be sure to update the apiCertThumbprint and the seqLocation parameters in the ApplicationManifest.xml configuration file with the appropriate values, and that all projects are set to compile to 64 bit. The local certificate installed by IIS should be fine for the API certificate.

Support

Quality

Security

License

Reuse

Support

Company.ServiceFabric has a low active ecosystem.

It has 10 star(s) with 3 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

Company.ServiceFabric has no issues reported. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Company.ServiceFabric is current.

Quality

Company.ServiceFabric has 0 bugs and 0 code smells.

Security

Company.ServiceFabric has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Company.ServiceFabric code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Company.ServiceFabric is licensed under the BSD-2-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

Company.ServiceFabric releases are not available. You will need to build from source code and install.

It has 246 lines of code, 0 functions and 57 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Company.ServiceFabric

Get all kandi verified functions for this library.

Company.ServiceFabric Key Features

No Key Features are available at this moment for Company.ServiceFabric.

Company.ServiceFabric Examples and Code Snippets

No Code Snippets are available at this moment for Company.ServiceFabric.

Community Discussions

Trending Discussions on Company.ServiceFabric

FabricTransientException during load test "Could not ping any of the provided Service Fabric gateway endpoints."

QUESTION

FabricTransientException during load test "Could not ping any of the provided Service Fabric gateway endpoints."

Asked 2017-Nov-14 at 16:35

We have a class that broadcasts messages to a Service Fabric stateless service. This stateless service has a single partition, but with many replica's. The message should be send to all the replica's in the system. Therefore we query the FabricClient for the single partition, and all the replica's of that partition. We use standard HTTP communication (the stateless service has Communication Listener with a selfhosted OWIN listener, using WebListener/HttpSys) with a shared HttpClient instance. During a load test, we get many errors during the sending of messages. Note that we have other services in the same application, also communicating (WebListener/HttpSys, ServiceProxy, and ActorProxy).

The code where we see Exceptions is (stacktrace is below the code sample):

...

ANSWER

Answered 2017-Oct-19 at 05:31

It would seem you have a port exhaustion problem. Provided that is the case then Either you have to figure out how to reuse your connections, or you will have to implement some sort of throttling mechanism so you don't use up all the available ports.

Not sure how the fabric client behaves, it might be that it is responsible for the exhaustion, or perhaps its the SQL Server part that we cannot see the code for (but since you posted it in a log I assume its probably unrelated to your ping test).

Looking at the referencesource for httpwebresponse (https://github.com/Microsoft/referencesource/blob/master/System/net/System/Net/HttpWebResponse.cs) it might also be that disposing the response (i.e. your using statement for postasync) is closing the HttpClients connection. Meaning you are not reusing the connection but opening new ones all the time.

I would guess that testing a variant that does not dispose your httpwebresponse is a rather easy thing.

Source https://stackoverflow.com/questions/46809825

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Company.ServiceFabric

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: