Data-related topics

# Direct data-related topics:

- "non-http" fetch methods (msgpack or bson)
- web-app vs PWA preferred data transports
- client-daraSource vs inter-service transports
- moderately large data:
  - one huge chunk (GraphQL/Falcor/msgpack & cached queries)
  - a lot of smaller ones (websockets to minimize request overhead, even when data is not RT; long-polling as alternative and viable fallback option)
- update frequency? regular overhead
- a lot of small data
  - conditional background data fetching of small data chunks
- fetch polyfills, custom libraries or axios: why, how and when
- server-side flux vs message buses for real-time and near real-time data feeding
- client side rendering: methods, challenges, hacks, solutions
- classic vs SPA vs pJAX
  - _proper_ pJAX form handling: everybody thinks it's OOB when it's not (client + _server_)

# Indirectly related topics

- internal workings of Webservers on async IO loop
- X-Accel overuse, alternatives, pepper caching techniques (rewrites and `try_files` in nginx)
- Rails controllers vs Hanami actions and controller modules, performance and resource usage perspective, why is there not always much of difference (node.js modules, JIT, compiled languages)
- Server side push (http2), nghttpx and conditional webpack bundle preload using it, cookie-based caching: native vs nginx + embedded lua + nghttpx vs H2O + embedded ruby
- data pushing vs embedding data in HTML, total impact (in case reverse-proxy serves most of the resources and backend only works for direct API requests)
- web-app balancing: monolith (multi-process vs multi-threaded and internal vs external control)
- runit init system and why it is the best choice for node.js web-app process controller (KISS, Single Responsibility Principle)