224 karma · joined December 31, 2009
1) fear of a bug. just the right firmware bug and you have 100 million phones lose data, and perhaps bricked too. unlikely, but consider the cost. i would be worried about this if i were in charge of the iphone project and the secure enclave feature were newish. we can imagine pretty good solutions to this one though, with work and time.
2) out of 100+ countries where they sell phones, over time, some will give them a confidential court order saying they must retain this capability. if a foreign court order, they could refuse to comply, but then would have to exit that market -- infeasible if multiple countries. and a different 'version' for just those countries would be noticed over time by security researchers?
3) they might already have an order as such from the U.S., for foreign intelligence purposes. as mentioned a different international version if noticed is a PR disaster for apple. so the easiest way to comply is just do it that way for all phones.
perhaps they push back on the fbi request because that's the one they can talk about, yet it templates the whole issue.
(given it is a 5C with no secure enclave)
that said it will be a big release in other aspects, with pluggable storage engines now, and WiredTiger specifically.
have the carpenter build something (of trivial scope) while you watch. somewhat analogous to coding on the whiteboard in the interview.
come to think of it, it might be darn hard to interview carpenters. but if you watch them work for 2 hours you know everything.
So it's available; albeit there is an intent to have a subscriber build with some extra features that are heavily enterprise biased in their usefulness.
In src/mongo/db/db.cpp I see:
void _initAndListen(int listenPort ) {
...
dur::startup(); // <- this i believe preallocs journal files
...
listen(listenPort); // after journal prealloc i think
p.s. this blog post is a very interesting article overall i think, without commenting on all the specifics...it will not be schmidt.
1. Not a myth! Apple, Microsoft, Yahoo, Google, Facebook, Foursquare, ... There are counterexamples but certainly plenty of young ones. I'm 40+ now so no bias. :-) 2. Correct, myth. I could teach you to be an entrepreneur if you wanted to be one. 3. Myth 4. Myth. Gilt Groupe a good example. 5. Myth
We've always clearly said don't build a bond trading system with it. Our philosophy is one-size-fits-all is over; use the right tool for the right problem.
Based on how I like to define the term, there is nothing in the NoSQL space that does full "ACID", including complex transactional semantics involving many objects, on many server clusters. That is ok : the perf + scale problem isn't really solvable if you don't give on something.
Each "car" holds just 2-4 people. they run on the tracks and switch on and off at the right stops. Very granular.
But still like a train in that you have tracks and power from the tracks. There is no conductor then, so everything would have to be computer controlled.
Add 3 hours as lots of the developers are on eastern time. So that explains the smaller dots as 9 (lunch).
C++ is great. I really like the control it gives one over initialization at construction and scoped destruction. It's pretty safe these days too give pointers aren't highly involved (shared_ptr, stl containers instead).
Theorem 1. It is impossible in the asynchronous network model to implement a read/write data object that guarantees the following properties: * Availability, * Atomic consistency, in all fair executions (including those in which messages are lost).
DoubleClick doesn't use MongoDB (afaik). My understanding is that it is switching over gradually to internal google infrastructure services - so presumably bigtable like things, and its internal successors, whatever those are. That said, MongoDB is basically what I wish I had had when we began building DART long ago.
In the early days of DART we build a proprietary distributed key/value store called UIS. It was super simple and super fast and worked well. The request volume, both read and write to it, was huge: it was hit in realtime by the ad servers.