Can you please expand on "connection oriented networks carry a few overheads wrt scalability"? I didn't see anything related in the linked doc.
Is there any w3c doc specifically about web's scaling/caching architecture/principles?
Also do you have any suggestions of how nostr's cache architecture could look like?
Login to reply
Replies (1)
Connection-oriented networks carry overhead because they need to maintain continuous connections, which doesn’t scale well as the network grows. The web scales by focusing on stateless interactions and efficient caching strategies.
For Nostr’s caching, consider distributed caches or edge approaches to reduce server load.