This page summarises the various features which are present in Trillian, and their implementation status.
The status of features is listed as one of:
- Not Implemented (NI)
- In Development
- Partial
- Alpha
- Beta
- General Availability (GA)
- Deprecated (⚠)
| Status | Deployed in production | Notes | |
|---|---|---|---|
| Log V1 | GA | ✓ | |
| Log V2 (Skylog) | In development | #1674 | |
| Map | Alpha | ||
| Log-Backed-Map | In development |
This is feature complete, and is actively used in production by multiple CT log operators, including Google.
Skylog is an append-only log with considerably higher throughput and lower integration latency than the v1 log. It currently exists only in prototype form, but is being developed.
The Trillian Map is currently considered experimental code; while it's functional and could certainly be used to prototype systems, its use is nuanced and it is not currently recommended to deploy it into a production system.
(Also see section below on Log-Backed-Map for future work to make the map easier to use correctly.)
The log backed map is a framework for combining log(s) and map(s) to build systems that are able to represent the evolution and current "world state" of an ecosystem.
It's currently in a design phase.
This section lists the status of implementations for the pluggable subsystems which Trillian supports.
Trillian supports "pluggable" storage implementations for durable storage of the merkle tree data. The state and characteristics of these implementations are detailed below.
The Log storage implementations supporting the original Trillian log.
| Storage | Status | Deployed in prod | Notes |
|---|---|---|---|
| Spanner | GA | ✓ | Google internal-only, see CloudSpanner for external use. |
| CloudSpanner | Beta | Google maintains continuous-integration environment based on CloudSpanner. | |
| MySQL | GA | ✓ | |
| Postgres | In dev. | #1298 |
This is a Google-internal implementation, and is used by all of Google's current Trillian deployments.
This implementation uses the Google CloudSpanner APIs in GCE. It's been tested to tens of billions of entries and tens of log tenants.
Performance largely depends on the number of CloudSpanner servers allocated, but write throughput of 1000+ entries/s has been observed.
Issue #1681 tracks this becoming ready for GA.
This implementation has been tested with MySQL 5.7. It's currently in production use by at least one CT log operator.
Write throughput of 4-500 entries/s has been observed.
The postgres implementation is currently under development, and is not ready for use.
New Skylog capable storage implementations.
| Storage | Status | Deployed in prod | Notes |
|---|---|---|---|
| Spanner | NI | ||
| CloudSpanner | In dev. | #1674 | |
| MySQL | NI | ||
| Postgres | NI |
Storage implementations which support Trillian's Map mode.
| Storage | Status | Deployed in prod | Notes |
|---|---|---|---|
| Spanner | Alpha | ||
| CloudSpanner | Alpha | ||
| MySQL | Alpha | ||
| Postgres | NI |
Supported monitoring frameworks, allowing for production monitoring and alerting.
| Monitoring | Status | Deployed in prod | Notes |
|---|---|---|---|
| Prometheus | GA | ✓ | |
| OpenCensus | Partial | Currently, only support for Tracing is implemented. |
Supported frameworks for providing Master Election.
| Election | Status | Deployed in prod | Notes |
|---|---|---|---|
| Chubby | GA | ✓ | Google internal-only. |
| etcd | GA | ✓ |
Supported frameworks for quota management.
| Implementation | Status | Deployed in prod | Notes |
|---|---|---|---|
| Google internal | GA | ✓ | |
| etcd | GA | ✓ | |
| MySQL | Beta | ? | |
| Redis | Alpha | ✓ | |
| Postgres | NI |
Supported frameworks for key management and signing.
| Election | Status | Deployed in prod | Notes |
|---|---|---|---|
| Google internal | GA | ✓ | |
| golang stdlib | GA | i.e PEM files, etc. | |
| PKCS#11 | GA | ? |