Istio vs Jersey

Overview

Jersey

Stacks217

Followers125

Votes6

Istio

Stacks2.3K

Followers1.5K

Votes54

GitHub Stars37.6K

Forks8.1K

Istio vs Jersey: What are the differences?

Developers describe Istio as "Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft". 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. On the other hand, Jersey is detailed as "*A REST framework that provides a JAX-RS implementation *". 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.

Istio and Jersey can be categorized as "Microservices" tools.

Istio is an open source tool with 20K GitHub stars and 3.51K GitHub forks. Here's a link to Istio's open source repository on GitHub.

According to the StackShare community, Istio has a broader approval, being mentioned in 57 company stacks & 140 developers stacks; compared to Jersey, which is listed in 9 company stacks and 22 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 Jersey, Istio

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

lyc218

Feb 21, 2020

Needs advice

Envoy proxy is widely adopted in many companies for service mesh proxy, but it utilizes BoringSSL by default. Red Hat OpenShift fork envoy branch with their own OpenSSL support, I wonder any other companies are also using envoy-openssl branch for compatibility? How about AWS App Mesh?

Any input would be much appreciated!

42.8k views42.8k

Comments

Detailed Comparison

Jersey	Istio
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.	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.
Track the JAX-RS API and provide regular releases of production quality Reference Implementations that ships with GlassFish; Provide APIs to extend Jersey & Build a community of users and developers; Make it easy to build RESTful Web services utilizing Java and the Java Virtual Machine.	-
Statistics
GitHub Stars -	GitHub Stars 37.6K
GitHub Forks -	GitHub Forks 8.1K
Stacks 217	Stacks 2.3K
Followers 125	Followers 1.5K
Votes 6	Votes 54
Pros & Cons
Pros 4 Lightweight 1 Fast Performance With Microservices 1 Java standard	Pros 14 Zero code for logging and monitoring 9 Service Mesh 8 Great flexibility 5 Powerful authorization mechanisms 5 Resiliency Cons 17 Performance
Integrations
Oracle Java Apache Maven Java EE Eclipse	Kubernetes Docker

What are some alternatives to Jersey, Istio?

ExpressJS

Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.

Django REST framework

It is a powerful and flexible toolkit that makes it easy to build Web APIs.

Sails.js

Sails is designed to mimic the MVC pattern of frameworks like Ruby on Rails, but with support for the requirements of modern apps: data-driven APIs with scalable, service-oriented architecture.

Sinatra

Sinatra is a DSL for quickly creating web applications in Ruby with minimal effort.

Lumen

Laravel Lumen is a stunningly fast PHP micro-framework for building web applications with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Lumen attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as routing, database abstraction, queueing, and caching.

Slim

Slim is easy to use for both beginners and professionals. Slim favors cleanliness over terseness and common cases over edge cases. Its interface is simple, intuitive, and extensively documented — both online and in the code itself.

Fastify

Fastify is a web framework highly focused on speed and low overhead. It is inspired from Hapi and Express and as far as we know, it is one of the fastest web frameworks in town. Use Fastify can increase your throughput up to 100%.

Falcon

Falcon is a minimalist WSGI library for building speedy web APIs and app backends. We like to think of Falcon as the Dieter Rams of web frameworks.

hapi

hapi is a simple to use configuration-centric framework with built-in support for input validation, caching, authentication, and other essential facilities for building web applications and services.

TypeORM

It supports both Active Record and Data Mapper patterns, unlike all other JavaScript ORMs currently in existence, which means you can write high quality, loosely coupled, scalable, maintainable applications the most productive way.