Thanks, that’s helpful. Will keep an eye out for that.

Glad that known issues are being addressed. Ideally I wouldn’t be treading new ground but rather deploying existing known patterns and best practices. But it seems like this would be a departure from existing installations. Thanks for your input.

Thanks, appreciate your input.

If postgres is the scaling limit on most deployments, I assume normal postgres scaling via replicas and sharding would apply.

Is the frontend amenable to heavy caching for non-logged-in views?

Thanks, appreciate the data point.

Can you provide any info about the number of pageviews/month or pageviews/hr that setup can support for lemmy?