Infrastructure discussion thread

[deltaidea]

There're two options:

• Doing everything centralized.
• Decentralizing some parts of the registry.

I want to provide stats on the packages, and that requires a central point of info collection.

I also can't spend much money on hosting.

Another thing to consider is that while npm packages contain only several Kbs of source code, mcpm packages can contain HD textures. Traffic generated by contents of packages can quickly become the largest cost in the system.

What I propose:

• Allow to upload small packages (<5 Mb) to the registry.
• Allow to instead provide a direct download link for any package.
• Allow to instead provide a magnet link for any package.

That way, publishers can still have their packages available with minimal costs for everyone involved.

Relevant links:

• Elasticsearch hosting with a free plan - can be used for the meta info on the registry.
• create-torrent npm package.
• Amazon S3 pricing - has a free 12-month trial, which sounds great.