<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with high]]></title><description><![CDATA[A list of topics that have been tagged with high]]></description><link>https://fusionauth.io/community/forum/tags/high</link><generator>RSS for Node</generator><lastBuildDate>Thu, 16 Apr 2026 14:32:13 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/high.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Should I use HA for development?]]></title><description><![CDATA[<p dir="auto">Our HA cloud offerings, outlined on <a href="http://fusionauth.io/pricing" rel="nofollow ugc">fusionauth.io/pricing</a> are aimed at the following use cases:</p>
Large production needs
Reliability required
Higher monthly active users

<p dir="auto">Development doesn't typically fall into any of these :).</p>
<p dir="auto">With HA you get an SLA, a custom URL (<a href="http://auth.example.com" rel="nofollow ugc">auth.example.com</a> instead of <a href="http://example.fusionauth.io" rel="nofollow ugc">example.fusionauth.io</a>) and an architecture capable of handling more users.</p>
<p dir="auto">You might want a custom URL to test your DNS/cookie config. Or you might want to load test (please don't load test with a basic cloud deployment, it won't tell you anything about production performanc).</p>
<p dir="auto">If you want to derisk this early, in both these cases, we recommend standing up a temporary HA instance, applying your configuration, testing, and then tearing down the HA instance.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1280/should-i-use-ha-for-development</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1280/should-i-use-ha-for-development</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>