4 ms·
With graphql, you could provide a unified access point and the resolvers can go to different backend data stores. This does depend on the consumer. Someone wil
by verdverm 7y ago
With graphql, you could provide a unified access point and the resolvers can go to different backend data stores. This does depend on the consumer.
Someone will surely try to convince you of a data lake product. I would leave them separate and then migrate components as appropriate.
Kubernetes and Istio / service mesh, more so, are things to consider. Search for cloud native design patterns and the paper by Brendan Burns