Kong is a cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway, API Middleware or in some cases Service Mesh). Backed by the battle-tested NGINX with a focus on high performance, Kong was made available as an open-source platform in 2015. Under active development, Kong is used in production at thousands of organizations from startups, Global 5000 and Government organizations.
 
If you are building for web, mobile or IoT (Internet of Things) you will likely end up needing common functionality to run your actual software. Kong can help by acting as a gateway (or a sidecar) for microservices requests while providing load balancing, logging, authentication, rate-limiting and more through plugins.
 
Its features include: 
<ul>
<li>Cloud-Native: Platform agnostic, Kong can run from bare metal to
Kubernetes.</li>
<li>Dynamic Load Balancing: Load balance traffic across multiple backend
services.</li>
<li>Service Discovery: Resolve SRV records in third-party DNS resolvers like
Consul.</li>
<li>Serverless: Invoke and secure AWS Lambda or OpenWhisk fuctions directly
from Kong.</li>
<li>WebSockets: Communicate to your upstream services via WebSockets.</li>
<li>OAuth2.0: Easily add OAuth2.0 authentication to your APIs.</li>
<li>Logging: Log requests and responses to your system over HTTP, TCP, UDP,
or to disk.</li>
<li>Security: ACL, Bot detection, whitelist/blacklist IPs, etc...</li>
<li>Syslog: Logging to System log.</li>
<li>SSL: Setup a Specific SSL Certificate for an underlying service or API.</li>
<li>Monitoring: Live monitoring provides key load and performance server
metrics.</li>
<li>Authentications: HMAC, JWT, Basic, and more.</li>
<li>Rate-limiting: Block and throttle requests based on many variables.</li>
<li>Transformations: Add, remove, or manipulate HTTP requests and responses.</li>
<li>Caching: Cache and serve responses at the proxy layer.</li>
<li>CLI: Control your Kong cluster from the command line.</li>
<li>REST API: Kong can be operated with its RESTful API for maximum
flexibility.</li>
<li>Geo-Replicated: Configs are always up-to-date across different regions.</li>
<li>Failure Detection &amp; Recovery: Kong is unaffected if one of your Cassandra
nodes goes down.</li>
<li>Clustering: All Kong nodes auto-join the cluster keeping their config
updated across nodes.</li>
<li>Scalability: Distributed by nature, Kong scales horizontally by simply
adding nodes.</li>
<li>Performance: Kong handles load with ease by scaling and using NGINX at
the core.</li>
<li>Plugins: Extendable architecture for adding functionality to Kong and
APIs.</li>
</ul>

Kong is a cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway, API Middleware or in some cases Service Mesh). Backed by the battle-tested NGINX with a focus on high performance, Kong was made available as an open-source platform in 2015. Under active development, Kong is used in production at thousands of organizations from startups, Global 5000 and Government organizations.

Kong - The Microservice API Gateway 

Micro is an operating system built for the cloud. It addresses the key requirements for building services in the cloud. It leverages the microservices architecture pattern and provides a set of services which act as the building blocks of a platform. Micro deals with the complexity of distributed systems and provides simpler programmable abstractions to build on.
 
Micro is built as a microservices architecture and abstracts away the complexity of the underlying infrastructure. It is composed as a single logical server to the user but decompose that into the various building block primitives that can be plugged into any underlying system.
The server is composed of the following services.<ul>
 <li>API - HTTP Gateway which dynamically maps http/json requests to RPC using path based resolution</li>
 <li>Auth - Authentication and authorization out of the box using jwt tokens and rule based access control.</li>
 <li>Broker - Ephemeral pubsub messaging for asynchronous communication and distributing notifications</li>
 <li>Config - Dynamic configuration and secrets management for service level config without the need to restart</li>
 <li>Events - Event streaming with ordered messaging, replay from offsets and persistent storage</li>
 <li>Network - Inter-service networking, isolation and routing plane for all internal request traffic</li>
 <li>Proxy - An identity aware proxy used for remote access and any external grpc request traffic</li>
 <li>Runtime - Service lifecycle and process management with support for source to running auto build</li>
 <li>Registry - Centralised service discovery and API endpoint explorer with feature rich metadata</li>
 <li>Store - Key-Value storage with TTL expiry and persistent crud to keep microservices stateless</li></ul>

Micro is an operating system built for the cloud. It  addresses the key requirements for building services in the cloud. It leverages the microservices architecture pattern and provides a set of services which act as the building blocks of a platform. Micro deals with the complexity of distributed systems and provides simpler programmable abstractions to build on.

Micro - Distributed Cloud OS 

Light 4j is a fast, lightweight and cloud native microservices framework. Light means lightweight, lighting fast and shed light on how to program with modern Java SE. It is 44 times faster than the most popular microservices platform Spring Boot embedded Tomcat and use only 1/5 of memory. 
Its features include: 
<ul>
<li>Plugin architecture for startup/shutdown hooks and middleware components</li>
<li>Distributed OAuth2 JWT security verification as part of the framework</li>
<li>Request and response validation against OpenAPI specification at runtime</li>
<li>Metrics collected in influxdb and viewed from Grafana Dashboard for both services and clients</li>
<li>Global exception handling for runtime exception, api exception and other checked exceptions</li>
<li>Mask sensitive data like credit card, sin number etc. before logging</li>
<li>Sanitize cross site scripting for query parameters, request headers and body</li>
<li>Audit to dump important info or entire request and response.</li>
<li>Body parser to support different content types</li>
<li>Standardized response code and messages from configuration file</li>
<li>Externalized configuration for all modules for dockerized environment</li>
<li>CORS pre-flight handler for SPA (Angular or React) from another domain</li>
<li>Rate limiting for services that exposed outside to the Internet</li>
<li>Service registry and discovery support direct, Consul and Zookeeper</li>
<li>Client side discovery and load balance to eliminate proxies</li>
<li>A client module that is tightly integrated with Light-OAuth2 and supports traceability</li>
</ul>

Light 4j is a fast, lightweight and cloud native microservices framework. Light means lightweight, lighting fast and shed light on how to program with modern Java SE. It is 44 times faster than the most popular microservices platform Spring Boot embedded Tomcat and use only 1/5 of memory.

light-4j - A fast, lightweight and more productive microservices framework

Debugging microservices applications is a difficult task. The state of an application is spread across multiple processes, often on different nodes. It is hard to get the holistic view of an application's state. Certain tools exist for troubleshooting microservice issues. OpenTracing can be used to produce transaction or workflow logs for post-mortem analysis. Service meshes like Istio can be used to monitor the network to identify latency problems. Unfortunately, these tools are passive, the feedback loop is slow, and they do not allow you to monitor and alter the application during run time.
 
Squash brings the power of modern debuggers to developers of microservice apps. Squash bridges between the apps running in a Kubernetes environment (without modifying them) and the IDE. Users are free to choose which containers, pods, services or images they are interested in debugging, and are allowed to set breakpoints in their codes, follow values of their variables on the fly, step through the code while jumping between microservices, and change these values during run time.

Debugging microservices applications is a difficult task. The state of an application is spread across multiple processes, often on different nodes. It is hard to get the holistic view of an application's state. Certain tools exist for troubleshooting microservice issues. OpenTracing can be used to produce transaction or workflow logs for post-mortem analysis. Service meshes like Istio can be used to monitor the network to identify latency problems. Unfortunately, these tools are passive, the feedback loop is slow, and they do not allow you to monitor and alter the application during run time.


Squash - The debugger for microservices

Jina is a neural search framework that empowers anyone to build SOTA & scalable deep learning search applications in minutes. It helps to build solutions for indexing, querying, understanding multi-/cross-modal data such as video, image, text, audio, source code, PDF.

Jina - Cloud-native neural search framework for any kind of data

Apache Juneau is a single cohesive Java ecosystem consisting of the following parts juneau-marshall, juneau-dto, juneau-svl, juneau-config, juneau-rest-server, juneau-rest-client, juneau-microservice.
 
<ul>
	<li>juneau-marshall A universal toolkit for marshalling POJOs to a wide variety of content types using a common framework with no external library dependencies.
	</li><li>juneau-dto A variety of predefined DTOs for serializing and parsing languages such as HTML5, Swagger and ATOM.
	</li><li>juneau-svl A simple yet powerful variable replacement language API.
	</li><li>juneau-config A sophisticated configuration file API.
	</li><li>juneau-rest-server A universal REST server API for creating Swagger-based self-documenting REST interfaces using POJOs, simply deployed as 
		one or more top-level servlets in any Servlet 3.1.0+ container.
	</li><li>juneau-rest-client A universal REST client API for interacting with Juneau or 3rd-party REST interfaces using POJOs and proxy interfaces.
	</li><li>juneau-microservice A REST microservice API that combines all the features above with a simple configurable Jetty server for 
		creating lightweight standalone REST interfaces that start up in milliseconds.
</li></ul>

Apache Juneau is a single cohesive Java ecosystem consisting of the following parts juneau-marshall, juneau-dto, juneau-svl, juneau-config, juneau-rest-server, juneau-rest-client, juneau-microservice.

Apache Juneau - Single cohesive framework

Cube.js is an open-source analytical API platform. It is primarily used to build internal business intelligence tools or add customer-facing analytics to existing applications. Cube.js was designed to work with serverless data warehouses and query engines like Google BigQuery and AWS Athena. A multi-stage querying approach makes it suitable for handling trillions of data points. Most modern RDBMS work with Cube.js as well and can be further tuned for performance.

Cube.js — Open-Source Analytical API Platform

Javalin is a very lightweight web framework for Kotlin and Java, inspired by Sparkjava and koa.js. Javalin is written in Kotlin with a few functional interfaces written in Java. This was necessary to provide an enjoyable and near identical experience for both Kotlin and Java developers.
<ul>
 <li>Lightweight - You don’t have to learn any advanced concepts to get started</li>
 <li>Consistent API - All handlers and mappers are void and operate on the Context (ctx)</li>
 <li>Almost identical API for both Kotlin and Java</li>
 <li>Not opinionated - A library rather than a framework (you never have to extend anything)</li>
 <li>Fully customizable embedded server (Jetty)</li>
 <li>JSON-object-mapping (via Jackson)</li>
 <li>Simple per-endpoint auth via <code class="highlighter-rouge">AccessManager</code> interface</li>
 <li>Simple static file handling</li>
 <li>Lifecycle events</li>
 <li>CookieStore - An easy way to serialize and store objects in cookies</li>
 <li>Template rendering (Velocity, Freemarker, Thymeleaf, Mustache)</li>
 <li>Markdown rendering</li>
</ul>

Javalin is a very lightweight web framework for Kotlin and Java, inspired by Sparkjava and koa.js. Javalin is written in Kotlin with a few functional interfaces written in Java. This was necessary to provide an enjoyable and near identical experience for both Kotlin and Java developers.

Javalin - A Simple REST API Library for Java / Kotlin

NebulaChat is an open source mtproto server written in golang with compatible telegram client. mproto protocol is designed for access to a server API from applications running on mobile devices. 

NebulaChat - Open source mtproto server written in golang with compatible telegram client

The goal of this project is to create a micro web framework in Java that should be easy to use and hack. Pippo can be used in small and medium applications and also in applications based on micro services architecture. Also, Pippo comes with a very small footprint that makes it excellent for embedded devices (Raspberry Pi for example).

pippo - Micro Java Web Framework

Spincast is a framework to serve as a backend for Single Page Applications (SPA), to develop old-school HTML generated websites or to be a REST API services platform. Spincast aims to feel more like a library than like a framework. It is not opinionated and favors configuration over convention. Its main goal is to give power to the developers. 

Spincast is an highly flexible and open source Java web framework, based on Guice

Discover open source projects across all platforms

Projects