Feature Request: Edge Caching/Localize satillite server

Is your feature request related to a problem? Please describe.

Feature request:

I would like to have a thin server that acts like a localized cache within a network for the main Nextcloud instance. For example, this would help with replication and network traffic. My home network -> the server location. The thin client would connect to the main server, and it would hold a cache of the files between the two. All clients connecting to the main server would have knowledge about the remote cache/edge points and test the connections.

This is a need to reduce bandwidth cost amongst multiple devices in the same network and repeated traffic locally. This is not needed for hosting applications.

Describe the solution you'd like

Have a portable server version that is there for caching. This client would mostly be there for localized/edge cache needs/or full sync.

Describe alternatives you've considered

I'm considering investigating in the protocol and hotwiring some of the requests and force a full sync on a nextcloud client locally. But this might be a hack.

Start by reviewing the Nextcloud protocol and the Nextcloud client behavior mentioned in the issue, focusing on how requests, local caching, and full synchronization currently work. Before implementation, define the portable server's scope and how clients discover and use edge points; done should include a clear cache or sync design that reduces repeated local traffic without hosting applications.