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 expect a subgraph to have multiple "entities" as a common approach? #290

Closed
longility opened this issue Aug 17, 2021 · 1 comment

Comments

@longility
Copy link

The demo shows an example of 1 subgraph - 1 entity, which is more "pure" microservice. However, I think that 1 subgraph - many entities (more "monolith") may be a common scenario. I see it as an incremental and pragmatic approach to development where we can defer splitting up the subgraph to more subgraphs, which may not necessarily be 1 subgraph - 1 entity as well. I don't know if the lib will conveniently allow that or not.

Should we expect a subgraph to have multiple "entities" as a common approach? If so, should we consider that part of the demo?

/cc @prasek

@prasek
Copy link
Contributor

prasek commented Sep 21, 2021

@longility yes that's a good point. the demo was intended to keep things as simple as possible, but that would be good to mention and perhaps include in the demo. /cc @michael-watson

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

2 participants