<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - API - アーティクル</title>
    <link>https://www.infoq.com/jp</link>
    <description>InfoQ API アーティクル フィード</description>
    <item>
      <title>アーティクル: APIデザインレビューは死んだ。APIデザインレビュー万歳！</title>
      <link>https://www.infoq.com/jp/articles/api-design-review/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=API-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/api-design-review/ja/headerimage/API-design-reviews-are-dead-long-live-API-design-reviews-header-1684310900854.jpg"/&gt;&lt;p&gt;To design APIs at scale, it takes deliberate effort to create consistency and make several discrete APIs feel like a platform.  This requires an efficient and useful API design review process.&lt;/p&gt; &lt;i&gt;By Jason Harmon&lt;/i&gt; &lt;i&gt; Translated by Tetsuya Hanakawa&lt;/i&gt;</description>
      <category>設計</category>
      <category>API</category>
      <category>Architecture</category>
      <category>設計/アーキテクチャ</category>
      <category>アーティクル</category>
      <pubDate>Thu, 14 Dec 2023 04:30:00 GMT</pubDate>
      <guid>https://www.infoq.com/jp/articles/api-design-review/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=API-articles</guid>
      <dc:creator>Jason Harmon</dc:creator>
      <dc:date>2023-12-14T04:30:00Z</dc:date>
      <dc:identifier>/articles/api-design-review/ja</dc:identifier>
    </item>
  </channel>
</rss>
