Skip to content
An all-in-one data service for microservices, FaaS functions, etc. gRPC and HTTP interfaces.
Go Makefile Dockerfile HCL
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add GitHub Actions workflow for build/test plus README badges Jul 28, 2019
cmd Add Cobra-based CLI system Jul 28, 2019
deploy Add multiple K8s configs plus README instructions Aug 11, 2019
examples Remove test forcing test suite to hang Jul 28, 2019
proto Fix merge conflicts Jul 28, 2019
vendor Re-vendor Jul 28, 2019
.gitignore Fix KV tests Jul 28, 2019
Dockerfile Update Makefile commands for multiple images Jul 28, 2019
LICENSE Add MIT license Aug 5, 2019
Makefile Add -p 1 to tests Jul 31, 2019 Add multiple K8s configs plus README instructions Aug 11, 2019
cache.go Remove unused proto converstion function for CacheItem Jul 26, 2019
config.go Add Cobra-based CLI system Jul 28, 2019
config_test.go Remove test forcing test suite to hang Jul 28, 2019
counter.go Rename counter methods for clarity Jul 28, 2019
docker-compose.yml Add Docker Compose config for strato image Jul 26, 2019
error.go Add Viper-based config system for gRPC and HTTP servers Jul 28, 2019
error_test.go Fix tests (not yet) Jul 28, 2019
go.mod Add gRPC set tests Jul 31, 2019
go.sum Add gRPC set tests Jul 31, 2019
grpc_client.go Fix merge conflicts Jul 28, 2019
grpc_client_test.go Remove test forcing test suite to hang Jul 28, 2019
grpc_server.go Add gRPC server shutdown test Jul 31, 2019
grpc_server_test.go Add gRPC search tests Jul 31, 2019
http_server.go Add Cobra-based CLI system Jul 28, 2019
kv.go Fix tests (not yet) Jul 28, 2019
kv_test.go Fix broken KV tests Jul 28, 2019
memory.go Fix merge conflicts Jul 28, 2019
memory_test.go Reinstate KV test Jul 28, 2019
search.go Fix merge issues Jul 27, 2019
search_test.go Rename module to Jul 27, 2019
set.go Add initial Set interface and Memory impl Jul 27, 2019


Actions Status GoDoc

An all-in-one data service with support for:

  • Key/value operations
  • Counters and sets
  • Caching with TTL
  • Search indexing and querying

Strato is meant to abstract away complex database interfaces (Redis, DynamoDB, Mongo, etc.) in favor of a unified set of dead-simple operations (see the full list of operations below).

You can run Strato as a gRPC server or an HTTP server (both expose the same interfaces). There's currently a gRPC client for Go only but in principle gRPC clients could be added for other languages.

The project


Microservices or FaaS functions that rely on stateful data operations no longer have to interact with multiple databases and can interact only with Strato for all stateful data needs. This greatly simplifies the service/function development process by sharply reducing the hassle of dealing with databases (i.e. no need to install/learn/use 5 different database clients).

Does your service need something that isn't provided by Strato? File an issue or submit a PR and I'll add it!

Current status

Strato is in its very early stages. The data interfaces it provides are almost comically simple and it has only an in-memory implementation, which means that Strato data is not durable.

So please do not use Strato as a production data service just yet (though I'd like to get there). Instead, use it for prototyping and experimenting. It runs as a single instance and has no clustering built in.

Future directions

In the future, I imagine Strato acting as an abstraction layer over lots of different data systems, exposing a powerful interface that covers the overwhelming majority of data use cases without exposing the system internals of any of those systems. This would entail:

  • Making the current data interfaces more sophisticated and capable of covering a wider range of use cases
  • Adding new interfaces, such as a timeseries interface, a simple graph interface, etc.
  • Providing a relational interface that supports a subset of SQL (SQLite would likely suffice for this)
  • Providing optional pluggable backends behind Strato (e.g. using Redis for caching, Elasticsearch for search)
  • Providing a message queue/pub-sub interface, eliminating the need for a Kafka/Pulsar/RabbitMQ/etc. client

Want to contribute?

See the contributors guide for details.


The table below lists the available client operations for the Go client:

Operation Domain Explanation
CacheGet(key string) Cache Fetches the value of a key from the cache. Returns an error if the TTL has been exceeded.
CacheSet(key, value string, ttl in32) Cache Sets the value associated with a key and assigns a TTL (the default is 5 seconds).
CounterIncrement(key string, amount in32) Counter Increments a counter by the designated amount.
CounterGet(key string) Counter Fetches the current value of a counter.
GetSet(set string) Set Fetch the items currently in the specified set.
AddToSet(set, item string) Set Add an item to the specified set.
RemoveFromSet(set, item string) Set Remove an item from the specified set.
KVGet(location *Location) KV Gets the value associated with a Location. Location is currently just a key but could be made more complex later (e.g. a bucket + key scheme).
KVPut(location *Location, value *Value) KV Sets the value associated with a location. The value is currently just a byte array payload but could be made more complex later (e.g. a payload plus a content type, metadata, etc.).
KVDelete(location *Location) KV Deletes the value associated with a key.
Index(doc *Document) Search Indexes a search Document.
Query(q string) Search Returns a set of documents that matches the supplied search term. At the moment, it simply uses the raw query string but more sophisticated schemes will be added later.

The Go client is currently only for the gRPC interface.

Try it out

To try out Strato locally, you can run the Strato gRPC server in one shell session and some example client operations in another session:

git clone && cd strato

# Start the gRPC server...
go run examples/grpc-server/main.go

# And then in a different session...
go run examples/grpc-client/main.go


gRPC server

To install the Strato gRPC server:

# Executable
go get

# Docker image
docker pull lucperkins/strato-grpc:latest

Then you can run it:

# Executable

# Docker image
docker run --rm -it -p 8080:8080 lucperkins/strato-grpc:latest

You should see log output like this:

2019/07/27 14:37:09 Starting up the server on port 8080

HTTP server

To install the Strato HTTP server:

# Executable
go get

# Docker image
docker pull lucperkins/strato-http:latest

Then you can run it:

# Executable

# Docker image
docker run --rm -it -p 8081:8081 lucperkins/strato-http:latest

gRPC Go client

To use the Go client in your service or FaaS function:

go get

To instantiate a client:

import ""

// Supply the address of the Strato gRPC server
client, err := strato.NewClient("localhost:8080")
if err != nil { 
    // Handle error

// Now you can run the various data operations, for example:
if err := client.CacheSet("player1-session", "a1b2c3d4e5f6", 120); err != nil {
    // Handle error



There are two configuration files in the deploy directory that enable you to run the Strato gRPC and HTTP servers, respectively, on Kubernetes. Both use the default namespace.


kubectl apply -f deploy/strato-grpc-k8s.yaml


kubectl apply -f deploy/strato-http-k8s.yaml

Accessing the service

Once you've deployed Strato on Kubernetes, you can access it in your local environment using port forwarding:

# gRPC
kubectl port-forward svc/strato 8080:8080

kubectl port-forward svc/strato 8081:8081
You can’t perform that action at this time.