An open platform to connect, manage, and secure microservices.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.

An open platform to connect, manage, and secure microservices. 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.

Istio - An open platform to connect, manage, and secure microservices

An application metrics facade for the most popular monitoring tools. Instrument your code with dimensional metrics with a vendor neutral interface and decide on the monitoring backend at the last minute. Micrometer is the instrumentation library underpinning Spring Boot 2.0's metrics collection.
 
As an instrumentation facade, Micrometer allows you to instrument your code with dimensional metrics with a vendor-neutral interface and decide on the monitoring system as a last step. Instrumenting your core library code with Micrometer allows the libraries to be included in applications that ship metrics to different backends. It supports out-of-the-box instrumentation of caches, the class loader, garbage collection, processor utilization, thread pools, and more tailored to actionable insight.

 An application metrics facade for the most popular monitoring tools. Instrument your code with dimensional metrics with a vendor neutral interface and decide on the monitoring backend at the last minute. Micrometer is the instrumentation library underpinning Spring Boot 2.0's metrics collection.

Micrometer - An application metrics facade for the most popular monitoring tools

Jib builds optimized Docker and OCI images for your Java applications without a Docker daemon - and without deep mastery of Docker best-practices. It is available as plugins for Maven and Gradle and as a Java library. Jib separates your application into multiple layers, splitting dependencies from classes. Now you don’t have to wait for Docker to rebuild your entire Java application - just deploy the layers that changed. 
 
Rebuilding your container image with the same contents always generates the same image. Never trigger an unnecessary update again. Reduce your CLI dependencies. Build your Docker image from within Maven or Gradle and push to any registry of your choice. No more writing Dockerfiles and calling docker build/push.

Jib builds optimized Docker and OCI images for your Java applications without a Docker daemon - and without deep mastery of Docker best-practices. It is available as plugins for Maven and Gradle and as a Java library.

jib - Build container images for your Java applications.

ThingsBoard is an open-source IoT platform for data collection, processing, visualization, and device management. It enables device connectivity via industry standard IoT protocols - MQTT, CoAP and HTTP and supports both cloud and on-premises deployments. ThingsBoard combines scalability, fault-tolerance and performance so you will never lose your data.
 
It helps to provision and manage devices and assets, Collect and visualize data, Raise alarms on incoming telemetry events, Construct your ThingsBoard cluster and get maximum scalability and fault-tolerance with microservices architecture. Construct your ThingsBoard cluster and get maximum scalability and fault-tolerance with microservices architecture.

ThingsBoard is an open-source IoT platform for data collection, processing, visualization, and device management. It enables device connectivity via industry standard IoT protocols - MQTT, CoAP and HTTP and supports both cloud and on-premises deployments. ThingsBoard combines scalability, fault-tolerance and performance so you will never lose your data.

ThingsBoard - IoT platform for data collection, processing, visualization, and device management

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 

Armeria is your go-to microservice framework for any situation. You can build any type of microservice leveraging your favorite technologies, including gRPC, Thrift, Kotlin, Retrofit, Reactive Streams, Spring Boot and Dropwizard. Armeria is capable of running services using different protocols, all on a single port. No need for any proxies or sidecars.
 
Armeria's documentation service allows you to browse the complete list of services and their documentation from a web browser. It provides various service discovery mechanisms, from Kubernetes-style DNS records to ZooKeeper data nodes.
 
Armeria is from the creator of <a href="https://netty.io/">Netty</a>&nbsp;and his colleagues at <a href="https://engineering.linecorp.com/en/">LINE</a>

Armeria is your go-to microservice framework for any situation. You can build any type of microservice leveraging your favorite technologies, including gRPC, Thrift, Kotlin, Retrofit, Reactive Streams, Spring Boot and Dropwizard. Armeria is capable of running services using different protocols, all on a single port. No need for any proxies or sidecars.

Armeria - Build any type of microservice leveraging your favorite technologies, including gRPC, Thrift, Kotlin, Retrofit, Reactive Streams, Spring Boot and Dropwizard

The Atmosphere Framework contains client and server side components for building Asynchronous Web Applications. It transparently supports WebSockets, Server Sent Events (SSE), Long-Polling, HTTP Streaming (Forever frame) and JSONP. Its mission is to make real time apps possible in every browser, library and mobile device, blurring the differences between the different transport mechanisms.
 
The Atmosphere Framework Stack works on all Servlet based servers, Spring Boot and frameworks like Netty, Play! Framework and Vert.x. We support a variety of extensions like Apache Kafka, Hazelcast, RabbitMQ, Redis and many more.

The Atmosphere Framework contains client and server side components for building Asynchronous Web Applications. It transparently supports WebSockets, Server Sent Events (SSE), Long-Polling, HTTP Streaming (Forever frame) and JSONP. Its mission is to make real time apps possible in every browser, library and mobile device, blurring the differences between the different transport mechanisms.

Atmosphere - Realtime Client Server Framework for the JVM

Nameko is a microservices framework for Python that lets service developers concentrate on application logic and encourages testability. Developer can focus on business logic and write regular Python methods and classes to implement your service. Nameko will manage connections, transports and concurrency for you.
 
Nameko gives you effortless concurrency by yielding workers when they wait for I/O, leaving you free to handle many requests without the worry of threading. Nameko is compatible with almost any protocol, transport or database. Simply use the built-in extensions, build your own or leverage the community.

Nameko is a microservices framework for Python that lets service developers concentrate on application logic and encourages testability. Developer can focus on business logic and write regular Python methods and classes to implement your service. Nameko will manage connections, transports and concurrency for you.



Nameko - A Microservice framework for Python

Apollo is a set of Java libraries that we use at Spotify when writing microservices. Apollo includes modules such as an HTTP server and a URI routing system, making it trivial to implement restful API services. Apollo has been used in production at Spotify for a long time.

Apollo - Java libraries for writing composable microservices

Micronaut is a modern, JVM-based, full stack microservices framework designed for building modular, easily testable microservice applications. Micronaut is developed by the creators of the Grails framework and takes inspiration from lessons learnt over the years building real-world applications from monoliths to microservices using Spring, Spring Boot and Grails.
 
Micronaut apps startup in tens of milliseconds with GraalVM. It features a Dependency Injection and Aspect-Oriented Programming runtime that uses no reflection. Micronaut's Cloud support is built right in, including support for common discovery services, distributed tracing tools, and cloud runtimes.

Micronaut is a modern, JVM-based, full stack microservices framework designed for building modular, easily testable microservice applications. Micronaut is developed by the creators of the Grails framework and takes inspiration from lessons learnt over the years building real-world applications from monoliths to microservices using Spring, Spring Boot and Grails.

Micronaut  - A modern, JVM-based, full-stack framework for building modular, easily testable microservice and serverless applications

Litmus is a toolset to do cloud-native chaos engineering. Litmus provides tools to orchestrate chaos on Kubernetes to help SREs find weaknesses in their deployments. SREs use Litmus to run chaos experiments initially in the staging environment and eventually in production to find bugs, vulnerabilities. Fixing the weaknesses leads to increased resilience of the system.
 
Chaos experiments are hosted on hub.litmuschaos.io. It is a central hub where the application developers or vendors share their chaos experiments so that their users can use them to increase the resilience of the applications in production.

Litmus is a toolset to do cloud-native chaos engineering. Litmus provides tools to orchestrate chaos on Kubernetes to help SREs find weaknesses in their deployments. SREs use Litmus to run chaos experiments initially in the staging environment and eventually in production to find bugs, vulnerabilities. Fixing the weaknesses leads to increased resilience of the system.

Litmus - Cloud-Native Chaos Engineering

Apache APISIX is a dynamic, real-time, high-performance API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. You can use Apache APISIX to handle traditional north-south traffic, as well as east-west traffic between services. It can also be used as a k8s ingress controller.
 
You can use Apache APISIX as a traffic entrance to process all business data, including dynamic routing, dynamic upstream, dynamic certificates, A/B testing, canary release, blue-green deployment, limit rate, defense against malicious attacks, metrics, monitoring alarms, service observability, service governance, etc.

Apache APISIX is a dynamic, real-time, high-performance API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. You can use Apache APISIX to handle traditional north-south traffic, as well as east-west traffic between services. It can also be used as a k8s ingress controller.

Apache APISIX - Dynamic, real-time, high-performance API gateway

Kubernetes has made it very easy to deploy applications to the cloud at a higher scale than ever, but the development practices have not evolved at the same speed as application deployment patterns. Today, most developers try to either run parts of the infrastructure locally, or just test these integrations directly in the cluster via CI jobs or the "docker build, docker push, kubectl apply" cycle. It works, but this workflow is painful and incredibly slow.

Okteto - A Tool for Cloud Native Developers

WildFly Swarm offers an innovative approach to packaging and running Java EE applications by packaging them with just enough of the server runtime to "java -jar" your application. It is MicroProfile compatible. It is the decomposition and reconstitution of the popular WildFly Java Application Server in order to support just enough appserver for microservice type applications.

Wildfly-swarm - Java Application Server

Discover open source projects across all platforms

Projects