Architectural Blueprint: Scaled Fan-Out Hypermedia BEAM System

This document establishes the official context for your decoupled, multi-region architecture. It is optimized for direct ingestion by AI engineering agents.

1. The Ingress Strategy (The Load Balancer Triad)

Instead of relying on a single edge bottleneck, this setup implements a hierarchical, algorithmic "fan-out" ingress pattern:

• Level 1 (The Global Ingress): A single master Rust Load Balancer intercepts the initial secure client connections, terminates TLS, manages HTTPS negotiation, and enforces protocol compliance.
• Level 2 (The Node Balancers): Two or more discrete, secondary Rust Load Balancers receive the pre-filtered connections from Level 1. Each secondary balancer is assigned to a dedicated physical or remote virtual server instance.
• Level 3 (The Application Target): These Level 2 balancers multiplex clean traffic down to multiple localized Cowboy web server nodes running concurrently within that specific server machine.
• The Supervision Hook: The entire triad—despite sitting in front of your server stacks—is registered directly inside the LFE/BEAM VM supervision tree. Erlang monitors the health of the Rust load balancers, dynamically reviving them if a connection thread panics.

2. Stateless Asymmetric Routing Loop

The network topology utilizes a coordinate-addressing scheme where requests and responses are completely decoupled:

• The Glass Payload: Incoming HTTP upstream requests pass through the thin-pipe load balancers and Cowboy servers. They are instantly dropped into the system as a lightweight payload containing the raw transaction data paired with source metadata identifying the origin client coordinates (the "glass").
• Active-Active Processing: Because the request is a self-contained payload with absolute source coordinates, it can pass through any available node in the cluster without requiring local session sticky routing.
• Dynamic Response Paths: The LFE backend processes the request and generates an HTML response containing a return destination coordinate address. It designates a preferred node to send the Server-Sent Events (SSE) through. If that preferred node is too busy or suffers a hardware fault, the backend seamlessly flips the response to route through any other available node in the grid. Which physical node the traffic goes through does not matter.

3. Wails v3 Window Configuration Model

Because the network topology is fully managed by your load balancers and the BEAM, the desktop wrapper’s sole job is to provide a native system window frame. Unlike Tauri, Wails v3 handles this entirely via programmable Go code rather than a static JSON configuration file, allowing for dynamic runtime environment overrides.

Go Window Blueprint:

package main

import (
	"://github.com"
)

func main() {
	app := application.New(application.Options{
		Name: "Hypermedia Client Shell",
	})

	// Dynamically establish your Level 1 Load Balancer IP/Port
	targetURL := "https://127.0.0.1:YOUR_INGRESS_PORT"

	app.NewWebviewWindowWithOptions(application.WebviewWindowOptions{
		Title:     "LFE Application Frame",
		Width:     1280,
		Height:    800,
		URL:       targetURL,
		Frameless: true, // Removes OS borders so your custom LFE HTML titlebar handles layout drag windows

		// Windows OS specific features (Matches modern Win11/10 UI styles)
		Windows: application.WindowsWindow{
			WindowIsTranslucent: true,
			BackdropType:        application.Mica, // Beautiful native blur behind your app layout
			DisableWindowIcon:   true,
		},

		// macOS specific features
		Mac: application.MacWindow{
			TitleBar:               application.MacTitleBarHidden,
			WindowButtonsInvisible: false, // Keeps native close/minimize buttons but overlays them on your HTML canvas
		},
	})

	app.Run()
}
    

Note on CSS Compatibility: Because Wails hooks directly into the native OS rendering layers (WebView2 on Windows, WebKit on macOS, WebKitGTK on Linux), your single unified frontend codebase requires zero modification. You can use standard CSS styling variables like --wails-draggable: drag directly on your LFE-delivered HTML layout blocks to instantly match your Electron and Tauri drag bar behaviors.