Meta is building a platform that allows users to seamlessly search for, access, and share files across all cloud platforms and devices; in essence, Google for your files. We’ve closed a seed funding round and are looking for talented developers to help us scale our MVP and take our platform to the next level.
We have exciting development work ahead of us in nearly every area imaginable, including responsive client-side web development, a microservices-based cloud architecture written in Go and Python, performance-critical native client applications, a lightning fast personalized search engine, and complex data science problems in stream processing, semantic analysis, and information retrieval.
We’re right in downtown Boston and looking for talented developers and computer scientists to join us. Offering competitive salaries and large equity compensation. Email us at [email protected] and check out our careers page at https://www.meta.sc/careers
Facebook is already battling pretty large privacy concerns with a lot of media scrutiny. There's a lot of danger in having a tool like the graph search available to people with malicious intent. The EFF had a good post on the subject from back when it was active [1].
When you're part of a network as big as Facebook's, at a certain point your own privacy settings don't matter very much, because the people you're connected to can generally fill in the gaps about whatever you may want to keep private.
It's imortant to keep in mind that metadata alone says a lot about a person. Combine that with more precise data from a few people in the same set and you can end up with very accurate data about everybody.
This may or may not be what you're looking for, but you should check out my company's product, Meta Search. Our website is https://www.meta.sc and our product provides a really powerful search experience across a bunch of different cloud platforms as well as local devices. Happy to answer any questions you may have!
Meta is building a platform that allows users to seamlessly search for, access, and share files across all cloud platforms and devices; in essence, Google for your files. We’ve closed a seed funding round and are looking for talented developers to help us scale our MVP and take our platform to the next level.
We have exciting development work ahead of us in nearly every area imaginable, including responsive client-side web development, a microservices-based cloud architecture written in Go and Python, performance-critical native client applications, a lightning fast personalized search engine, and complex data science problems in stream processing, semantic analysis, and information retrieval.
We’re right in downtown Boston and looking for talented developers and computer scientists to join us. Offering competitive salaries and large equity compensation. Email us at [email protected] and check out our careers page at https://www.meta.sc/careers
We use both and try to stick with standard runtimes wherever possible, resorting to flexible runtimes for things doing heavier processing and/or with lots of instances.
The standard runtimes are superior in a lot of ways, two big wins being lightning fast deployments (seconds vs. many minutes) and batteries included for all the app engine services. Logging in the flexible environment can also be a bit lacking. When you have something running in standard runtimes you basically don't have to think about many of the things that can normally go wrong on a server.
That said, many things about the flexible environment are rapidly improving, they've certainly come a long way since we first started playing with them around 6 months ago.
We use a combination of both at my company. We use the standard environment for the majority of our services, doing things like proving APIs, serving webpages, performing datastore interactions, etc. The flexible environment starts to make a lot of sense when you're doing heavier weight processing, text analytics in our case. App Engine instances are relatively cheap when you're using the smallest instance sizes, and have even more benefits if your application has idle time when they can spin down completely, but costs start to go up very quickly if you need to move to the bigger instances in the standard environment [1]. The flexible environment is current billed at the rate of the machines you're using, so is much cheaper for bigger instances [2].
The other downsides are the deploys are slower, for now at least, and it's still in Beta. Beta means it has SLOs, which are like reliability goals, but it doesn't have SLAs, which means you get refunds for downtime. App Engine Standard does have SLAs:
Beta products are also more willing to make backwards incompatible changes with shorter deprecation timelines. But overall it's certainly a lot more, ahem, flexible. Sneaky awesome feature is ability to install things like imagemagick , phantomjs, or ffmpeg, which to shamelessly self-promote I wrote about here:
That's using a custom runtime, which won't be as officially blessed, but you can of course just extend from the official runtimes, since they're on Google Container Registry and open-source:
Can't edit the parent anymore: Actually the flex price should go down compared to Compute Engine because it should be optimised for a more specific use-case?
waprin's comments are on the nose with what we've experienced.
There are pain points with the flexible environment that we don't have to worry about at all with standard runtimes. The two biggest ones for us are slower deployments and a lack of monitoring tools.
Just today we actually switched one of our App Engine modules to Flexible runtimes out of necessity as we we're hitting quotas for App Engine infrastructure, and in doing so we no longer have easy access to metrics on how many instances are running or memory usage for the service. The "Cloud Trace" tools are also impaired when you aren't using standard runtimes. In short, you lose visibility into your instances. It ends up being a tradeoff between developer time and cost.
With certain runtimes in the flexible environment, you also lose out on pieces of the App Engine infrastructure like memcache, which are invaluable in optimizing services.
Ahhh yes we've been hit with this. There are subtle differences in the GAE APIs when using flex. Trace as you mentioned, but also channels api doesn't work at all, cloud debugger only sometimes works, etc.
Most of these have gotten a lot better since managed vm's first rolled out (3 years ago!?!?!?!?!)
Meta is building a platform that allows users to seamlessly search for, access, and share files across all cloud platforms and devices; in essence, Google for your files. We’ve closed a seed funding round and are looking for talented developers to help us scale our MVP and take our platform to the next level.
We have exciting development work ahead of us in nearly every area imaginable, including responsive client-side web development, a microservices-based cloud architecture written in Go and Python, performance-critical native client applications, a lightning fast personalized search engine, and complex data science problems in stream processing, semantic analysis, and information retrieval.
We’re right in downtown Boston and looking for talented developers and computer scientists to join us. Offering competitive salaries and large equity compensation. Email us at [email protected] and check out our careers page at https://www.meta.sc/careers
Meta is building a platform that allows users to seamlessly search for, access, and share files across all cloud platforms and devices; in essence, Google for your files. We’ve closed a seed funding round and are looking for talented developers to help us scale our MVP and take our platform to the next level.
We have exciting development work ahead of us in nearly every area imaginable, including responsive client-side web development, a microservices-based cloud architecture written in Go and Python, performance-critical native client applications, a lightning fast personalized search engine, and complex data science problems in stream processing, semantic analysis, and information retrieval.
We’re right in downtown Boston and looking for talented developers and computer scientists to join us. Offering competitive salaries and large equity compensation. Email us at [email protected] and check out our careers page at https://www.meta.sc/careers
