Web | C++

on YouTube ↗41m

" summary

Compares three C++ WebSocket stacks by building a working straw‑poll service that uses FlatBuffers for zero‑copy messages and a static HTML/JS client; measures code size (uWebSockets ~1.6 KB, IncludeOS ~3 KB, Beast ~9 KB; uWebSockets <100 LOC, Beast >400 LOC), compile/iteration times, and memory under load. Shows uWebSockets handling 10,000 concurrent connections with only ~2 MB extra RAM, IncludeOS as a bootable ~1 MB unikernel option, and Beast as a low‑level, multi‑threaded but template‑heavy solution. Gives concrete APIs, lifetime and async write strategies, and microbenchmark numbers.

AI-written summary · about

" chapters (15)

1. 0:00Intro
2. 1:17ROADMAP
3. 2:57ADVANTAGES
4. 3:41CHALLENGES
5. 6:33EXAMPLE SERVICE
6. 11:16VALIDATION
7. 11:49SCHEMA
8. 13:52CLIENT
9. 17:02IMPLICIT CONVERSIONS
10. 22:12CYCLIC CALL GRAPH
11. 30:45EXAMPLE CODE SIZE
12. 31:25EXAMPLE COMPILE TIME
13. 35:01MEMORY USAGE USER SPACE
14. 36:01KEY STRENGTH
15. 37:43FUTURE

" related talks

• 01h 01mGet rich quick! Using Boost.Beast WebSockets and Networking TSVinnie Falco · CppCon 2018
• 01h 16mApplied C++20 CoroutinesJim Pascoe · ACCU 2023
• 13mIntroducing Beast...Vinnie Falco · CppCon 2016
• 58mSSE vs WebSockets vs Long PollingMartin Chaov · JS Fest 2018
• 30mWebSockets: The Real-Time AvengersHarshil Agrawal · CityJS New Delhi 2024
• 29mWebSockets Bring Light at the End of the TunnelJoel Lord · NodePDX 2016
• 01h 14mWebSocket: How, When and What It CostsAleksandr Lavrinenko · Mobius 2020 Moscow
• 01h 00mThe Future of Rust Web ApplicationsGreg Johnston · Rust Nation UK 2025