You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
@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
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
The text was updated successfully, but these errors were encountered: