<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Windranger Labs - Medium]]></title>
        <description><![CDATA[windranger.io - Medium]]></description>
        <link>https://medium.com/windrangerlabs?source=rss----1b10b725ed62---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Windranger Labs - Medium</title>
            <link>https://medium.com/windrangerlabs?source=rss----1b10b725ed62---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:16:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/windrangerlabs" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Review of Discourse deployment strategies]]></title>
            <link>https://medium.com/windrangerlabs/review-of-discourse-deployment-strategies-e93ed57a0954?source=rss----1b10b725ed62---4</link>
            <guid isPermaLink="false">https://medium.com/p/e93ed57a0954</guid>
            <category><![CDATA[bitdao]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[cost-analysis]]></category>
            <category><![CDATA[discourse]]></category>
            <dc:creator><![CDATA[CJ Hare]]></dc:creator>
            <pubDate>Mon, 05 Sep 2022 19:20:41 GMT</pubDate>
            <atom:updated>2022-09-07T12:04:45.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WdcqmI-9EOCSdov9BKTkUg.jpeg" /></figure><p>An analysis on strategies for providing a Discourse forum service.</p><p>Evaluating four different strategies, implemented in three of the major cloud players, providing data with pros, cons and costs of each.</p><p>All the interesting investigation work and primary authoring credit goes to <a href="https://medium.com/u/7525b6ae4e78">Luis Fernando Laimer</a></p><h3>Introduction</h3><p>Many companies rely on a good forum tool in order to improve communication with customers and communities. A forum enables people to create discussion topics and collectively contribute with ideas, votes and comments in order to improve the topic.</p><p>Although a simple concept, a good forum application requires features in order to enable a good communication flow and sharing of ideas. These features include, identity management, content management, tagging, analytics, attaching, notifications, a good UI/UX, community moderation, social media integration, digests and many other features that significantly increase the complexity of this kind of tool.<br>As most companies do not have the bandwidth to develop a tool with that many features, adopting an existing tool becomes almost a natural path for a great majority. Also, maintaining a forum server requires maintenance, such as updates, and managing backups which can be overwhelming for smaller organizations.</p><p>There are a considerable number of forum apps available in the market. Discourse, Flarum, Kialo, NodeBB, FluxBB, MyBB and several others, most of it open-source and free.</p><p>To make it even better, some of the alternatives also include a paid SaaS version of the forum, so companies do not have to manage infrastructure and maintain the tool.</p><p>For the purpose of this post, we will take a better look at the Discourse as a forum product, since it is the most widely used on the web3 ecosystem, and will do a deep dive into a few different deployment scenarios for this tool.</p><h3>About Discourse</h3><p>Discourse is one of the most complete forum solutions available in the market. It is open-source, but also has the option to be purchased as a SaaS. It covers multiple languages, SEO, an impressive number of administration features, a good user interface, lots of flexibility through different plug-ins available. Overall it is a great solution.</p><p>Discourse is written in Ruby and uses PostgreSQL and Redis. Redis is used specifically for live page updates, Rails cache, distributed rate limit and internal semaphore system, while PostgreSQL is widely used for meta, configs and content storage. MailHog is also used to interface with email servers (this one needs to be set up by the user).</p><p>All these components are normally configured through a bash script that packs them into a Docker container. The script also has the option for creating two Docker images to both execute on a single Docker client.</p><p>To improve performance using a CDN, it’s a standard CDN configuration with a single entry in the Discourse YAML config file.</p><h3>Deploying Discourse</h3><p>Although Discourse can be easily deployed using the setup script, there are a few important points of attention when running this installation:</p><ul><li>There is no redundancy on the system. If your machine, your Docker or your container go down, your forum will be unavailable.</li><li>There is no native monitoring in the solution deployed via script</li></ul><p>If availability is something crucial for your forum service, and you have a high SLA associated with it, it might be a good idea to start to think about redundancy.</p><p>I can think in a couple of options that can be explored when looking for a high availability architecture:</p><ul><li>Deploy Discourse into Kubernetes.</li><li>Deploy Discourse using multiple hosts and an Application Load Balancer.</li><li>Purchase SaaS service from Discourse.</li></ul><p>In this post we will take a look at each one of these scenarios and compare the pros, cons and costs (as of Aug 2022). We will also compare with deploying to a single host using the provided configuration script.</p><p><em>(* denotes the provider recommended email solution)</em></p><h3>Strategy: Kubernetes</h3><p>Kubernetes is an open-source container orchestration system for automating software deployment, scaling, and management. Kubernetes dramatically increases the availability of container based applications. In order to deploy Discourse using Kubernetes, we require a Kubernetes cluster, a Network Storage and a Database server (PostgreSQL)</p><p>Pros:</p><ul><li>Extremely reliable solution</li><li>Very easy to maintain</li><li>Easy to implement CI/CD using Infrastructure as Code</li><li>Simplified monitoring and logging solution.</li><li>Email service can be deployed without extra cost (i.e. Mailu)</li><li>No limits on views</li></ul><p>Cons:</p><ul><li>Kubernetes is a very complex system and requires specialized knowledge to operate</li><li>Cost can be a lot higher if you are not sharing this cluster with multiple applications</li><li>Kubernetes was designed to work with microservices. Anything that maintain state on disk can be a challenge and will require better tunning to extract good performance</li><li>Still have the cost of the external database.</li></ul><p><strong>Cost comparison:</strong></p><p>In order to add some perspective into costs for this scenario, we have an estimate of the scenario in each of the main Cloud Services (AWS, GCP and Azure)</p><p><strong>AWS:</strong></p><ul><li>EKS Managed service</li><li>2x workers 2vCPU 16GB</li><li>RDS PostgreSQL 2vCPU 7.5GB</li></ul><p>Price/month: U$547.84</p><p><strong>GCP:</strong></p><ul><li>GKE Cluster Management</li><li>2x workers 2vCPU 16GB</li><li>CloudSQL PostgreSQL 2vCPU 7.5GB</li></ul><p>Price/month: U$452.42</p><p><strong>Azure:</strong></p><ul><li>AKS Management</li><li>2x workers 2vCPU 16GB</li><li>Azure Database for PostgreSQL</li></ul><p>Price/month: U$480.10</p><h3>Strategy: Multiple hosts</h3><p>Another valid alternative would be to create multiple hosts, in different zones and use an application load balancer to distribute traffic.</p><p><strong>Pros:</strong></p><ul><li>Good availability</li><li>It is possible implement CI/CD</li><li>Less complex approach than Kubernetes</li><li>No limits on views</li></ul><p><strong>Cons:</strong></p><ul><li>Requires external Postgres and Redis</li><li>Not as flexible as Kubernetes</li><li>Slightly more expensive than using a Kubernetes solution</li><li>Requires monitoring and centralized log solution</li><li>Requires email service</li></ul><p><strong>Cost Comparison breakdown:</strong></p><p><strong>AWS:</strong></p><ul><li>2x vm 2vCPU 16GB</li><li>Amazon MemoryDB for Redis</li><li>RDS PostgreSQL 2vCPU 7.5GB</li><li>Elastic Load Balancer</li><li>Simple Email Service (SES)</li></ul><p>Price/month: 588.37</p><p><strong>GCP:</strong></p><ul><li>2x vm 2vCPU 16GB</li><li>CloudSQL PostgreSQL 2vCPU 7.5GB</li><li>Memory store for Redis</li><li>Cloud Load Balancing</li><li>1x VM 2vCPU 8GB RAM (Sendgrid, Mailgun or Jetmail images available for free)*</li></ul><p>Price/month: U$401.80</p><p><strong>Azure:</strong></p><ul><li>2x vms 2vCPU 16GB</li><li>Azure Database for PostgreSQL</li><li>Azure Cache for Redis</li><li>Load Balancer</li><li>SocketLabs Core subscription (for email relay)*</li></ul><p>Price/month: U$583.51</p><h3>Strategy: Discourse SaaS</h3><p>The Discourse offers a paid product as a SaaS.</p><p>Pros:</p><ul><li>Very low complexity to set up</li><li>Low maintenance overhead</li><li>Very good availability</li><li>Multiple tiers, which makes it the cheapest option</li></ul><p>Cons:</p><ul><li>Data hosted outside your environment</li><li>Increase in use may incur in a larger price</li></ul><p>Cost comparison:</p><p><strong>Standard</strong>:</p><ul><li>100k month views</li><li>20GB storage</li><li>5 staff accounts</li></ul><p>Price/month: U$100.00</p><p><strong>Business</strong>:</p><ul><li>500K month views</li><li>100GB storage</li><li>15 staff accounts</li></ul><p>Price/month: U$300.00</p><h3>Strategy: Single host</h3><p>In this case, a single machine is used to run the containers from Discourse.</p><p><strong>Pros:</strong></p><ul><li>Low complexity setup</li><li>Data ownership</li><li>No limits on views</li></ul><p><strong>Cons:</strong></p><ul><li>No fail-over architecture, which means that if machine, docker or discourse goes down, forum will become unavailable</li><li>Requires monitoring and centralized log solution</li><li>Requires email service</li></ul><p><strong>Price comparison:</strong></p><p><strong>AWS:</strong></p><ul><li>1x VM 4 vCPU 32GB</li><li>Simple Email Service (SES)</li></ul><p>Price/month: U$175.17</p><p><strong>GCP:</strong></p><ul><li>1x VM 4 vCPU 32GB</li><li>1x VM 2vCPU 8GB RAM (Sendgrid, Mailgun or Jetmail images available for free)*</li></ul><p>Price/month: U$180.96</p><p><strong>Azure:</strong></p><ul><li>1x VM 4 vCPU 32GB</li><li>SocketLabs Core subscription (for email relay)*</li></ul><p>Price/month: U$ 244.45</p><h3>Summary</h3><p>Each proposed scenario has strengths and weaknesses.</p><p>As an example, if you already own a Kubernetes cluster running other systems, this might be the best cost benefit for you to deploy Discourse, since the cost will be diluted with multiple applications.</p><p>Looking at the table below we can have a good comparison between the costs of many different strategies/providers.</p><pre>    :-----------------+-----------+---------:<br>    | Strategy        |           | USD$    |<br>    :-----------------+-----------+---------:<br>    | Kubernetes      | AWS       | 547.84  |<br>    |                 | GCP       | 452.42  |<br>    |                 | AZURE     | 480.10  |<br>    |-----------------+-----------+---------|<br>    | Multiple Hosts  | AWS       | 588.37  |<br>    |                 | GCP       | 401.80  |<br>    |                 | AZURE     | 583.51  |<br>    |-----------------+-----------+---------|<br>    | Single Host     | AWS       | 175.19  |<br>    |                 | GCP       | 180.96  |<br>    |                 | AZURE     | 244.45  |<br>    |-----------------+-----------+---------|<br>    | SaaS            | Standard  | 100.00  |<br>    |                 | Business  | 300.00  |<br>    &#39;-----------------&#39;-----------&#39;---------&#39;</pre><ul><li>In the case your Discourse data cannot be hosted in a 3rd party either because of compliance or because of security concerns (some compliances will require that the 3rd party have an appropriate security certification)</li><li>In the case your forum has a huge amount of access, this would bump the price from SaaS significantly. In this case you will require to choose between multiple hosts or Kubernetes (considering that in this case, SLA will most likely be an important factor for your business)</li></ul><p>For the SaaS product, we can have a less expensive, low complexity forum, with no maintenance costs. It is crucial here data storage management and control over crawlers and web spiders access, since this could easily bump your tier from Standard to Business.</p><p>Overall the SaaS should cover most of the needs for the majority of small to medium size organizations.</p><h3>Conclusion</h3><p>This study enabled the Windranger team to make a decision regarding our current choice of Discourse deployment strategy. After analyzing the data, a decision was made to transition from a single host strategy into a SaaS strategy for the forum discourse.bitdao.io, since this option was better in many different aspects such as maintenance, availability and cost.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e93ed57a0954" width="1" height="1" alt=""><hr><p><a href="https://medium.com/windrangerlabs/review-of-discourse-deployment-strategies-e93ed57a0954">Review of Discourse deployment strategies</a> was originally published in <a href="https://medium.com/windrangerlabs">Windranger Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Windranger Hosts Official Hacker House at EthCC in Paris]]></title>
            <link>https://medium.com/windrangerlabs/windranger-hosts-official-hacker-house-at-ethcc-in-paris-5d58786aad7e?source=rss----1b10b725ed62---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d58786aad7e</guid>
            <dc:creator><![CDATA[Windranger Labs]]></dc:creator>
            <pubDate>Tue, 16 Aug 2022 16:49:31 GMT</pubDate>
            <atom:updated>2022-08-16T16:52:50.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*xgGFy_8nfXJ7iG-3Z-RMJw.png" /></figure><p>The Windranger Hacker House at EthCC was the latest in a series of <a href="https://twitter.com/BitDAO_Official">BitDAO</a>-sponsored events to support the work of exceptional builders and foster a multidimensional ecosystem for imagining and creating the future of a decentralized world.</p><p>23 developers participated in this iteration of our hacker house series. Participation was invite-only and merit-based, and included some of the most talented builders in the web3 space including four members of our ecosystem partner <a href="https://www.edudao.io/">EduDAO</a>.</p><p>Programming included networking events, round table discussions, and real-time collaborations.</p><p>The roundtables were organized in partnership with <a href="https://daohaus.club/">DAOHaus</a> and <a href="https://docs.flashbots.net/">Flashbot</a> and focused on topics pertinent to <a href="https://github.com/windranger-io/public-docs">BitDAO Prompts</a> and Hacker interests. Our first roundtable, in partnership with DAOHaus, was led by @<a href="https://twitter.com/0xJoshuaSL">0xJoshuaSL</a>, @<a href="https://twitter.com/spengrah">spengrah</a>, @<a href="https://twitter.com/0xBillW">0xBillW</a>, @<a href="https://twitter.com/CryptononymousE">CryptononymousE</a>. <a href="https://twitter.com/WindrangerLabs/status/1550310898505490432?s=20&amp;t=T8EYEeQqw1sxsJSDB6BgCw">The DAOHaus team guided us through new, promising tools in the DAO ecosystem</a> and provided deep insight about some of the critical issues in the DAO tooling space. We also discussed methods for more effectively distributing administrative power across DAO contributors, ensuring accountability and compliance within a decentralized community to reduce risk for token holders, and distributing responsibilities and influence.</p><p>The second roundtable, organized in partnership with Flashbots featured:</p><ul><li>Tarun Chitra: <em>Even rotten sandwiches can taste good once in a while</em></li><li>Patrick McCorey: <em>MEV and Censorship-resistance</em></li><li>Zaki Manian: <em>IBC MEV</em></li><li>Chris Goes: <em>Cross-domain MEV and the crucial conundrum of proposer selection</em></li><li>Barnebe Monnot: <em>Relays in MEV-boost</em></li><li>thegostep &amp; Mateusz: <em>MEV-boost deep dive with builders workshop</em></li><li>Vlad Zamfir: <em>PBS is impossible! I’ve got beef with PBS!</em></li></ul><p>Hackers were excited by the connections made and resources provided by the Flashbots team and their collaborators. Many commented on the unprecedented level of access they were allowed to areas of research and development produced by the builders they are actively following.</p><p>Beyond the roundtables, the house activities developed organically. Some participants hosted impromptu workshops on solidity, and <a href="https://twitter.com/LucemansNL">@lucemansnl</a> and Timothy Guo created an on-chain tic tac toe game together “tic tac so” deployed on Matic mainnet. They partnered with our lead dev and mentor <a href="https://twitter.com/afk0b">AFK</a> to debug their smart contracts and organized a ‘tic tac so’ tournament in the house. It’s still live. Head to <a href="https://tictac.so/welcome">https://tictac.so/welcome</a> to play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/0*CLuE98D1FnTKJ19j" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/0*HCjgfUNNY5NqbYft" /></figure><p>In general, the hacker house was a big success. We deepened relationships with builders and partners, we supported builders as they expanded their knowledge base and facilitated social introductions that will become future collaborations. Participants reported deriving value from the structure that was largely built to suit their areas of interests and met individuals they admired to discuss papers that influenced them, including Vitalik Buterin.</p><p>The BitDAO ecosystem reaches across web3 to build and hosts communities ranging from deep Ethereum research to venture capital. We are eager to connect builders with our resources and are focused on meeting them where they are to find the support they need to grow their work. We look forward to continuing to scaffold the success of dedicated builders in the space.</p><p>Follow our Twitter <a href="https://twitter.com/BitDAO_Official">@BitDAO_Official</a> to stay updated on our upcoming hacker houses and other programming. We hope to see you there.</p><p>Special thanks to all of the amazing developers and staff who shaped the Windranger Hacker House at EthCC!</p><p>Partners: <a href="https://daohaus.club/">@DAOHaus</a>, <a href="https://docs.flashbots.net/">@Flashbots</a> and <a href="https://www.edudao.io/">@EduDAO</a></p><p>Developers: @<a href="https://twitter.com/BrandonSeverin">BrandonSeverin</a>, @<a href="https://twitter.com/jessicapointing">jessicapointing</a>, @<a href="https://twitter.com/MaanavKhaitan">MaanavKhaitan</a>, @<a href="https://twitter.com/VagariViatorem">VagariViatorem</a>, @<a href="https://twitter.com/Eito_Miyamura">Eito_Miyamura</a>, @<a href="https://twitter.com/jrcarlos2000">jrcarlos2000</a>, @<a href="https://twitter.com/m1guelpf">m1guelpf</a>, @<a href="https://twitter.com/ChundaMcCain">ChundaMcCain</a>, @<a href="https://twitter.com/LucemansNL">LucemansNL</a>, @<a href="https://twitter.com/timg51237">timg51237</a>, @<a href="https://twitter.com/atris_eth">atris_eth</a>, @<a href="https://twitter.com/GrindalSean">GrindalSean</a>, @<a href="https://twitter.com/juanbugeth">juanbugeth</a>, @<a href="https://twitter.com/skyler_chan_">skyler_chan_</a>, @<a href="https://twitter.com/figmasimp">figmasimp</a>, and 8 anons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d58786aad7e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/windrangerlabs/windranger-hosts-official-hacker-house-at-ethcc-in-paris-5d58786aad7e">Windranger Hosts Official Hacker House at EthCC in Paris</a> was originally published in <a href="https://medium.com/windrangerlabs">Windranger Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>