Developer Advocate
Technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.
Markdown supported · ⌘↵ to post
Kyllie
Great breakdown, Nicolas! 👏 The way you explained cookie-based routing in APISIX with the traffic-split plugin and priorities makes it much easier to understand for newcomers. I especially liked how you simplified the example from 10:90 to 50:50 for testing — that’s practical advice most developers can follow step by step.
One thing I find very useful in real-world scenarios is combining this approach with A/B testing or gradual rollouts, where weighted upstreams help you safely introduce new features. Your explanation of using cookies to keep routing consistent after the first request is exactly what many production setups need.
Thanks for sharing such a clear guide — this definitely helps anyone exploring smart routing with APISIX.