Displaying 1 to 20 from 20 results

vert.x - Vert.x is a tool-kit for building reactive applications on the JVM


This is the repository for Vert.x core.Vert.x core contains fairly low-level functionality, including support for HTTP, TCP, file system access, and various other features. You can use this directly in your own applications, and it's used by many of the other components of Vert.x.

unfiltered - A toolkit for servicing HTTP requests in Scala


See the Unfiltered documentation for instructions on using the project. The core application library for Unfiltered. This module provides interfaces and implementations of core request extractors and response combinators.




rsocket-java - Java implementation of RSocket


RSocket is a binary protocol for use on byte stream transports such as TCP, WebSockets, and Aeron.Snapshots are available via JFrog.

goframe - send/receive framed data via TCP


goframe provides wrapped net.Conn that can send and receive framed data.You can use NewXXXXXXX function to get a concrete FrameConn.


ob1k - Ob1k - The RPC Framework


Ob1k is an asynchronous light-weight RPC framework for rapid development of async, high performance micro services.

NioImapClient - High performance, async IMAP client implementation


This client is well tested and heavily used at HubSpot, but it is still under active development and its public API is not guaranteed to be stable.

link - A clojure framework for nonblocking network programming


link is the event-driven network library used by slacker. It's a thin wrapper of Netty. Currently, link only works on the JVM implementation of Clojure. We might support nodejs in future.

highlander - soft landing for high speed data


Highlander is taking on the "lightings" of data at high speeds and stores this data with the speed that a data store feels comfortable with. where "Non blocking I/O", "Queue" and "Data Store" pieces are pluggable.

netty-rest - Yet another high performance REST server based on Netty


Netty-rest is a high performance HTTP and WebSocket server implementation based on Netty. It uses javax.ws.rs annotations and generates Java bytecode at runtime in order to provide best performance. It basically maps the java methods to endpoints and takes care of validation, serialization / deserialization, authentication and designed for minimum overhead and maximum performance. It can generate Swagger specification automatically so that you can generate client libraries, API documentation easily. If you don't pass one of the parameters, the server will return 400 response, you can also use complex java beans in parameters and method return signature. The library uses Jackson for serialization of the object that you passed and deserialization of the JSON attributes. It will be mapped to the parameters and the method will be invoked for the API calls.

vertx-materials - Various stuff about Vert.x


This is a book effort that aims to document more advanced/internal about Vert.x. The book uses the Vert.x Docgen project to render Java code in the Asciidoc files, allowing real source code to be included in the project with Javadoc {@link} tags.

netty-tcnative-alpine - Build netty-tcnative native binaries for Alpine Linux.


Docker container used to build netty-tcnative binaries for Alpine Linux. One needs an alpine container, obviouslly and libuuid dependency, otherwise even boringssl-static won't work.

netty-queue - Simple queue: java, json-rest, netty


This is an simple java queue server. See integration test benchmarks for more details.

netty-sni-example - An example of how to use server-side SNI in Netty with Java 8.


This is a quick example demonstrating how to use Java 8's server-side SNI support in Netty. SniKeyManager is a key manager which wraps around the default key manager. It forwards most methods to the default key manager. However, it implements its own logic for the chooseEngineServerAlias() method - using SNI to pick which certificate to use.

mongo-java-server - Stub implementation of MongoDB in Java that speaks the wire protocol.


Stub implementation of the core MongoDB server in Java. The MongoDB Wire Protocol is implemented with Netty. Different backends are possible and can be easily extended. The in-memory backend is the default, such that mongo-java-server can be used as stub in unit tests. It supports the basic CRUD operations. However, not all features are implemented, such as full-text search or map/reduce.