Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we address / discuss scale? #6

Open
Potherca opened this issue Feb 4, 2022 · 0 comments
Open

Should we address / discuss scale? #6

Potherca opened this issue Feb 4, 2022 · 0 comments

Comments

@Potherca
Copy link
Member

Potherca commented Feb 4, 2022

As noted on Gitter by @gibsonf1 (thank you!)

[..] There is a scale issue as well. For example, we have a service that converts a pdf into units of thought which results in up to milions of triples per pdf. So it could be a big burden for a server to handle redirects etc for millions and millions of uris per moved user

A resource in our case is as small as a single triple, and there can be 100's of millions of these in a pod, so scale is an issue but I guess you really just need a pattern matching at the server level to do it. Such that any request with a certain uri pattern would redirect to another pattern.

This should either be discussed and addressed in the spec, or mention may need to be made if the spec is not otherwise adapted in this direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant