Azure Service Fabric vs Kong

Overview

Kong

Stacks671

Followers1.5K

Votes139

GitHub Stars42.1K

Forks5.0K

Azure Service Fabric

Stacks103

Followers284

Votes26

GitHub Stars3.0K

Forks399

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.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Kong, Azure Service Fabric

Prateek

Mar 14, 2020

Decided

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.

322k views322k

Comments

Detailed Comparison

Kong	Azure Service Fabric
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 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.
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; IP-restriction: Whitelist or blacklist IPs that can make requests; Authentication: Manage consumer credentials query string and header tokens; Rate-limiting: Block and throttle requests based on IP or authentication; Transformations: Add, remove or manipulate HTTP params and headers on-the-fly; CORS: Enable cross-origin requests to your APIs that would otherwise be blocked; Anything: Need custom functionality? Extend Kong with your own Lua plugins;	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; Run anything – your choice of languages and programming models; Run anywhere – supports Windows/Linux in Azure, on-premises, or other clouds; Scales up to thousands of machines
Statistics
GitHub Stars 42.1K	GitHub Stars 3.0K
GitHub Forks 5.0K	GitHub Forks 399
Stacks 671	Stacks 103
Followers 1.5K	Followers 284
Votes 139	Votes 26
Pros & Cons
Pros 37 Easy to maintain 32 Easy to install 26 Flexible 21 Great performance 7 Api blueprint	Pros 5 Intelligent, fast, reliable 4 Runs most of Azure core services 3 Superior programming models 3 Open source 3 More reliable than Kubernetes
Integrations
Cassandra Docker Prometheus Kubernetes PostgreSQL NGINX Vagrant	No integrations available

What are some alternatives to Kong, Azure Service Fabric?

Istio

Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.

Amazon API Gateway

Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management.

Tyk Cloud

Tyk is a leading Open Source API Gateway and Management Platform, featuring an API gateway, analytics, developer portal and dashboard. We power billions of transactions for thousands of innovative organisations.

Moleculer

It is a fault tolerant framework. It has built-in load balancer, circuit breaker, retries, timeout and bulkhead features. It is open source and free of charge project.

Express Gateway

A cloud-native microservices gateway completely configurable and extensible through JavaScript/Node.js built for ALL platforms and languages. Enterprise features are FREE thanks to the power of 3K+ ExpressJS battle hardened modules.

ArangoDB Foxx

It is a JavaScript framework for writing data-centric HTTP microservices that run directly inside of ArangoDB.

Dapr

It is a portable, event-driven runtime that makes it easy for developers to build resilient, stateless and stateful microservices that run on the cloud and edge and embraces the diversity of languages and developer frameworks.

Zuul

It is the front door for all requests from devices and websites to the backend of the Netflix streaming application. As an edge service application, It is built to enable dynamic routing, monitoring, resiliency, and security. Routing is an integral part of a microservice architecture.

linkerd

linkerd is an out-of-process network stack for microservices. It functions as a transparent RPC proxy, handling everything needed to make inter-service RPC safe and sane--including load-balancing, service discovery, instrumentation, and routing.

Jersey

It is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. It provides it’s own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development.

Related Comparisons

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 vs Kong