Need advice about which tool to choose?Ask the StackShare community!

Azure Service Fabric

101
283
+ 1
26
Kong

622
1.5K
+ 1
139
Add tool

Azure Service Fabric vs Kong: What are the differences?

Developers describe Azure Service Fabric as "Distributed systems platform that simplifies build, package, deploy, and management of scalable microservices apps". Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices. Service Fabric addresses the significant challenges in developing and managing cloud apps. On the other hand, Kong is detailed as "Open Source Microservice & API Management Layer". Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.

Azure Service Fabric and Kong can be primarily classified as "Microservices" tools.

Some of the features offered by Azure Service Fabric are:

  • Simplify microservices development and application lifecycle management
  • Reliably scale and orchestrate containers and microservices
  • Data-aware platform for low-latency, high-throughput workloads with stateful containers or microservices

On the other hand, Kong provides the following key features:

  • Logging: Log requests and responses to your system over TCP, UDP or to disk
  • OAuth2.0: Add easily an OAuth2.0 authentication to your APIs
  • Monitoring: Live monitoring provides key load and performance server metrics

Azure Service Fabric and Kong are both open source tools. It seems that Kong with 22.4K GitHub stars and 2.75K forks on GitHub has more adoption than Azure Service Fabric with 2.57K GitHub stars and 304 GitHub forks.

Checkr, Policygenius, and Cuemby are some of the popular companies that use Kong, whereas Azure Service Fabric is used by Starbucks, OneWire, and eVestor. Kong has a broader approval, being mentioned in 50 company stacks & 15 developers stacks; compared to Azure Service Fabric, which is listed in 6 company stacks and 3 developer stacks.

Decisions about Azure Service Fabric and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 288.5K views

Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Azure Service Fabric
Pros of Kong
  • 5
    Intelligent, fast, reliable
  • 4
    Runs most of Azure core services
  • 3
    Reliability
  • 3
    Superior programming models
  • 3
    More reliable than Kubernetes
  • 3
    Open source
  • 2
    Quickest recovery and healing in the world
  • 1
    Deploy anywhere
  • 1
    Is data storage technology
  • 1
    Battle hardened in Azure > 10 Years
  • 37
    Easy to maintain
  • 32
    Easy to install
  • 26
    Flexible
  • 21
    Great performance
  • 7
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Security
  • 2
    Has a good plugin infrastructure
  • 2
    Agnostic
  • 1
    Load balancing
  • 1
    Documentation is clear
  • 1
    Very customizable

Sign up to add or upvote prosMake informed product decisions

What is Azure Service Fabric?

Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices. Service Fabric addresses the significant challenges in developing and managing cloud apps.

What is Kong?

Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Azure Service Fabric?
What companies use Kong?
See which teams inside your own company are using Azure Service Fabric or Kong.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Azure Service Fabric?
What tools integrate with Kong?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

GitHubPythonNode.js+26
29
15941
What are some alternatives to Azure Service Fabric and Kong?
Docker
The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
Kubernetes
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
Azure Container Service
Azure Container Service optimizes the configuration of popular open source tools and technologies specifically for Azure. You get an open solution that offers portability for both your containers and your application configuration. You select the size, the number of hosts, and choice of orchestrator tools, and Container Service handles everything else.
AWS Lambda
AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
Azure App Service
Quickly build, deploy, and scale web apps created with popular frameworks .NET, .NET Core, Node.js, Java, PHP, Ruby, or Python, in containers or running on any operating system. Meet rigorous, enterprise-grade performance, security, and compliance requirements by using the fully managed platform for your operational and monitoring tasks.
See all alternatives