GoFr: Open-Source Go Framework Bundles Observability and Resilience for Microservices

·1 views

GoFr is an opinionated, open-source Go framework designed specifically for building microservices destined for Kubernetes environments. It ships with built-in structured logging, distributed tracing, and metrics, eliminating the need to stitch together multiple third-party libraries. The framework also includes an HTTP client with circuit breaker support, pub/sub and gRPC integration, database migrations, cron jobs, and health checks out of the box. Developers can adjust log verbosity at runtime without redeploying, a feature that proves useful during incident response. Licensed under Apache-2.0 and listed in the CNCF Landscape, GoFr is actively maintained and available at github.com/gofr-dev/gofr.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Engineering Guide Explains Why QR Codes Fail in the Field and How to Fix Them

A technical guide published on DEV Community outlines the engineering decisions that determine whether a QR code scans reliably in real-world conditions, not just on screen. The piece frames QR codes as input/output systems, where payload size, version, error correction level, and module size must be matched carefully to the physical medium. It explains that the four error correction levels — L, M, Q, and H — offer trade-offs between capacity and damage tolerance, with higher correction increasing module density and reducing effective scanning distance at a fixed print size. The guide warns that a payload near a version boundary can be pushed into a denser, harder-to-scan version by even a single extra URL parameter. Practical recommendations include computing the required version before generating a code and sizing up the physical print area when higher error correction is necessary, such as when overlaying a logo.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds AI Agent in CI Pipeline to Automate Multi-Repo Release Notes

A developer at Entire automated the company's weekly release notes, called Dispatches, by integrating an AI agent named Goose into a GitHub Actions CI pipeline. The task proved far more complex than a similar project built at Block, where a single repository with clean release tags made automation straightforward. Entire's Dispatches span multiple projects with different deployment cadences, feature flags, and mixed public-private visibility, making it difficult to determine which changes were safe to announce. The developer iterated through several approaches, eventually shifting from release-tag-based triggers to a time-window method using the previous Dispatch's publication date to avoid duplicating entries. The pipeline was designed not just to surface what changed, but to assess whether each change had fully shipped, was stable, and was appropriate for public communication.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Dev cuts Next.js CI/CD pipeline from 15 minutes to 4 by fixing artifact bloat

A developer discovered their Azure DevOps pipeline was packaging a 1.2 GB artifact — including full node_modules and source files — despite Next.js already generating a lean 24 MB standalone build directory. The fix involved updating the pipeline to copy only the .next/standalone folder into the deployment zip, shrinking the transferred artifact from 614 MB compressed down to 24 MB. This single change reduced the total pipeline runtime from roughly 15 minutes to about 4 minutes. The developer also added a dedicated /api/health route after finding health checks were hitting auth middleware and returning redirects instead of status responses. A separate cookie-naming bug that caused an infinite sign-in loop locally was resolved by basing the secure cookie prefix on the actual NEXTAUTH_URL protocol rather than NODE_ENV.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build Customer-Aware API Monitoring for B2B SaaS Products

Standard API monitoring tracks error rates and latency by endpoint, but for B2B SaaS platforms, teams also need to know which specific customers and integrations are affected when failures occur. A practical approach involves emitting a small structured event after authentication, capturing fields like customer ID, application ID, API version, SDK version, release tag, and a stable error code alongside the HTTP status and route. This telemetry is kept off the response path to prevent monitoring issues from disrupting the API itself, and sensitive data such as request bodies, credentials, and client IPs are deliberately excluded to limit security and privacy risk. With customer context embedded in observability data, support and engineering teams can quickly rank affected accounts by error count, identify which customers are still on older API versions, and prioritize outreach for high-value or newly onboarding clients. The model treats customer identity as a core dimension of API health rather than an afterthought, making incident response faster and more targeted.

0 comments Read more at DEV Community