Get Advice Icon

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

Kong
Kong

208
255
+ 1
90
seneca
seneca

27
29
+ 1
0
Add tool

Kong vs seneca: What are the differences?

Kong: 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; seneca: A Micro-Services toolkit for Node.js. Seneca is a toolkit for organizing the business logic of your app. You can break down your app into "stuff that happens", rather than focusing on data models or managing dependencies.

Kong and seneca belong to "Microservices Tools" category of the tech stack.

Some of the features offered by Kong are:

  • 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

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

  • pattern matching: a wonderfully flexible way to handle business requirements
  • transport independence: how messages get to the right server is not something you should have to worry about
  • maturity: 5 years in production (before we called it micro-services), but was once taken out by lightning

Kong and seneca are both open source tools. It seems that Kong with 22.4K GitHub stars and 2.75K forks on GitHub has more adoption than seneca with 3 GitHub stars and 1 GitHub forks.

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.

What is seneca?

Seneca is a toolkit for organizing the business logic of your app. You can break down your app into "stuff that happens", rather than focusing on data models or managing dependencies.
Get Advice Icon

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

Why do developers choose Kong?
Why do developers choose seneca?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
        Be the first to leave a con
        What companies use Kong?
        What companies use seneca?

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

        What tools integrate with Kong?
        What tools integrate with seneca?

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

        What are some alternatives to Kong and seneca?
        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.
        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鈥檚 own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development.
        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.
        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.
        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.
        See all alternatives
        Decisions about Kong and seneca
        Kong
        Kong

        I use Kong because it reliably proxies traffic quickly with an assortment of pluggable features. The engineers behind the product are of the highest quality. The Company has cultivated the largest active open source community of any API gateway. They generally squash bugs in hours or days not weeks/months. Company engineers help community members through social avenues as well as supporting large enterprise. They heavily value their product and individuals as opposed to just solely growing enterprise license fees.

        See more
        Al Tsang
        Al Tsang
        CEO at LunchBadger | 4 upvotes 33.3K views
        atLunchBadgerLunchBadger
        Express Gateway
        Express Gateway
        ExpressJS
        ExpressJS
        Kong
        Kong
        Tyk Cloud
        Tyk Cloud
        #Gateway
        #OAuth2
        #JWT
        #APIs
        Problem/Challenge

        We needed a lightweight and completely customizable #microservices #gateway to be able to generate #JWT and introspect #OAuth2 tokens as well. The #gateway was going to front all #APIs for our single page web app as well as externalized #APIs for our partners.

        Contenders

        We looked at Tyk Cloud and Kong. Kong's plugins are all Lua based and its core is NGINX and OpenResty. Although it's open source, it's not the greatest platform to be able to customize. On top of that enterprise features are paid and expensive. Tyk is Go and the nomenclature used within Tyk like "sessions" was bizarre, and again enterprise features were paid.

        Decision

        We ultimately decided to roll our own using ExpressJS into Express Gateway because the use case for using ExpressJS as an #API #gateway was tried and true, in fact - all the enterprise features that the other two charge for #OAuth2 introspection etc were freely available within ExpressJS middleware.

        Outcome

        We opened source Express Gateway with a core set of plugins and the community started writing their own and could quickly do so by rolling lots of ExpressJS middleware into Express Gateway

        See more
        Interest over time
        Reviews of Kong and seneca
        Review ofKongKong

        We're a small startup in San Francisco (team of 18 people). After spending lots of time building our core technology, it was time to bring it to life and deploy with several very large customers (500+ API requests/customer/minute).

        We looked for a solid API management solution that would allow for easy authentication, quick installation and great logging features (requests and responses). After looking at various (very) expensive solutions out there, we ran into Kong.

        After testing it for a few days, we deployed quickly to production to serve the needs of our customers. 3 weeks in, our experience has been great. Highly recommended to anyone who's looking for API management solutions.

        P.s. Scored "Reliability" as "OK" for now with lack of data. Will definitely update once we've had Kong in production for a longer period of time.

        Review ofsenecaseneca

        It points to a fork (thus showing a low number of GitHub stars).

        Should be: https://github.com/senecajs/seneca

        How developers use Kong and seneca
        Avatar of Vincent Vermersch
        Vincent Vermersch uses KongKong

        And if developper can also code the load balancer ? Add plugin, dynamically change backend, Kong give this versatility

        Avatar of Datacoon
        Datacoon uses KongKong

        Easy to use

        How much does Kong cost?
        How much does seneca cost?
        Pricing unavailable
        News about seneca
        More news