Web | C++
summary
Small voting webservice is implemented with WebSockets and FlatBuffers, showing end-to-end code and benchmarks: uWebSockets: ~2 MB memory for 10,000 concurrent connections, FlatBuffers: about three orders of magnitude faster and far less memory-hungry than JSON, and implementation sizes differ (uWebSockets under 100 LOC, Beast ~400+ LOC, IncludeOS ~3 KB source). Compilation and iteration times favor uWebSockets (fast static link), Beast is template-heavy and slower, IncludeOS targets unikernel security but lacked a debug build in these tests.
AI-written summary · about
chapters (13)
- 0:00Introduction to web and C++
- 2:12Web development cycle
- 6:33Example service showcase
- 8:31uWebSockets library
- 10:46Serialization with FlatBuffers
- 13:51Client-side implementation
- 15:31JavaScript pitfalls
- 17:54IncludeOS library
- 19:44Boost.Beast library
- 25:12Managing asynchronous state
- 30:45Library comparison
- 34:15Performance benchmarking
- 35:42Conclusion and Q&A
related talks
30mWebSockets: The Real-Time Avengers
01h 01mGet rich quick! Using Boost.Beast WebSockets and Networking TS
29mWebSockets Bring Light at the End of the Tunnel
58mSSE vs WebSockets vs Long Polling
41mWebsockets as the glue to interactivity
40mSocket to me
30mUnderstanding the realtime web with websockets
33mFun With Websockets