Behind the Scenes: How GoBrunch Adopted WebRTC, Sockets and SVGs
- richardlowenthal6
- Feb 8, 2018
- 1 min read
Updated: Mar 27, 2023

There are several ways to choose a technology for a startup website. We always believed that GoBruch is more than a simple videoconference or webinar platform. It's a promising community to share knowledge. In one hand, we wanted to avoid using paid SaaS, since this was going to be a free website. In the other, we were studying different possibilities to implement sockets through the web pages, with multi-tab capabilities. We ended up choosing node.js as the back-end server, including all sockets management. The technology used for the live video in the browser (called WebRTC) is quite new, dated from 2009. There is a huge lack of information online, which made us to rethink the architecture many times, guided by the promise to cover large audiences. After some study, we chose one of the few available frameworks and customized it a lot, in order to work following the Selected Forwarded Unit concept. Thinking about providing a different virtual experience to the user, we also explored a wide range of features offered by SVG (Scaled Vector Graphics), including the possibility to allow the user to choose a "seat" in a meeting room. Check the results at https://gobrunch.com
_edited.png)



I've been wondering about the decision-making process behind choosing certain technologies for a startup, especially when you aim to foster a community, like in the case of GoBrunch. It's interesting to ask how the balance between open-source solutions and custom development impacts user experience in a platform like this. I noticed something similar with another project I came across recently, which also highlighted the challenges of utilizing newer tech while trying to maintain scalability—like those found at https://fox-slots-casino.com/. What do you all think are the most crucial factors to consider when selecting tech for community-driven platforms?