Live Lab
Production Rust Systems, Demonstrated Live
I build secure, observable backend systems with typed boundaries. This portfolio runs on the same real auth, Postgres, and SSE stack I ship in production-style projects.
Preview
images/identity-session-surface
Anchor target: Home hero
Identity Context Across Requests
Session-backed authentication keeps request and UI identity aligned over time.
- Registration, login, and protected routes operate on one durable session model.
- Cookie and server session state remain coherent during normal navigation.
- User context is available where handlers and views require it.
- The identity path can be validated directly from public routes.
Preview
images/request-burst-surface
Anchor target: Request burst
Client-Side Burst Driver for Throughput Checks
One control generates high request volume so latency and failures become visible quickly.
- A range input sets request volume before execution starts.
- Parallel workers dispatch traffic from a single browser session.
- Progress shows sent, successful, failed, and requests per second.
- The harness is useful for quick smoke checks after backend changes.
Preview
images/live-chat-surface
Anchor target: Chat demo
Persisted Chat With Multi-Client Fanout
Messages are stored once and streamed to connected viewers without polling.
- Posting a message writes to storage before broadcast fanout.
- Moderation status is part of the same message lifecycle.
- Connected clients receive updates over the event stream.
- The demo supports both signed-in and guided demo interaction modes.
Preview
images/runtime-visibility-surface
Anchor target: Operational view
Operational Panels for Request and Network Signals
Backend events and network telemetry are visible side by side during interaction.
- The live panel streams backend events as they happen.
- Network output includes method, path, status, and timing context.
- UI actions can be correlated with transport behavior immediately.
- This setup shortens the cycle for reproducing and isolating issues.
Preview
images/command-sse-surface
Anchor target: Operational view
Command Endpoints With SSE State Convergence
Mutations travel through commands, while authoritative state converges from the event stream.
- Client actions invoke commands without returning JSON state payloads.
- Server updates are published as Datastar signal patches on the stream.
- State convergence uses one global event channel instead of mixed update paths.
- The model reduces drift between immediate UI writes and backend truth.
Preview
images/engineering-quality-surface
Anchor target: Engineering quality
Codebase Quality Signals Built Into Delivery
Typed contracts, reusable composition, and CI rules keep the system maintainable as it evolves.
- Component content is delivered through explicit CMS-shaped fixtures.
- Reusable primitives keep view composition predictable and reviewable.
- CI checks enforce architecture, naming, and interaction conventions.
- The code can evolve with fewer cross-layer regressions.
High-Volume Request Burst
Use the slider to send a large burst of requests from this browser and watch live request logs and SSE updates in real time.
Burst size: 1000 requests
Concurrency: 24 workers
Ready. Choose a burst size and run the load.
Live chat room
Try live posts as the demo user. Sign in to send as yourself.
Room: Lobby
- eboody2026-02-17 17:10visible
a
- eboody2026-02-17 17:09visible
aa
- demo bot2026-02-17 15:39visible
k
- eboody2026-02-17 15:39visible
a
- demo bot2026-02-17 15:37visible
there!
- eboody2026-02-17 15:37visible
test
- eboody2026-02-17 15:25visible
aaa
- demo bot2026-02-17 15:25visible
asda
- eboody2026-02-17 15:25visible
asd
- demo bot2026-02-17 15:25visible
asda
- eboody2026-02-17 15:25visible
test
- eboody2026-02-17 14:48visible
ok
- eboody2026-02-17 14:39visible
blah
- eboody2026-02-17 13:49visible
aaa
- eboody2026-02-17 13:48visible
blah
- demo bot2026-02-16 16:59visible
helloooooooo
- eboody2026-02-16 16:59visible
hello
- demo bot2026-02-14 17:18visible
this is from
- eboody2026-02-14 17:18visible
blah
- demo bot2026-02-14 17:17visible
hello
- eboody2026-02-14 17:17visible
hello
- eboody2026-02-17 17:10visible
a
- eboody2026-02-17 17:09visible
aa
- demo bot2026-02-17 15:39visible
k
- eboody2026-02-17 15:39visible
a
- demo bot2026-02-17 15:37visible
there!
- eboody2026-02-17 15:37visible
test
- eboody2026-02-17 15:25visible
aaa
- demo bot2026-02-17 15:25visible
asda
- eboody2026-02-17 15:25visible
asd
- demo bot2026-02-17 15:25visible
asda
- eboody2026-02-17 15:25visible
test
- eboody2026-02-17 14:48visible
ok
- eboody2026-02-17 14:39visible
blah
- eboody2026-02-17 13:49visible
aaa
- eboody2026-02-17 13:48visible
blah
- demo bot2026-02-16 16:59visible
helloooooooo
- eboody2026-02-16 16:59visible
hello
- demo bot2026-02-14 17:18visible
this is from
- eboody2026-02-14 17:18visible
blah
- demo bot2026-02-14 17:17visible
hello
- eboody2026-02-14 17:17visible
hello
Operational View
Run a demo interaction, then follow request, backend, and SSE behavior in one timeline.
Debounced command updates server-side request flow filtering.
No timeline events yet. Trigger a demo action to populate this view.
Engineering Quality
Quick signals a lead Rust engineer can validate in this running app and in the repo.
Layer boundaries stay explicit
Business policy, transport, and storage code are separated so feature work does not leak implementation details across layers.
- App services consume traits, not SQL primitives.
- Domain types carry invariants at compile time.
- HTTP handlers stay focused on protocol concerns.
Runtime behavior is inspectable
The page exposes observable runtime surfaces that make backend behavior debuggable during normal interaction.
- Live logs stream backend events without manual refresh.
- Network traces show request shape and timing in context.
- Interactive demos can be correlated against transport output.
Quality guardrails are enforced
Architecture and component conventions are checked by scripts so regressions are caught before merge.
- Datastar command and SSE conventions are verified in CI.
- Component composition and naming rules are enforced.
- CMS-shaped fixtures are validated as part of component flow.