gofr-dev/gofr

An opinionated GoLang framework for accelerated microservice development. Built in support for databases and observability.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 2nd, 2026
Created on October 24th, 2023
Open Issues & Pull Requests: 136 (+0)
GitHub issues: Enabled
Number of forks: 1,761
Total Stargazers: 20,941 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 100
New in 7 days: 8
Closed in 7 days: 9
Avg open age: 267 days
Stale 30+ days: 74
Stale 90+ days: 52

Recent activity

Opened in 7 days: 7
Closed in 7 days: 9
Comments in 7 days: 12
Events in 7 days: 43

Top labels

  • enhancement (105)
  • triage (77)
  • Datasource (75)
  • bug (72)
  • good first issue (67)
  • documentation (44)
  • go (29)
  • Service (26)

Detailed Description

GoFr is an opinionated Go framework for building microservices with built-in support for databases and observability.

The framework addresses the complexity of microservice development by providing integrated tooling for common concerns. It bundles observability features including structured logging, distributed tracing, and metrics collection; database connectivity with health checks and migration support; gRPC and HTTP communication with circuit breaker patterns; and authentication middleware. The approach emphasizes sensible defaults and REST standards while allowing customization through middleware and configuration management.

GoFr suits teams building microservices intended for Kubernetes deployment who want observability and database integration without assembling multiple libraries. The framework handles cron jobs, pub/sub messaging, websockets, and dynamic log level adjustment without restarts. It generates Swagger documentation and provides abstracted file system access. Developers should adopt it if they value a cohesive, opinionated stack over picking individual components, though the framework remains capable of building generic applications despite its microservice focus.

The project maintains active development with regular updates and engagement across multiple communication channels. The codebase demonstrates high code coverage and maintainability standards. The team actively documents features through comprehensive guides and API documentation. Community participation is supported through Discord and question-answering platforms, indicating ongoing investment in developer experience.