<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Qwen on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/qwen/</link><description>Recent content in Qwen on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 07 May 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/qwen/index.xml" rel="self" type="application/rss+xml"/><item><title>Alibaba Cloud Full Stack (10): Bailian and DashScope — The LLM Layer</title><link>https://www.chenk.top/en/aliyun-fullstack/10-bailian-llm/</link><pubDate>Thu, 07 May 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-fullstack/10-bailian-llm/</guid><description>&lt;p>When I first needed an LLM API for a production app in China, my options were limited and expensive. Most international providers had no mainland endpoint, billing required a foreign credit card, and latency from calling US-based APIs was 800ms+ before a single token came back. Then Qwen showed up on DashScope with an OpenAI-compatible endpoint, and suddenly building AI products in China became as straightforward as anywhere else. Same SDK, same request shape, same streaming protocol — just a different &lt;code>base_url&lt;/code> and a key from the Bailian console. I have been running production workloads against it for over a year now, and this article is the comprehensive walkthrough I wish I had on day one.&lt;/p></description></item><item><title>Aliyun Bailian (2): The Qwen LLM API in Production</title><link>https://www.chenk.top/en/aliyun-bailian/02-qwen-llm-api/</link><pubDate>Thu, 26 Feb 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-bailian/02-qwen-llm-api/</guid><description>&lt;p>This article in the series covers most of the production wins. While the other models are interesting, the LLMs are what every product I&amp;rsquo;ve shipped on Bailian calls every minute of every day. The official Qwen API reference is dense and complete; this article is the readable companion that guides you through it.&lt;/p>
&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/aliyun-bailian/02-qwen-llm-api/illustration_1.png" alt="Aliyun Bailian (2): The Qwen LLM API in Production — Chapter overview" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p>
&lt;hr>
&lt;h2 id="pick-the-right-qwen-variant-for-the-workload" class="heading-anchor">Pick the right Qwen variant for the workload&lt;a href="#pick-the-right-qwen-variant-for-the-workload" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>The Qwen family is large. Some teams overspend by defaulting to &lt;code>qwen-max&lt;/code> everywhere; others underspend on quality by defaulting to &lt;code>qwen-turbo&lt;/code>. The right answer is &amp;ldquo;match variant to job&amp;rdquo;:&lt;/p></description></item></channel></rss>