Alternatives to Netty logo

Alternatives to Netty

Jetty, Mina, Apache Tomcat, Undertow, and Akka are the most popular alternatives and competitors to Netty.
206
300
+ 1
13

What is Netty and what are its top alternatives?

Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server.
Netty is a tool in the Concurrency Frameworks category of a tech stack.
Netty is an open source tool with 28.3K GitHub stars and 14K GitHub forks. Here’s a link to Netty's open source repository on GitHub

Top Alternatives to Netty

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

  • Mina

    Mina

    Mina works really fast because it's a deploy Bash script generator. It generates an entire procedure as a Bash script and runs it remotely in the server. Compare this to the likes of Vlad or Capistrano, where each command is run separately on their own SSH sessions. Mina only creates one SSH session per deploy, minimizing the SSH connection overhead. ...

  • Apache Tomcat

    Apache Tomcat

    Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. ...

  • Undertow

    Undertow

    It is a flexible performant web server written in java, providing both blocking and non-blocking API’s based on NIO. It has a composition based architecture that allows you to build a web server by combining small single purpose handlers. The gives you the flexibility to choose between a full Java EE servlet 4.0 container, or a low level non-blocking handler, to anything in between. ...

  • Akka

    Akka

    Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM. ...

  • NGINX

    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

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

  • Node.js

    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

Netty alternatives & related posts

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

Mina logo

Mina

76
62
9
Really fast deployer and server automation tool
76
62
+ 1
9
PROS OF MINA
  • 6
    Easy, fast and light weight
  • 2
    Reusable task
  • 1
    Ruby
CONS OF MINA
    Be the first to leave a con

    related Mina posts

    Apache Tomcat logo

    Apache Tomcat

    12.4K
    8.9K
    200
    An open source software implementation of the Java Servlet and JavaServer Pages technologies
    12.4K
    8.9K
    + 1
    200
    PROS OF APACHE TOMCAT
    • 79
      Easy
    • 72
      Java
    • 48
      Popular
    • 1
      Spring web
    CONS OF APACHE TOMCAT
      Be the first to leave a con

      related Apache Tomcat posts

      Остап Комплікевич

      I need some advice to choose an engine for generation web pages from the Spring Boot app. Which technology is the best solution today? 1) JSP + JSTL 2) Apache FreeMarker 3) Thymeleaf Or you can suggest even other perspective tools. I am using Spring Boot, Spring Web, Spring Data, Spring Security, PostgreSQL, Apache Tomcat in my project. I have already tried to generate pages using jsp, jstl, and it went well. However, I had huge problems via carrying already created static pages, to jsp format, because of syntax. Thanks.

      See more

      Java Spring JUnit

      Apache HTTP Server Apache Tomcat

      MySQL

      See more
      Undertow logo

      Undertow

      40
      54
      5
      A flexible performant web server written in java
      40
      54
      + 1
      5
      PROS OF UNDERTOW
      • 4
        Performance
      • 1
        Lower footprint
      CONS OF UNDERTOW
      • 1
        Smaller community
      • 1
        Less known

      related Undertow posts

      Akka logo

      Akka

      808
      843
      85
      Build powerful concurrent & distributed applications more easily
      808
      843
      + 1
      85
      PROS OF AKKA
      • 31
        Great concurrency model
      • 16
        Fast
      • 11
        Actor Library
      • 10
        Open source
      • 7
        Resilient
      • 5
        Scalable
      • 5
        Message driven
      CONS OF AKKA
      • 3
        Mixing futures with Akka tell is difficult
      • 2
        Closing of futures
      • 2
        No type safety
      • 1
        Typed actors still not stable
      • 0
        Very difficult to refactor

      related Akka posts

      To solve the problem of scheduling and executing arbitrary tasks in its distributed infrastructure, PagerDuty created an open-source tool called Scheduler. Scheduler is written in Scala and uses Cassandra for task persistence. It also adds Apache Kafka to handle task queuing and partitioning, with Akka to structure the library’s concurrency.

      The service’s logic schedules a task by passing it to the Scheduler’s Scala API, which serializes the task metadata and enqueues it into Kafka. Scheduler then consumes the tasks, and posts them to Cassandra to prevent data loss.

      See more
      Shared insights
      on
      AkkaAkkaKafkaKafka

      I decided to use Akka instead of Kafka streams because I have personal relationships at @Lightbend.

      See more
      NGINX logo

      NGINX

      95.2K
      45.4K
      5.5K
      A high performance free open source web server powering busiest sites on the Internet.
      95.2K
      45.4K
      + 1
      5.5K
      PROS OF NGINX
      • 1.4K
        High-performance http server
      • 896
        Performance
      • 728
        Easy to configure
      • 606
        Open source
      • 529
        Load balancer
      • 286
        Scalability
      • 285
        Free
      • 222
        Web server
      • 173
        Simplicity
      • 134
        Easy setup
      • 29
        Content caching
      • 19
        Web Accelerator
      • 14
        Capability
      • 13
        Fast
      • 11
        Predictability
      • 10
        High-latency
      • 7
        Reverse Proxy
      • 6
        Supports http/2
      • 4
        The best of them
      • 4
        Lots of Modules
      • 4
        Enterprise version
      • 4
        Great Community
      • 3
        High perfomance proxy server
      • 3
        Streaming media
      • 3
        Embedded Lua scripting
      • 3
        Reversy Proxy
      • 3
        Streaming media delivery
      • 2
        Fast and easy to set up
      • 2
        Lightweight
      • 2
        Slim
      • 2
        saltstack
      • 1
        Virtual hosting
      • 1
        Blash
      • 1
        GRPC-Web
      • 1
        Ingress controller
      • 1
        Narrow focus. Easy to configure. Fast
      • 1
        Along with Redis Cache its the Most superior
      • 0
        A
      CONS OF NGINX
      • 8
        Advanced features require subscription

      related NGINX posts

      Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

      We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

      See more
      Gabriel Pa
      Shared insights
      on
      TraefikTraefikNGINXNGINX
      at

      We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

      We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

      The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

      See more
      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
      Node.js logo

      Node.js

      127.6K
      107.6K
      8.4K
      A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
      127.6K
      107.6K
      + 1
      8.4K
      PROS OF NODE.JS
      • 1.4K
        Npm
      • 1.3K
        Javascript
      • 1.1K
        Great libraries
      • 1K
        High-performance
      • 795
        Open source
      • 484
        Great for apis
      • 474
        Asynchronous
      • 420
        Great community
      • 390
        Great for realtime apps
      • 295
        Great for command line utilities
      • 81
        Node Modules
      • 80
        Websockets
      • 67
        Uber Simple
      • 57
        Great modularity
      • 56
        Allows us to reuse code in the frontend
      • 40
        Easy to start
      • 35
        Great for Data Streaming
      • 31
        Realtime
      • 26
        Awesome
      • 24
        Non blocking IO
      • 17
        Can be used as a proxy
      • 16
        High performance, open source, scalable
      • 15
        Non-blocking and modular
      • 14
        Easy and Fun
      • 12
        Same lang as AngularJS
      • 12
        Easy and powerful
      • 11
        Future of BackEnd
      • 10
        Fast
      • 9
        Cross platform
      • 9
        Fullstack
      • 9
        Scalability
      • 8
        Simple
      • 7
        Mean Stack
      • 6
        Great for webapps
      • 6
        Easy concurrency
      • 5
        React
      • 5
        Fast, simple code and async
      • 5
        Typescript
      • 5
        Friendly
      • 4
        Easy to use and fast and goes well with JSONdb's
      • 4
        Great speed
      • 4
        Scalable
      • 4
        Fast development
      • 4
        Its amazingly fast and scalable
      • 4
        Control everything
      • 3
        Easy to use
      • 3
        It's fast
      • 3
        Isomorphic coolness
      • 2
        Not Python
      • 2
        Easy
      • 2
        Easy to learn
      • 2
        TypeScript Support
      • 2
        Scales, fast, simple, great community, npm, express
      • 2
        One language, end-to-end
      • 2
        Sooper easy for the Backend connectivity
      • 2
        Javascript2
      • 2
        Great community
      • 2
        Less boilerplate code
      • 2
        Blazing fast
      • 2
        Performant and fast prototyping
      • 1
        Event Driven
      • 1
        Lovely
      CONS OF NODE.JS
      • 46
        Bound to a single CPU
      • 42
        New framework every day
      • 37
        Lots of terrible examples on the internet
      • 29
        Asynchronous programming is the worst
      • 23
        Callback
      • 18
        Javascript
      • 11
        Dependency based on GitHub
      • 10
        Dependency hell
      • 10
        Low computational power
      • 7
        Can block whole server easily
      • 6
        Very very Slow
      • 6
        Callback functions may not fire on expected sequence
      • 3
        Unstable
      • 3
        Breaking updates
      • 3
        Unneeded over complication
      • 1
        No standard approach
      • 1
        Can't read server session
      • 1
        Bad transitive dependency management

      related Node.js posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 44 upvotes · 1.8M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 39 upvotes · 4.4M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more