Meteor community is the best OpenSource community I have ever worked with. Unfortunately, the framework couldn't reach it's goals & we had to move on into other things :(
> Just to clarify, this is what the author wanted to do. You can create distributed apps easily using Fleek or by manually uploading to IPFS, Arweave or Filecoin.
Seems like the author has never build an app before. There nothing easy even with the current tech. It's much harder with the tech they mentioned.
Even with that, there's a centralized system anywhere. Liek Arweave's DNS system etc.
It's not traditional LOD baking. There's no LOD baking. It's the new rasterization system doing the whole work.
And most of us doesn't use fast SSDs like in PS5 and it works really well. Also these engineers said, it even works just fine with slowers HDDs too. Because, they don't stream meshes for each camera movements. But it's a continuos setup.
We don't have insight on what our customer's use mostly.
We use existing technologies. Anyone can use any cloud Database service. We've datacenters on San Fransisco and in Belgium. So, based on those users can choose where they need to deploy their DBs.
Usually we recommend to configure databases via env variables. Users can also use our [now secrets](https://zeit.co/docs/getting-started/secrets) service as well to avoid hard-coding secrets.
Whether it's serverless of not choice of hardware is very important.
For an simple web app, you might not need special CPU and Memory requirements.
But for a video encoding/decoding serverless app may needs different CPU/Memory requirements (and GPU).
That's what this `slot` configuration property does.
The default is good enough for all the general purpose apps. But if you need more, you can control it.
> 1. Once your docker container is built, am I paying to store it on Zeit?
No. You don't need to pay to store containers.
> 2. How is a Dockerfile versioned? Can I update it? Or do I need to redeploy
Once the Dockerfile is built, you'll get a URL for that. It's a immutable URL and you don't need to re-deploy again.
It'll sleep if there are no HTTP requests. If there are it'll start again.
> 3. Is pricing for containers granular by time or per request to a container?
It's based on the container running time. But we'll have a another blog post on this soon with more info.
> 4. How can these Dockerfiles talk to each other? Is there an API or method to fetch specific url's for each container?
There's no internal API to communicate with each other. But every docker container has a URL. You can use our [alias](https://zeit.co/docs/features/aliases) feature and communicate with each other via HTTP.
As it previously said it's two different projects. Meteor is a full stack framework where it does everything from data to rendering.
But Next.js is not like this. It's only for the UI (rendering)
You can build server rendered React apps pretty easily. It supports dynamic imports, prefetching, preloading and you name it.
Now you can export any Next.js app into a static app too.
Recently, Meteor adds some new JS features into it's build setup too.