Do you think that's still true in a "serverless" architecture?
4,602 karma · joined October 1, 2007
[ my public key: https://keybase.io/boucher; my proof: https://keybase.io/boucher/sigs/QnKkp1_s4Cs18LqgGer6G6ME-KXo6SqZ56xHjiqND74 ]
EFS/NFS makes a lot of sense I think when you have a lot of random/unpredictable access across large numbers of files. You could do the same thing with FUSE/S3 but across lots of smaller files/accesses I would think the overhead adds up faster.
From a caching perspective, you wouldn't seem to gain much in lamda. You can cache in memory/tmpfs until your container eventually dies, and then you likely aren't on the same machine so there's no EFS level caching to take advantage of.
I'm biased of course, and I understand why some people are turned off by an in browser solution. But I think it's probably faster, in most cases, to try something you've never installed in Tonic than in this. (And I hope there's genuine value in things like being able to share links to your experiments.)
(edited to add that, of course, pickle is part of the python standard library, which makes this specific feature less interesting)
They are an offshoot of the Japanese division. All of their games are really well done. There are several other places in the bay area doing this now too, this one in Richmond is also great: http://letsescapesf.com/
It has data visualization features, and it also manages npm packages for you, but those are just features. Another way to think of it is, a different (hopefully better) version of the thing you'd get if you just typed "node" in your terminal.
The actual thing you are embedding is a version of our app, Tonic, which yes interfaces remotely with Node.js. I think this title is the best way of getting the idea across in a few words though.