BoGO is shaking up back-end bootstrapping by generating a complete Go backend directly from SQL. Write your tables or queries, run the generator, and you get models, repository code, API handlers, and a ready-to-run project—no boilerplate needed. The pitch: move fast, explore architecture, and prototype APIs with a clean, production-ready structure. [1]
With BoGO, the SQL-first approach maps schemas straight into production-grade code, aiming to cut hand-typed boilerplate and speed up learning how SQL translates to real apps. It’s being compared to sqlc and oapi-codegen by early adopters, signaling a shift toward more automated code creation. [1]
Android migrations debate — a mobile take on the same problem shows how migrations live on devices. The idea is a Gradle plugin that brings Prisma-style migrations to Android, auto-detects schema changes from your models, and generates safe migration SQL with rollback and dry-run. It also aims to validate migrations in CI/CD and visualize schema evolution, while integrating with Room or SQLDelight. [2]
- Prisma-style migrations for Android [2]
- Auto-detect schema changes from your models [2]
- Generate safe migration SQL with rollback + dry-run [2]
- Validate migrations in CI/CD and visualize schema evolution [2]
- Integrate with Room or SQLDelight [2]
If SQL-driven scaffolding keeps gaining ground, CI/CD and deployment pipelines could pivot from hand-written code to SQL-first automation, challenging traditional codegen approaches and keeping teams on track with rapid iteration. [1][2]
References
Show HN: BoGO – Generate Go back end services directly from SQL files
BoGO generates models, repository code, and API scaffolding from SQL schema; compares to sqlc and oapi-codegen; seeks feedback and iterations.
View sourceAsk HN: Would you use an auto-migration ORM for Android apps?
Post weighs hand-writing migrations vs automated Prisma-style migrations; seeks feedback on tooling, CI integration, and headaches
View source