229 karma · joined April 5, 2012
In brief, the goal with CBTI is to force yourself to get out of bed at 8am (say). You can still continue going to sleep at whatever time you’re used to. So clearly, you’ll be extremely tired if you keep getting 5-6 hours of sleep. My therapist told me that I’d essentially hate him for 1.5 weeks until this keeps going. Also, no naps are allowed in this phase. At some point, your body will be so tired that you’ll just pass out at midnight.
Book tokens?! Is this some kind of 40s cryptocurrency?
https://en.m.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fen...
For instance, it certainly is possible to run a Cassandra cluster by having each instance run in its own Docker container. My understanding is that it would be much more efficient to run this cluster with a dedicated Cassandra cluster instead.
Is this right? Or are the performance benefits of running a dedicated Cassandra scheduler on Mesos negligible compared to running them in containers?
The article doesn't mention any startups. Any ideas what startups could be potential disruptors?
These seem to be way more mature than Swarm.
At some point I asked them whether they could "emulate" Gmail's UI, so that these apps and Chrome extensions could run on Fastmail. But understandably this is quite a big task. If they could pull it off, it would be quite phenomenal though..
I understand that ES can lose data, or have some data storage problems, but one could just as well store all the incoming data on Hadoop or so, without having to bother with C*, no?
But shouldnt WikiLeaks be releasing this as a torrent?! Wouldn't that be much more effective, both efficiency and cost-wise?
Based on the schema he writes at the beginning, it looks as though he works mostly with time-series. My understanding is that Cassandra is particularly well-suited for these types of workloads (definitely more so than MongoDB?). If the write throughput is such that a single server can handle it, how would Postgres compare with Cassandra? What are the distinctions in read-latencies? Storage space?
Perhaps for the next article..?