Hi all. I have a question on system design. I want to create graph ql apis for my profile info service and my order history service. I was wondering if there is any complication to that or would they just be separate apis connected by the front end to make payments with a payment gateway like Square? My profile info api will provide auth and payment info while my order history api recieves the history of orders as well as sending the last 5 orders made

Hey @Kevin Lam, I’m not an expert with graphql, but I don’t see any downside of keeping them under the same api.

Thanks @Frank I'll try to see if I can make it work.