Open
Description
Description
I am thinking if graphql can be used to replace the need of EI's aggregation service using jmespath rules
I read a bit of both, it seems for me a EI subscription can be replaced by a graphql query and its subscription functionality.
graphql naturally support to aggregate the data according to client's request. client only need to describe the query in graphql and let the backend to handle the query to push the data to client when data available
of course, I do not have full view of all the use cases that EI provide, would like to hear the thoughts of the community
Motivation
utilize graphql ecosystem, lightweight tech stack, easier to extend functionality in backend without impacting frontend
Exemplification
not clear
Benefits
flexible, extensible, fast iteration
Possible Drawbacks
not clear
Metadata
Metadata
Assignees
Labels
No labels
Activity