Patterns on Bits, Trades & Systems https://blog.turboawesome.win/tags/patterns/ Recent content in Patterns on Bits, Trades & Systems Hugo en-us Wed, 10 Jul 2024 09:38:00 +0000 LLM Integration Patterns for Backend Engineers https://blog.turboawesome.win/2024/07/llm-integration-patterns-for-backend-engineers/ Wed, 10 Jul 2024 09:38:00 +0000 https://blog.turboawesome.win/2024/07/llm-integration-patterns-for-backend-engineers/ Integrating LLMs into backend systems requires engineering discipline that the AI ecosystem tutorials often skip. Structured output, function calling, retry strategy, and testing patterns from production. Building Reliable Pipelines with Go: Retry, Circuit Breaker, and Backoff https://blog.turboawesome.win/2021/11/building-reliable-pipelines-with-go-retry-circuit-breaker-and-backoff/ Wed, 17 Nov 2021 11:41:00 +0000 https://blog.turboawesome.win/2021/11/building-reliable-pipelines-with-go-retry-circuit-breaker-and-backoff/ Every service that calls another service will eventually face failures. The patterns that contain those failures — retry with backoff, circuit breakers, bulkheads — are not optional for production Go services. Here's how to implement them correctly. Go 1.18 Generics: Real Use Cases Worth the Complexity https://blog.turboawesome.win/2021/04/go-1.18-generics-real-use-cases-worth-the-complexity/ Wed, 07 Apr 2021 10:29:00 +0000 https://blog.turboawesome.win/2021/04/go-1.18-generics-real-use-cases-worth-the-complexity/ Go 1.18 shipped generics and the ecosystem immediately split between 'finally' and 'we didn't need this.' After using them in production code, here are the cases where generics genuinely simplify things and the cases where they add complexity for no gain. Error Handling in Go: Patterns That Actually Work at Scale https://blog.turboawesome.win/2019/09/error-handling-in-go-patterns-that-actually-work-at-scale/ Wed, 11 Sep 2019 11:58:00 +0000 https://blog.turboawesome.win/2019/09/error-handling-in-go-patterns-that-actually-work-at-scale/ Go's error handling is explicit and verbose by design. At scale — hundreds of functions, multiple layers, concurrent operations — the naive patterns break down. These are the patterns that held up. Channels vs Mutexes: When to Use Which in Go https://blog.turboawesome.win/2019/08/channels-vs-mutexes-when-to-use-which-in-go/ Wed, 07 Aug 2019 10:22:00 +0000 https://blog.turboawesome.win/2019/08/channels-vs-mutexes-when-to-use-which-in-go/ Go's concurrency slogan is 'share memory by communicating.' It's good advice but incomplete. Some problems are better solved with a mutex than a channel. A decision framework with concrete examples.