Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data. Zipkin’s design is based on the Google Dapper paper.
This project includes a dependency-free library and a spring-boot server. Storage options include in-memory, JDBC (mysql), Cassandra, and Elasticsearch.
Java Distributed Tracing implementation compatible with Zipkin.
Zipkin is based on Dapper.
dapper (dutch) = brave (english)... so that's where the name comes from.
More information on Distributed Tracing and OpenZipkin here: https://openzipkin.github.io
You can use brave if you use the JVM and:
- You can't use Finagle.
- You don't want to add Scala as a dependency to your Java project.
- You want out of the box integration support for RESTEasy, Jersey, Apache HttpClient.
Brave is compatible with OpenZipkin and its back-end components (zipkin-collector, zipkin-query, zipkin-web).
Motan is a remote procedure call(RPC) framework for rapid development of high performance distributed services.
- Create distributed services without writing extra code.
- Provides cluster support and integrate with popular service discovery services like [Consul][consul] or [Zookeeper][zookeeper].
- Supports advanced scheduling features like weighted load-balance, scheduling cross IDCs, etc.
- Optimization for high load scenarios, provides high availability in production environment.
Maven artifacts for each release are published to Maven Central.
For an overview of the available releases see Github releases. As of release 2.0 we try to stick to Semantic Versioning.