What can webdev learn from game developers?

Transcript

1. What we can learn from game developers?
2. There will be no code
3. Main problems in games • Performance • Performance • Performance
4. Solutions • Intrusive lists • Better CPU cache utilisation • Makes structures look „weird” • Entity-Component-System • Try to manage data independently form logic • Separate of concerns • Datagram protocols • Connection-less communication • Loosing package isn’t a problem
5. Intrusive lists are completely pointless for our case So I will not get into details
6. Entity-Component-System • Component - collection of data • Should be small • Contain no logic • Entity - collection of Components • In general sense - common ID for the components • System - logic over Components • Contain logic • Modifies one or more components • Do not care about Entities • Listen on events in log
8. Live
9. Live Fluffy
10. Live Fluffy Placeable
11. Live Fluffy Placeable Mobile
12. Live Fluffy Placeable Mobile Jumpy
13. Live Fluffy Placeable Mobile Feedable Jumpy
14. Live Fluffy Placeable Mobile Weight Feedable Jumpy
15. Live Fluffy Placeable Mobile Edible Weight Feedable Jumpy
16. Live Fluffy Placeable Mobile Edible Weight Feedable Jumpy
17. Placeable Mobile Jumpy Weight Jumping
18. Placeable Mobile Jumpy Weight Jumping Moving
19. Placeable Mobile Jumpy Weight Jumping Placeable Mobile Moving Weight
20. „Real example” Electronic Medical Record system
21. Entity-Component • Patient • Name (first name, last name) • Vitals (pulse, body temp., etc.) • Illness • Practitioner • Name • Authentication • License
22. Systems • Authentication • Authorisation • Vitals measurement • Morgue
23. Pros • Adding features to entities is simple • Making snake jumpy is as simple as adding component to it • Removing features is simple • Making rabbit immovable is as simple as removing component from it • You can dynamically add features to entities • Less edge cases, as system is not aware of the entities that do not contain given components
24. Cons • Eventually consistent • Systems tends to grow and touch a lot of components at once • Unexplored technique in webdev land
25. QUIC
26. TCP - pros • Nice when you can keep connection open • Quality of Service • Guarantee of delivery • TLS
27. TCP - cons • No multihoming (at least in IPv4) • One missing package will delay all next messages until delivered • Three-way handshake
28. Hello, would you like to hear a TCP joke? Yes, I'd like to hear a TCP joke. OK, I'll tell you a TCP joke. OK, I'll hear a TCP joke. Are you ready to hear a TCP joke? Yes, I am ready to hear a TCP joke. OK, I'm about to send the TCP joke. It will last 10 seconds, it has two characters, it does not have a setting, it ends with a punchline. OK, I'm ready to hear the TCP joke that will last 10 seconds, has two characters, does not have a setting and will end with a punchline. I'm sorry, your connection has timed out... ...Hello, would you like to hear a TCP joke?
29. UDP • Connectionless • No delivery guarantees • No QoS • No congestion negotiation - can cause package drops
30. QUIC • Implementing TCP guarantees on top of UDP • Still connectionless • Encrypted • No three way handshake • Multihoming • Implemented in user space • Non-blocking on missing packages
31. HTTP 3 = HTTP 2 over QUIC • Multi-network connections handled via multihoming • Faster delivery, even better than via HTTP 2 push • Encryption „reusage” • Less traffic when establishing encryption suite
32. –George Santayana Those who cannot remember the past are condemned to repeat it.
33. FIN @hauleth
34. Questions?