<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strategy on Go Micro</title><link>https://go-micro.dev/tags/strategy.html</link><description>Recent content in Strategy on Go Micro</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 29 Jul 2026 08:42:34 +0100</lastBuildDate><atom:link href="https://go-micro.dev/tags/strategy/index.xml" rel="self" type="application/rss+xml"/><item><title>Going All In on AI</title><link>https://go-micro.dev/blog/2026/06/04/going-all-in-on-ai.html</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://go-micro.dev/blog/2026/06/04/going-all-in-on-ai.html</guid><description>&lt;p&gt;I started Go Micro in 2015 because building microservices in Go was too hard. Too much boilerplate, too many decisions before you could test a single endpoint. The idea was simple: sane defaults, pluggable architecture, get out of the developer&amp;rsquo;s way.&lt;/p&gt;
&lt;p&gt;Eleven years later, the framework works. Service discovery, RPC, pub/sub, config, store — all pluggable, all production-tested. 23,000 stars on GitHub. But let&amp;rsquo;s be honest: the microservices ecosystem moved on. Kubernetes won infrastructure. gRPC became the default transport. Service meshes handle the network. The problems Go Micro originally solved are mostly solved.&lt;/p&gt;</description></item></channel></rss>