Go Full Stack Server-Side Rendering vs SPAs - Fernando J. Villamarin Diaz, JPMC

Over the past year, we've witnessed an exciting shift in the development community: front-end logic is merging into the back-end, converging neatly within the Go ecosystem. We're talking full-stack capabilities with server-side rendering via Templ and a dash of HTMX for interactivity. Creating a complete full stack application solely in Go? Sounds awesome!

In this talk, we'll delve into how this integrated Go approach stacks up against the traditional model of APIs with JavaScript-based SPAs. We'll focus particularly on performance, exploring how each architecture adapts to various scenarios. For instance, with server-side rendering like Go + Templ, HTML pages can be more substantial than the JSON responses typical in SPAs, which could challenge performance under limited bandwidth conditions.

We'll also dive deep into scalability. Understanding how each setup expands as user numbers increase is crucial. We'll explore the scalability traits of both server-side rendering and API-driven approaches, examining how they manage loads and what this means for performance during peak usage. To bring this to life, we'll look at cloud-based stress tests and benchmarks to uncover the real costs of scaling up and down.

And let's not overlook caching—a vital component of scalability. Server-side caching often involves storing complete HTML pages or significant chunks, significantly speeding up load times. In contrast, API caching usually focuses on JSON data, providing more precise control over what gets cached and how long it remains. Grasping these differences is key to making informed architectural decisions.
Join me as we unpack these technologies to help you determine which setup might be the better fit for your next project. Whether you're looking to enhance performance under varied network conditions or scale efficiently, this talk aims to equip you with the insights to make savvy choices!