nytimes/gizmo

A Microservice Toolkit from The New York Times

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 18th, 2026
Created on December 15th, 2015
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 225
Total Stargazers: 3,772 (+0)
Total Subscribers: 112 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Gizmo is a microservice toolkit for Go that provides standardized patterns and utilities for building server and pub/sub daemons.

The toolkit addresses the need for consistent infrastructure across microservices by offering reusable packages for common concerns. It provides standardized configuration and logging, health check endpoints with configurable strategies, structured logging with basic request information, useful metrics for endpoints, and graceful shutdown handling. The core server package includes a SimpleServer implementation capable of handling HTTP and JSON requests through multiple service types, while an optional server/kit package provides a more opinionated approach that integrates with go-kit for serving both HTTP/JSON and gRPC, with automatic monitoring, tracing, and metrics registration when running on Google Cloud Platform, AWS, or Kubernetes.

The toolkit suits teams building microservices in Go who want to standardize operational patterns across services. The server/kit package is specifically designed for services deploying to GCP, with built-in integration for Stackdriver logging, metrics, and error reporting. The observe package provides observability helpers through OpenCensus, enabling metrics and tracing with platform detection for App Engine, Cloud Run, Kubernetes Engine, Compute Engine, and AWS EC2. Teams should be aware that the project is in maintenance mode and that import paths are planned to migrate from the current structure to a versioned path, which will be a breaking change.

The project maintains a stable codebase with infrequent updates, reflecting its maintenance-mode status. Development activity is minimal, with no active feature development or rapid iteration occurring.