Alternatives to Jersey logo

Alternatives to Jersey

Spring, Jetty, Spring Boot, ExpressJS, and Flask are the most popular alternatives and competitors to Jersey.
91
99
+ 1
5

What is Jersey and what are its top alternatives?

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.
Jersey is a tool in the Microframeworks (Backend) category of a tech stack.

Top Alternatives to Jersey

  • Spring

    Spring

    A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments. ...

  • Jetty

    Jetty

    Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty. ...

  • Spring Boot

    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

  • ExpressJS

    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. ...

  • Flask

    Flask

    Flask is intended for getting started very quickly and was developed with best intentions in mind. ...

  • Django REST framework

    Django REST framework

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

  • Istio

    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. ...

  • Sinatra

    Sinatra

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

Jersey alternatives & related posts

Spring logo

Spring

3.4K
3.9K
1K
Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
3.4K
3.9K
+ 1
1K
PROS OF SPRING
  • 221
    Java
  • 155
    Open source
  • 133
    Great community
  • 120
    Very powerful
  • 111
    Enterprise
  • 63
    Lot of great subprojects
  • 59
    Easy setup
  • 44
    Convention , configuration, done
  • 38
    Standard
  • 29
    Love the logic
  • 12
    Good documentation
  • 10
    Stability
  • 10
    Dependency injection
  • 7
    MVC
  • 6
    Easy
  • 3
    Strong typing
  • 3
    Makes the hard stuff fun & the easy stuff automatic
  • 2
    Maven
  • 2
    Code maintenance
  • 2
    Best practices
  • 2
    Great Desgin
  • 2
    Easy Integration with Spring Security
  • 2
    Integrations with most other Java frameworks
  • 1
    Java has more support and more libraries
  • 1
    Supports vast databases
  • 1
    Large ecosystem with seamless integration
  • 1
    OracleDb integration
  • 1
    Live project
CONS OF SPRING
  • 15
    Draws you into its own ecosystem and bloat
  • 3
    Verbose configuration
  • 3
    Poor documentation
  • 3
    Java
  • 1
    Java is more verbose language in compare to python

related Spring posts

Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

See more

I am consulting for a company that wants to move its current CubeCart e-commerce site to another PHP based platform like PrestaShop or Magento. I was interested in alternatives that utilize Node.js as the primary platform. I currently don't know PHP, but I have done full stack dev with Java, Spring, Thymeleaf, etc.. I am just unsure that learning a set of technologies not commonly used makes sense. For example, in PrestaShop, I would need to work with JavaScript better and learn PHP, Twig, and Bootstrap. It seems more cumbersome than a Node JS system, where the language syntax stays the same for the full stack. I am looking for thoughts and advice on the relevance of PHP skillset into the future AND whether the Node based e-commerce open source options can compete with Magento or Prestashop.

See more
Jetty logo

Jetty

382
277
44
An open-source project providing an HTTP server, HTTP client, and javax.servlet container
382
277
+ 1
44
PROS OF JETTY
  • 15
    Lightweight
  • 10
    Very fast
  • 9
    Embeddable
  • 5
    Scalable
  • 5
    Very thin
CONS OF JETTY
  • 0
    Student

related Jetty posts

Spring Boot logo

Spring Boot

17.6K
15.6K
913
Create Spring-powered, production-grade applications and services with absolute minimum fuss
17.6K
15.6K
+ 1
913
PROS OF SPRING BOOT
  • 134
    Powerful and handy
  • 127
    Easy setup
  • 118
    Java
  • 86
    Spring
  • 82
    Fast
  • 42
    Extensible
  • 34
    Lots of "off the shelf" functionalities
  • 29
    Cloud Solid
  • 23
    Caches well
  • 21
    Many receipes around for obscure features
  • 20
    Productive
  • 20
    Modular
  • 19
    Spring ecosystem is great
  • 19
    Integrations with most other Java frameworks
  • 18
    Fast Performance With Microservices
  • 17
    Auto-configuration
  • 16
    Community
  • 13
    One-stop shop
  • 13
    Easy setup, Community Support, Solid for ERP apps
  • 12
    Cross-platform
  • 12
    Easy to parallelize
  • 11
    Easy setup, good for build erp systems, well documented
  • 11
    Powerful 3rd party libraries and frameworks
  • 10
    Easy setup, Git Integration
  • 3
    Kotlin
  • 3
    It's so easier to start a project on spring
CONS OF SPRING BOOT
  • 20
    Heavy weight
  • 17
    Annotation ceremony
  • 10
    Many config files needed
  • 8
    Java
  • 5
    Reactive
  • 4
    Excellent tools for cloud hosting, since 5.x

related Spring Boot posts

Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

See more
Praveen Mooli
Engineering Manager at Taylor and Francis · | 14 upvotes · 2.1M views

We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

To build #Webapps we decided to use Angular 2 with RxJS

#Devops - GitHub , Travis CI , Terraform , Docker , Serverless

See more
ExpressJS logo

ExpressJS

20.6K
16.6K
1.5K
Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
20.6K
16.6K
+ 1
1.5K
PROS OF EXPRESSJS
  • 368
    Simple
  • 323
    Node.js
  • 235
    Javascript
  • 186
    High performance
  • 148
    Robust routing
  • 67
    Middlewares
  • 66
    Open source
  • 53
    Great community
  • 34
    Hybrid web applications
  • 10
    Well documented
  • 8
    Sinatra inspired
  • 5
    Isomorphic js.. superfast and easy
  • 4
    Rapid development
  • 2
    Npm
  • 2
    Resource available for learning
  • 2
    Socket connection
  • 2
    Xxx
  • 2
    Light weight
  • 2
    Event loop
  • 1
    Data stream
  • 1
    Callbacks
CONS OF EXPRESSJS
  • 24
    Not python
  • 16
    Overrated
  • 14
    No multithreading
  • 6
    Javascript
  • 5
    Not fast
  • 2
    Easily Insecure for Novices
  • 1
    Nnnn
  • 1
    Not a lion

related ExpressJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.2M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more

Repost

Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

See more
Flask logo

Flask

14.5K
12.3K
1.5K
A microframework for Python based on Werkzeug, Jinja 2 and good intentions
14.5K
12.3K
+ 1
1.5K
PROS OF FLASK
  • 314
    Lightweight
  • 271
    Python
  • 215
    Minimal
  • 146
    Open source
  • 98
    Documentation
  • 66
    Easy to use
  • 54
    Easy to setup and get it going
  • 53
    Well designed
  • 48
    Easy to develop and maintain applications
  • 45
    Easy to get started
  • 18
    Beautiful code
  • 16
    Rapid development
  • 14
    Powerful
  • 13
    Expressive
  • 12
    Awesome
  • 11
    Flexibilty
  • 11
    Love it
  • 11
    Speed
  • 10
    Get started quickly
  • 10
    Easy to integrate
  • 10
    Simple to use
  • 9
    Customizable
  • 9
    For it flexibility
  • 9
    Perfect for small to large projects with superb docs.
  • 8
    Productive
  • 8
    Flexibilty and easy to use
  • 7
    Flask
  • 6
    Not JS
  • 6
    User friendly
  • 5
    Secured
  • 4
    Unopinionated
  • 1
    Secure
  • 1
    Orm
CONS OF FLASK
  • 10
    Not JS
  • 7
    Context
  • 4
    Not fast
  • 1
    Don't has many module as in spring

related Flask posts

James Man
Software Engineer at Pinterest · | 43 upvotes · 872.6K views
Shared insights
on
FlaskFlaskReactReact
at

One of our top priorities at Pinterest is fostering a safe and trustworthy experience for all Pinners. As Pinterest’s user base and ads business grow, the review volume has been increasing exponentially, and more content types require moderation support. To solve greater engineering and operational challenges at scale, we needed a highly-reliable and performant system to detect, report, evaluate, and act on abusive content and users and so we created Pinqueue.

Pinqueue-3.0 serves as a generic platform for content moderation and human labeling. Under the hood, Pinqueue3.0 is a Flask + React app powered by Pinterest’s very own Gestalt UI framework. On the backend, Pinqueue3.0 heavily relies on PinLater, a Pinterest-built reliable asynchronous job execution system, to handle the requests for enqueueing and action-taking. Using PinLater has significantly strengthened Pinqueue3.0’s overall infra with its capability of processing a massive load of events with configurable retry policies.

Hundreds of millions of people around the world use Pinterest to discover and do what they love, and our job is to protect them from abusive and harmful content. We’re committed to providing an inspirational yet safe experience to all Pinners. Solving trust & safety problems is a joint effort requiring expertise across multiple domains. Pinqueue3.0 not only plays a critical role in responsively taking down unsafe content, it also has become an enabler for future ML/automation initiatives by providing high-quality human labels. Going forward, we will continue to improve the review experience, measure review quality and collaborate with our machine learning teams to solve content moderation beyond manual reviews at an even larger scale.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
Django REST framework logo

Django REST framework

1.6K
1.7K
301
Web APIs for Django
1.6K
1.7K
+ 1
301
PROS OF DJANGO REST FRAMEWORK
  • 64
    Browsable api
  • 64
    Easy to use
  • 53
    Great documentation
  • 49
    Customizable
  • 41
    Fast development
  • 9
    Easy to use, customizable, pluggable, serializer
  • 8
    Python
  • 5
    Django ORM
  • 4
    FastSerialize
  • 2
    Less code
  • 2
    Easy implementation
  • 0
    Dsasda
CONS OF DJANGO REST FRAMEWORK
  • 2
    Bad documentation
  • 2
    Reimplements Django functionality
  • 1
    No support for URL Namespaces
  • 0
    Bad CSRF handling

related Django REST framework posts

Tim Abbott

Zulip has been powered by Django since the very early days of its development with Django 1.4, back in 2012. As a reasonably mature web application with significant scale, we're at the stage in many companies' development where one starts to rip out more and more of the web framework to optimize things or just make them work the way we want. (E.g. while I was at Dropbox in early 2016, we discovered we only had about 600 lines of code left from the original Pylons framework that actually ran).

One of the things that has been really fantastic about Django is that we're still happily using it for the vast majority of code in the project, and every time Django comes out with a new release, I read the changelog and get excited about several improvements that actually make my life better. While Django has made some design decisions that I don't agree with (e.g. I'm not a fan of Django REST framework, and think it makes life more difficult), Django also makes it easy to do your own thing, which we've done to great effect (see the linked article for details on our has_request_variables framework).

Overall I think we've gotten a ton of value out of Python and Django and would recommend it to anyone starting a new full-featured web application project today.

See more

Hi

I’ve been using Django for the last year on and off to do my backend API. I’m getting a bit frustrated with the Django REST framework with the setup of the serializers and Django for the lack of web sockets. I’m considering either Spring or .NET Core. I’m familiar with Kotlin and C# but I’ve not built any substantial projects with them. I like OOP, building a desktop app, web API, and also the potential to get a job in the future or building a tool at work to manage my documents, dashboard and processes point cloud data.

I’m familiar with c/cpp, TypeScript.

I would love your insights on where I should go.

See more
Istio logo

Istio

663
1.2K
44
Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
663
1.2K
+ 1
44
PROS OF ISTIO
  • 13
    Zero code for logging and monitoring
  • 8
    Service Mesh
  • 7
    Great flexibility
  • 4
    Ingress controller
  • 3
    Resiliency
  • 3
    Easy integration with Kubernetes and Docker
  • 3
    Full Security
  • 3
    Powerful authorization mechanisms
CONS OF ISTIO
  • 13
    Performance

related Istio posts

Anas MOKDAD
Shared insights
on
KongKongIstioIstio

As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

See more
Sinatra logo

Sinatra

584
462
212
Classy web-development dressed in a DSL
584
462
+ 1
212
PROS OF SINATRA
  • 65
    Lightweight
  • 50
    Simple
  • 35
    Open source
  • 20
    Ruby
  • 13
    Great ecosystem of tools
  • 10
    Ease of use
  • 8
    If you know http you know sinatra
  • 5
    Large Community
  • 5
    Fast
  • 1
    Flexibilty and easy to use
CONS OF SINATRA
    Be the first to leave a con

    related Sinatra posts