Most implementations (eg. WebRTC) involve pulling in truck loads of C libs; it's insane. And then you want to support other clients? Good luck.
2,215 karma · joined October 29, 2008
C/C++, baremetal/cloud, nginx/openresty/nchan, LuaJIT, PHP, Redis, statsd/rrd
Most implementations (eg. WebRTC) involve pulling in truck loads of C libs; it's insane. And then you want to support other clients? Good luck.
And it's not the experience for many to have a faster browsing experience, but I'm not going to argue how anyone quantities that -- really don't care what others use.
On desktop, I find the tooling much worse and sluggish. But the thread was about mobile, and there are a vanishing number of users of mobile FF.
We [web developers] owe a lot to FF, Firebug, etc, but the writings on the wall for mobile and desktop. Chrome is going to have to screw up really bad, and likewise for the base installs of IE/Edge and Safari. These days, I'm more likely to suggest Brave over FF, if someone really requires a Chrome alternative.
To compete with Memcached's multi-core throughput, it's probably not a big deal for you to run a Redis process per core. Surely you are already running multiple memcached for higher availability, so I can't see multiple Redis procs adding much more complexity.
Of course, Redis has many more advantages. For one, I can't be bothered to ever again not have Redis data types, so Memcached just doesn't make sense in my stacks. And even a caching layer has advantages in being able to persist to disk, so I love that too about Redis.
I dug up the mentioned case, and FB's first contact with the researcher included, "Please be mindful that taking additional action after locating a bug violates our bounty policy." Between FB's whitehat policies and that, I'd be pretty sure not to escalate privileges.
You do not exploit a security issue you discover for any reason. (This includes demonstrating additional risk, such as attempted compromise of sensitive company data or probing for additional issues.) [0]
It's no wonder other bounty researchers didn't find further vectors for exploiting their privileges. There was a researcher not too long ago hit by the book for this.
Surely your calculation doesn't / can't include bandwidth charges? And if you have Windows hosts... cloud screws you too.
You're not wrong that it takes a lot more machines than most shops need, and if you can make your scale elastic, 150 machines probably goes a long way! And to your point, developers undervalue their time a lot, and dealing with colocation and sourcing of hardware and backups can be a real drain to save some on CapEx.
The post only concerns itself with in-memory workloads; I don't think Aerospike is competition in this space, while their advantage is against workloads working against SSD backed datasets. "After Google published a blog post “Cassandra Hits One Million Writes Per Second on Google Compute Engine” – using 300 nodes, we followed the same steps and documented how Aerospike Hits One Million Writes Per Second With Just 50 Nodes On Google Compute Engine. [...] Aerospike on SSD is very comparable to that of RAM. At 100% write, the SSDs are able to sustain 226,000 transactions per second compared to 239,000 for RAM." [0] Redis would have no problem hitting 250K IOPS on just a single core provided by GCE (or AWS EC2 or similar).
[0] http://www.aerospike.com/resource/aerospike-soars-in-the-goo...
So, computers are discriminatory... we might want to ban them along with encryption; think of the children.
I mean, you only get these scars from actually working with your DB and hopefully in development / capacity planning stages, so maybe that makes you a rockstar. Not to take anything away from the Stripe engineer(s).
It too has seen not a lot of traction. However, Google has implemented a competing stack into Chrome (and Firefox supports it) in HPKP (HTTP Public Key Pinning) with sites having the ability to pin their cert, and these browsers will trust that bond all day.
I'd much sooner support adoption of Marlinspike's Convergence or something similarly distributed: http://convergence.io/
"Memory: 3GB RAM / 32 GB onboard / 100 GB online" [0]
And given that I can get a 128GB MicroSD for <$60 (and dropping) and static media (videos, photos, etc) can already be backed by cloud storage, I just don't see the need for such technology.
[0] https://www.kickstarter.com/projects/nextbit/robin-the-smart...
I think you hugely overestimate how measurable this concern is.
For "small" blobs, say <256K, your database is probably faster too. I can only recall one such study (and of only NTFS vs MSSQL), and NTFS was only advantageous at >1MB blobs: http://research.microsoft.com/pubs/64525/tr-2006-45.pdf
So, I got cast irons. It's trivial to keep them seasoned and thus non-stick, and they can take the beating of very high heat -- searing meats -- and any metal utensils or rough substances.