VL
ok Thanks, I will try.
Size: a a a
2021 June 02
Ɖ
But I think that having it done only using HotChocolate services would be better and will not introduce some apollo proxy for just combining schemas, so you could try this tutorial https://chillicream.com/docs/hotchocolate/v10/stitching
VL
you have example about hotchocolate?
Ɖ
No I'm not
You could just follow instructions on article above to create stitching service and you could use it as example
You could just follow instructions on article above to create stitching service and you could use it as example
VL
ok, let me try
VL
so I see Apollo, hotchocolate is same. it's only difference about js and .NET right?
VL
I mean with only my purpose is stiching schema
Ɖ
Apollo has different feature set that HotChocolate
Ɖ
They differ in details and integration part, you could try both and choose best option for you
I don't have ready answers because also need to check it out more.deeply in future
I don't have ready answers because also need to check it out more.deeply in future
VL
So I think stiching schema same API gateway for example Kong, Tyk,...
Ɖ
Yeah, something like that
It combines different schemas together and after that it could be used as a single entry point for your distributed API across different GraphQL servers
It combines different schemas together and after that it could be used as a single entry point for your distributed API across different GraphQL servers
VL
I can customize proxy cache, load balancer, rate limit same API Gateway on Stiching schema
VL
if can I think I don't need Gateway anymore?
Ɖ
I don't know about scaling features of shema stitching, but I think it is not responsibility of stitching server
VL
you mean, I still need gateway before stiching to responbility LB, cache...
Ɖ
I don't know anything about such functionality on stitching side, you could investigate it yourself
VL
yepp thanks again, I will try
Ɖ
You're welcome
VL
i try example bu tnot work
VL
I'm not attach my screenshots in group?