# go-dev-frame/sponge

A powerful and easy-to-use Go development framework that enables you to effortlessly build stable, reliable, and high-performance backend services with a "low-code" approach.

Repository: https://github.com/go-dev-frame/sponge
Canonical: https://ross.abutalabs.com/products/go-dev-frame-sponge
Homepage: https://go-sponge.com
Language: Go
License: MIT
License Family: permissive
Topics: gin, grpc, web, cloud-native, code-generation, low-code, microservice, go-sponge, sponge, custom-templates, developer-tools, grpc-gateway, restful-api, ai-assistant, ai-generated-code, development-framework, protobuf
Last push: 2025-12-15T13:00:56+00:00

## Health v2 (maintenance only)
Score: 67/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 57, release rhythm 61, longevity 100
- inputs: {"age_days": 1444, "days_push": 261, "days_rel": 261, "gap_med": 15.0, "n_releases_24m": 27}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2862, forks 270 (observed 2026-08-28T04:07:26.277160+00:00)

## What it is
Sponge is a Go development framework built on a 'Definition is Code' philosophy that generates modular backend code from SQL, Protobuf, and JSON definitions. It integrates Gin and gRPC with a code generation engine to build RESTful APIs, gRPC services, and microservice clusters with a low-code approach.

## Use cases
- generate a restful api service from a sql schema
- build grpc microservices in go with less boilerplate
- scaffold crud endpoints for a mysql database
- create a grpc gateway exposing both http and grpc
- generate go backend project with api docs and deployment configs
- use ai to generate business logic code in a go service
- build a monolith that can be split into microservices later

## When to choose
- starting a new Go backend service and wanting generated CRUD, routing, and docs out of the box
- building RESTful, gRPC, or hybrid HTTP+gRPC services on the Gin/GORM/gRPC stack
- teams wanting standardized architecture and a full lifecycle toolchain from generation to deployment
- reducing repetitive boilerplate in microservice development

## When to avoid
- maintaining an existing codebase with an established framework or architecture
- projects requiring full manual control over generated code structure or non-standard stacks
- non-Go projects or lightweight scripts where a full framework is overkill

## Facets
- artifact type: framework
- maturity: active
- function: web-framework, api-framework, rpc, developer-tools, middleware, orm, documentation, deployment
- domain: web-development, backend, developer-tools, microservices, apis
- platform: go, windows, cross-platform
- tags: low-code, code-generation, gin, grpc, grpc-gateway, protobuf, restful-api, microservices, ai-assisted, crud-generation, monolith, service-governance, automation, linux, macos, docker, kubernetes

## Member repositories
- go-dev-frame/sponge (main) score 67

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:26.277160+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:36:22.041154+00:00, confidence not recorded.
  - readme: https://github.com/go-dev-frame/sponge (fetched 2026-08-28T04:07:26.277160+00:00, sha c7a2b7cc6d28)
  - homepage: https://go-sponge.com (fetched 2026-08-29T09:52:00.437269+00:00, sha d8e8116aef81)
  - site_page: https://go-sponge.com/getting-started/overview.html (fetched 2026-08-29T09:52:00.439668+00:00, sha 292a615ffeaf)
- Data as of 2026-08-30T08:39:29.467469+00:00.