1) Yes these are HIGHLY scenario specific, but doing benchmarking and detailing is a great point, and we want to do it. 2) We have lots of thoughts about security - but it's all about just use your existing security profile FOR NOW. E.g. if you want to run data on something in private, and the machine would have access, then you can reuse that. You can also use things like env variable, endpoints, etc to provide credentials. We have LOTS of things planned, but I'd love to hear what you'd like first!
For running on the PUBLIC web, it is not for private workloads right now. You could encrypt everything you'd like, but even then, you'll still possibly run on an untrusted node, so not recommended. Instead, choose a trusted provider (e.g. GCP, AWS, etc) to provide the compute, and provision your nodes, and you're good.
3) We have tons of thoughts there too - basically anywhere you have more than 10 devices with/generating data and 100GB, you're PROBABLY running into a compute over data problem. This is many fold! Security, web serving, financial services, IoT, Edge, Fog, multi-cloud, etc etc. We are in the midst of narrowing down to some brain dead ones and providing scenarios and templates - expect lots of this to land in the next few weeks/months.
If you have some that you'd like us to work on, please let us know!
THANK YOU SO MUCH FOR YOUR FEEDBACK. You can also find/chat with the whole team in the #bacalhau channel in Slack [1]
Disclosure: I co-founded the Bacalhau project.
[1] filecoin.io/slack