<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - RMI - アーティクル</title>
    <link>https://www.infoq.com/jp</link>
    <description>InfoQ RMI アーティクル フィード</description>
    <item>
      <title>アーティクル: RMIベースのレガシー・アプリケーションをWebSocketに移行する</title>
      <link>https://www.infoq.com/jp/articles/rmi-to-websocket/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=RMI-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/rmi-to-websocket/ja/headerimage/migrate-a-RMI-based-legacy-application-to-WebSocket-header-1680106723513.jpg"/&gt;&lt;p&gt;Technical debt, especially in enterprise software, is a relevant problem that developers recurrently have to face. This article provides a use case related to removing technical debt in a large enterprise application based on an old fashioned Remote Method Invocation (RMI) protocol, and migrating it toward modern cloud-aware communication technologies.&lt;/p&gt; &lt;i&gt;By Bartolomeo Sorrentino&lt;/i&gt; &lt;i&gt; Translated by Takashi Kawase&lt;/i&gt;</description>
      <category>Java</category>
      <category>RMI</category>
      <category>設計/アーキテクチャ</category>
      <category>デベロップメント</category>
      <category>DevOps</category>
      <category>アーティクル</category>
      <pubDate>Tue, 16 Jan 2024 07:31:00 GMT</pubDate>
      <guid>https://www.infoq.com/jp/articles/rmi-to-websocket/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=RMI-articles</guid>
      <dc:creator>Bartolomeo Sorrentino</dc:creator>
      <dc:date>2024-01-16T07:31:00Z</dc:date>
      <dc:identifier>/articles/rmi-to-websocket/ja</dc:identifier>
    </item>
  </channel>
</rss>
