<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rolando Santamaría Masó</title>
    <description>The latest articles on DEV Community by Rolando Santamaría Masó (@kyberneees).</description>
    <link>https://dev.to/kyberneees</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1576013%2F84b034bc-bbe6-4cc8-9e7e-db7bdd950223.png</url>
      <title>DEV Community: Rolando Santamaría Masó</title>
      <link>https://dev.to/kyberneees</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kyberneees"/>
    <language>en</language>
    <item>
      <title>Realtime Pub/Sub meets Amazon SQS Elasticity</title>
      <dc:creator>Rolando Santamaría Masó</dc:creator>
      <pubDate>Tue, 04 Jun 2024 18:37:49 +0000</pubDate>
      <link>https://dev.to/kyberneees/realtime-pubsub-meets-amazon-sqs-elasticity-480k</link>
      <guid>https://dev.to/kyberneees/realtime-pubsub-meets-amazon-sqs-elasticity-480k</guid>
      <description>&lt;p&gt;In this blog post, we will explore one standout feature: real-time message forwarding to Amazon SQS queues.&lt;br&gt;
We’ll delve into the details and provide a hands-on example of how to process and respond to your WebSocket clients requests using an Amazon SQS queue as a proxy layer between your application clients and the backend services.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fjvy3xmjy4li24ubg4qr8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fjvy3xmjy4li24ubg4qr8.png" alt="Image description" width="800" height="908"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@kyberneees/realtime-pub-sub-meets-amazon-sqs-elasticity-150cb2ac1df6"&gt;https://medium.com/@kyberneees/realtime-pub-sub-meets-amazon-sqs-elasticity-150cb2ac1df6&lt;/a&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>sqs</category>
      <category>messaging</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Authenticate Realtime Pub/Sub WebSocket clients with Supabase</title>
      <dc:creator>Rolando Santamaría Masó</dc:creator>
      <pubDate>Tue, 04 Jun 2024 18:34:41 +0000</pubDate>
      <link>https://dev.to/kyberneees/authenticate-realtime-pubsub-websocket-clients-with-supabase-59ko</link>
      <guid>https://dev.to/kyberneees/authenticate-realtime-pubsub-websocket-clients-with-supabase-59ko</guid>
      <description>&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fx5d7a45qd3u6euc1vbp8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fx5d7a45qd3u6euc1vbp8.png" alt="Image description" width="800" height="514"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In this blog post, we describe how to authenticate your Realtime Pub/Sub Application WebSocket clients using Supabase users.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@kyberneees/authenticate-realtime-pub-sub-websocket-clients-with-supabase-ed538a5eb47d"&gt;https://medium.com/@kyberneees/authenticate-realtime-pub-sub-websocket-clients-with-supabase-ed538a5eb47d&lt;/a&gt;&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>realtime</category>
      <category>messaging</category>
      <category>authentication</category>
    </item>
  </channel>
</rss>
