It might not be the best tool available, but Timescale's columnar capabalities [0][1] looks great to me. I mean, being able to achieve 90%+ compression on a row-oriented database is not something to be ignored.
I'm not so sure. According to [1], for 1MB data transfer over TLS there's up to 15% overhead used for encryption on WLANs. That's 15% more data you have to process, which is not quite the carbon footprint of your coffee drink if you consider how many requests you serve. And that's just data, not to mention all calculations necessary to actually encrypt stuff.
I get that TimescaleDB is good for time series and the like. HOWEVER, people are actually using its extension to just improve PostgreSQL performance on OLTP workloads without having to change a big piece of tech. I have experienced it myself: just enable TSDB in a regular PG database and you can expect things to work faster, no code change required.
Django has always had some magic, although much less than ruby/rails.
That kind of magic is the reason why it is a pain to package a Django project with py2exe, for instance.
Yeah, I guess I could say that before I tried rebinding ctrl-w and some of the Fx keys (like F12).